Release 3.3.0 Beta

[shawn_a]

ok I went ahead and just fixed ajax timeouts anyway. heh

Also I found an issue that has probably always existed but is now an issue, and am curious how we should handle it without redesigning it entirely atm.

Update.php gets executed after an upgrade, then is deleted along with install.php and setup.php, if not a new install. What is now new is that is that it used to only run when upgrading from a pre 3.x version. Now it is always executed by design.

The problem with this is that if the file exists and a visitor visits the front end they are redirected to the update.php. So basically you have to visit your site after upgrading to avoid this, I think this has always been an issue, but now more so, and since we have no maintainence mode someone ( the first visitor )will get redirected to the login page.

I have added logic to send a 503 and a new lang string when visiting front end after upgrades.
I also added a new status and lang string for upgrades when visiting back end.

Should I do the same for installs or would that be confusing for people to have to actually goto /admin and not just site root.

This has been pushed to develop branch if anyone wants to test it before i move it over to the beta.