Fixes have been made to the following issues (Described in more detail):
- Adding a download gives an error, if done by URL
- All gallery images become rep images
- Attachment attaching does not work correctly on IE
- Bad breadcrumb link for zone editing
- CEDI CMS zone link broken
- Edit menu in zone editor missing param error
- Error when viewing stats
- Invision Board staff lookup problem
- Miniblocks not given parameters
- News summaries can't be edited
- PayPal IPN broken
- Points mail is incorrect
- Setup Wizard won't recolour the logo
- Small zone creation problem
- Some HTML breaks the WYSIWYG editor
- The main_recent_galleries block does not work correctly
- WYSIWYG editor doesn't load for some
- old versions of Internet Explorer (partial support for 5.5 [distributed with Windows ME], and basic support for 5.0 [Distributed with Windows 98SE])
- browsers set with a non-default text size
Due to the compatibility changes being situated in CSS files, upgrading to this release is a bit tricky, unless custom themes are deleted and then rebuilt. If you wish to preserve custom themes then you must take special action.
Special action to preserve themes
- check that there are ".css.editfrom" files in your themes/<your-theme-name>/css_custom directory that correspond to every ".css" file in there.
- if any are missing, copy over the default theme's CSS file and give it an ".editfrom" suffix. For example, if themes/mytheme/css_custom/global.css exists but themes/mytheme/css_custom/global.css.editfrom does not, copy over themes/default/css/global.css as themes/mytheme/css_custom/global.css.editfrom.
Then upload the files from the upgrade zip, and run force_upgrade.php, as if you were doing a normal upgrade (see the advice beneath this 'Special action' box).
force_upgrade.php has been specially enhanced for this release so as to automatically upgrade your CSS from the improved default theme CSS. It compares your overrided files, the '.editfrom' files, and the new default theme files, and applies any changes to your overrided files.
This automated process may not be foolproof if major structural changes have been made in your CSS files. Backup files are taken and you may refer to them to fix any problems that could develop. If you used the Theme Wizard to create your theme, then the process should work very smoothly (we have tested this).
We appreciate that there is complexity in this upgrade process, but the CSS changes are required as newly modified templates depend upon those changes, and thus there was no other way around it. We have done our best to make the transition as smooth as possible, by adding this new automated 'diff' technology in.
The attached zip file contains the files needed to upgrade from any previous 3.0.x release. After this is done, run http://mybaseurl/force_upgrade.php.
For general advice about upgrading ocPortal, see our upgrading tutorial.
Any common upgrade problems are being tracked in this forum topic.
If you have another problem, please file a bug report and ocProducts will respond and update the topic accordingly.