News/blog categories » News archive » 4.2.1 released

Skip navigation

4.2.1 released

2,917 views
Added 11 October 2009, 10:32 PM

Version 4.2.1 has now been released. This version is a patch release that introduces a number of bug fixes since the last release. Upgrading is suggested due to some important fixes to issues arising after the first recommended (widely tested) version of 4.2 came out.

To upgrade follow the steps in your website's http://mybaseurl/upgrader.php script. You will need to copy the URL of the attached TAR file as one of these steps ("3: Upload an upgrade TAR for extraction").

ť alternatively (but not recommended), you can manually upload the files inside the attached TAR file over existing files (7-zip is just one of many tools for tar files). This is not recommended because it will bypass the upgraders addon-aware extraction algorithm and potentially cause problems.

Your upgrade to version 4.2.1

You can generate an upgrader from any version of ocPortal to any other version. If you access this upgrade post via the version information box on your Admin Zone front page then we'll automatically know what version you're running.
If you'd prefer though you can enter in your version number right here:

Important

ocProducts cannot make any guarantees about the speed of which any new bugs might be patched, for this upgrade or any other upgrade. It is your own responsibility to make and test a full website backup (files and database) before you upgrade, for use in the unlikely event of you wanting to revert your upgrade. Some users may wish to test upgrades (and pre-fix any theme compatibility problems that could occur) on a staging site (a private mirror of their live site).
If you don't follow our advice by taking and testing a backup, and end up needing emergency repair help, ocProducts can help charged at our hourly rate.

For more details, see our upgrading tutorial.

Fixes have been made to the following issues:

Major fix for Internet Explorer on forms with upload fields that are optional alternatives to URL fields.
Major fix to new Flash uploader when a validation error happens just after an attached file uploads
Workaround in new Flash uploader for Flash cookie caching bug
Fixed support for .op files
Major fix to theme images
LDAP fix (one specific problem - note that we are only supporting OpenLDAP and ActiveDirectory)
Fix to SEF URLs, when item names of items deep within a tree are edited
Fix to SEF URLs, when item names of items are edited and no changes made to the name
Many minor fixes (too many to list)

Also the following feature changes have been made:

Support for closing support tickets from inside the tickets module (customers may use this also)
Various measures to introduce better stability for developers, when errors happen
Drag+Drop uploading for posting forms, on Firefox 3.6 (currently in alpha) and browsers with Google Gears installed (this is really cool)
New icons for addon/module management

Retweet

Stumbleupon

Digg

Trackbacks

There have been no trackbacks yet

» Trackback link

Comments

By cpet, posted 12 October 2009, 12:15 AM

The upgrade file is 25 mb, extracting it just extract a data.ocp file. Is this a known issue?

Also the upgrade script doesn;t recognize 4.2.0 as a valid version.

By cpet, posted 12 October 2009, 12:17 AM

Your upgrade to version 4.2.1

Version 4.2.0 is not recognised
Upgrade file: Critical startup error , or download upgrade directly (25 Mb).

By Chris Graham, posted 12 October 2009, 2:03 PM

Hi,

Yes, I can see we've got a problem here. I am working on it now, it should be resolved soon.
Thank you for your patience.

By Chris Graham, posted 12 October 2009, 2:32 PM

The problem is now fixed.

By cpet, posted 12 October 2009, 10:50 PM

Yeah saw that both my sites are updated thank you

next critical path

By digitalpublic, posted 13 October 2009, 8:42 PM

My uploader ist not responding to any kind of password, master password, the hint inside the info.php or any else…

bizarre…a bug?

By Chris Graham, posted 13 October 2009, 8:59 PM

This sounds like user error to be honest, as this code is pretty simple and mature. If you look in info.php, you'll see a line like…

Code


			$SITE_INFO['admin_password']='d41d8cd98f00b204e9800998ecf8427e';

d41d8cd98f00b204e9800998ecf8427 would be the password here, and it has to be put in the master password field (it is not the FTP password). Make sure to paste it exactly, with no extra white-space.

Hm

By digitalpublic, posted 13 October 2009, 9:05 PM

your were right. unfortunately the master password i wrote down is not valid. the info.php tip made it. now the server failed w/ a timeout and i do have to do it manually anyway ;-(

didn't work out for me w/ WordPress either - this automatic ftp-stuff

thx again for ur help

sleep well (if here in europe?)

Joerg

will this change any current setting..

By sandron, posted 15 October 2009, 6:41 PM

Ive made modifications to some of the .tpl files, images, CSS, and /sources/*.php .. and some customization through the adminzone.. will this autoupgrade affect these settings..or should I go for a manual upgrade… pls clarify..

thanks

By Chris Graham, posted 16 October 2009, 12:29 PM

You definitely should not be changing original PHP files, or generally any original file. There's an override system to stop you needing to do this, please check the framework tutorial. As obviously upgrading changes files, so if any of the files you've edited are changed in the new patch, your changes would be overwritten.

By Allen, posted 16 October 2009, 6:11 PM

Just to elaborate on what Chris said, it's not that you can never make PHP changes without being overwritten each upgrade. We've built in an override with exactly this in mind. (basically, save all of your changes into the appropriate _custom directory).

By sandron, posted 17 October 2009, 5:00 PM

thanks Allen & Chris.. that should help..