Hi guys,

I have a webpage on my hands which is on old October build - 170. The updater requires that I update my php to above 5.5.9 and edge updates to be turned on. My php is 5.6+ , and I set 'edgeUpdates' => true in my app/config/cms.php file, but still can not update. I always get the message "An older version of OctoberCMS has been detected. Please check you are using PHP version 5.5.9 or above, turn on edge updates in the CMS configuration and try again."

Can anyone help me out ? I also tried with php artisan october:update , but still the same message.

What version of php you are running? Did you run apache/nginx on windows or linux?

Hi there,

The production is on linux with apache, php 5.6.x. I am simulating first on local dev environment running xampp on windows with apache and php 5.6.x.

P.s. I am not giving the exact php versions because I don't have access right now, but I think this is enough? If not, i will get more detail. :)

A small update - I think the server requires edgeUpdates parameter to be passed, but this build of October does not consider it in the Update methods no matter if you put it in the cms.php. So what I did is that I manually passed it in the UpdateManager.php requestServerData() method like this: if (Config::get('cms.edgeUpdates', false)) { $postData['edge'] = 1; } So now my updater shows the latest updates and starts to download. Right after that I get the flash that update is successful, but nothing seems to be changed. I hard refresh but, I confirm that no updates are applied.

I guess that the Updater has too many changes through the versions and on 170 build can't handle the update files that have been downloaded.

If anyone can help me to get this update working, please ! (:

Update: As I try now from console with php artisan october:update , I get the packages but then I get an exception - File from server is corrupt.

Last updated 8 years ago

Ok, after I tried just to bypass the md5 check, the update process tried to apply the updates, but this broke the setup.

I decided to try another approach, so if anyone is in similar position can find this useful.

1. I created a new October installation with the latest build;
2. I took plugins folder and mytheme folder from the old October setup and pasted them in the new one;
3. The site is working with some small glitches on my email forms, but I will debug them easily;

*Note that this works in my case, because this website has all it's content in the templates created in the backend, and there are no specific models created in the DB, so I could migrate it without migrating the DB. If I had to migrate the DB also, those steps wouldn't have worked this easily.

xchattercho3568 said:

Ok, after I tried just to bypass the md5 check, the update process tried to apply the updates, but this broke the setup.

I decided to try another approach, so if anyone is in similar position can find this useful.

1. I created a new October installation with the latest build;
2. I took plugins folder and mytheme folder from the old October setup and pasted them in the new one;
3. The site is working with some small glitches on my email forms, but I will debug them easily;

*Note that this works in my case, because this website has all it's content in the templates created in the backend, and there are no specific models created in the DB, so I could migrate it without migrating the DB. If I had to migrate the DB also, those steps wouldn't have worked this easily.

did you find a solution to this problem? I solved this problem:

• Disabling all plugins from update
• In the config/cms.php file to change the line 'edgeUpdates' => false, on 'edgeUpdates' => true

Last updated 8 years ago

Yes,

You quoted my post where I described how I did it. :)