5.7.4RC1 updating a 5.7.3.1 site

Permalink
Is there a simple way to update from a 5.7.3.1 site to the 5.7.4 RC? I tried replacing the concrete folder with the new one but this just created a lot of errors such as:

Doctrine\Common\Proxy\AbstractProxyFactory::getProxyDefinition(): Failed opening required '/Applications/AMPPS/www/application/config/doctrine/proxies/__CG__ConcreteCoreFileStorageLocationStorageLocation.php' (include_path='/Applications/AMPPS/www/concrete/vendor:.:')

and

An exception occurred while executing 'select cID, msLanguage, msCountry, msNumPlurals, msPluralRule, msPluralCases from MultilingualSections where msLanguage = ? and msCountry = ?' with params ["en", "US"]: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'msNumPlurals' in 'field list'

 
mesuva replied on at Permalink Reply
mesuva
Just hold off until the official release of 5.7.4.

The RC means 'release candidate'. It's for testing and previewing, not for production.
a575606 replied on at Permalink Reply
Ya, um. Thanks. I'd like to do some testing and previewing, hence wanting to install it on my testing server. Need to see if the upcoming release will fix a problem I have. But hard to do that when I can't get to the dashboard.
mesuva replied on at Permalink Reply
mesuva
After replacing the folder, have you triggered an update?

You'd visit:
/index.php/ccm/system/upgrade
(you may need to be logged in first, so maybe log in, then replace the folder, then visit that URL)
a575606 replied on at Permalink Reply
Thanks, that was just what I needed. Working now. But the major point for me is URL forwarding. I'm trying to find a way to put my default locale at the root instead of at /en/ and was hoping with the new URL routing I could do that. But seems like if I set the path of /en/ to blank, it still shows the home page. But if I route the sub pages, i.e. /en/path/to/page -> /path/to/page, that page shows up correctly, as do the urls in the autonav.

Am I getting my hopes up for nothing, or is there a way to do what I'm trying to do?
andrew replied on at Permalink Reply
andrew
For anyone else who stumbles on this thread – any time you replace the concrete directory with an updated core, you have to run the update script:

http://www.concrete5.org/documentation/developers/5.7/installation/...
Stulk replied on at Permalink Reply
I forgot to log in when I performed my upgrade. I followed the instructions in that link to create the concrete.php file and now all I get when I access any IRL is this

return array( 'updates' => array( 'enable_permissions_protection' => false ) );return array( 'updates' => array( 'enable_permissions_protection' => false ) );return array( 'updates' => array( 'enable_permissions_protection' => false ) );