hibernate.properties Changes.
Two manual changes may be required before upgrading to 2.3.1, due to the upgrade to Hibernate 3.2. Hibernate now
enforces the existance of the hibernate.cache.use_second_level_cache property in
hibernate.properties. Because versions prior to 2.2.1 shipped with a typo for that
property, you should manually correct the typo in your hibernate.properties file before
upgrading to 2.3.1. Specifically, if your hibernate.properties file has a line for
this property:
hibernate.cglib.use_second_level_cache
you must correct it to read like this:
hibernate.cache.use_second_level_cache
In addition, if you have enabled
Hibernate's second level cache or query cache, Hibernate now
enforces the existance of the hibernate.cache.provider_class property in
hibernate.properties. Because versions prior to 2.2.1 shipped without that
property, you should manually add the property in your hibernate.properties file before
upgrading to 2.3.1. Specifically, add the following line to your hibernate.properties file:
hibernate.cache.provider_class=org.hibernate.cache.EhCacheProvider
Settings Changes.
The imageSystemPath and imagePathURL settings have changed slightly
in meaning. These settings only affect the image upload functions of the Administrator and no changes are typically
necessary for upgrading. If the imageSystemPath setting is blank, the application will
attempt to derive it from the imagePathURL setting (using
getRealPath() ). At the same, again only if imageSystemPath is
blank, the system will prepend the application's installation directory to the imagePathURL
setting when uploading and saving files.
xerces.jar.
Versions prior to 2.3.1 shipped with Xerces 1.4, consisting of the
/WEB-INF/lib/xerces.jar library. Including this library in installations running on the
1.6 Sun JDK causes errors with the UPS and USPS processors, and with the Google Sitemaps and Froogle (Google Base)
exports. To fix this, we have upgraded Xerces to 2.9.1, which consists of 5 other jar files. If you upgrade, it is
recommended that you delete the old, now-redundant xerces.jar file. Our testing indicates
that it will cause a problem if present on stores running with JDK 1.6.
New Default JSP Templates and the 'Base Layout' Setting.
Version 2.3.1 includes a completely reworked set of JSP templates featuring complete XHTML compliance and modern
CSS practices. The new set of default templates is located in the
/WEB-INF/layouts/default-xhtml directory.
However, if you are upgrading from a previous version, to maintain backwards compatibility, your store will
continue to use the original set of default templates, in /WEB-INF/layouts/default. The
result is you can install the upgrade without worry that your pages will break. We will continue to support and maintain
the original default set of templates for the foreseeable future; however, at a future point in time we may
elect to drop maintenance.
If you would like to take advantage of the new default templates, you can switch after upgrading. Under the
Settings -> Display screen, modify the "Base Layout" setting to "default-xhtml". Doing so may
break your pages, if you have created custom templates that interact with the default templates. We recommend you go
through your custom templates as part of the process of switching, and rework them to conform to the HTML code of
the new set of defaults.
Copyright © 2009-2017 SoftSlate, LLC. All Rights Reserved.
Powered by SoftSlate Commerce