PHP 8.1 issues

[prewebdesign]

Hi all - newbie alert! Migrated a client over to Winter 1.2 back end of 2022 and am running PHP 8.0.28 with IONOS on a managed dedicated server. When making the switch to 8.1 through IONOS' control panel, the site goes down. Tried forcing an update but can't see anything that needs changing. Is there something simple I am missing?

[bennothommo]

@prewebdesign are there any logs that might give a hint as to what is happening?

[LukeTowers]

yikes, PHP 4.4.9 is still set as your server's default CLI PHP version? That's incredibly concerning and I would look for a new host TBH.

As far as solving your immediate issue goes, please edit the index.php to have the following lines at the top immediately after the first line of <?php

echo phpinfo();
die;

Then share your results. If it says the webroot is set to PHP 8.1, then try running the following inside of your project root:

rm -rf vendor/ &&
rm -rf modules/ &&
/usr/bin/php8.1-cli /usr/bin/composer update;

[prewebdesign]

phpinfo() results...

[prewebdesign]

[prewebdesign]

Any update to this please @LukeTowers or @bennothommo - is there any easy way to determine what version of Winter is being used within the Dashboard?

I am currently running PHP8.0 on the majority of my installs and need to update to 8.1 without having to reinstall all CMS' one by one? Does the CMS not auto-update to the latest version through the System > Updates & Plugins?

TIA.

[LukeTowers]

@prewebdesign we're still working on backend updating system, we just launched the new website and documentation so the marketplace and backend updating system is the next step that we're working on now.

Do you have composer installed on your server?

[prewebdesign]

That’s good – is there a way for me to identify what version I am running? In terms of composer, I only ever use the web installer as I have always had CLI issues with my web host using SSH so would prefer web interface update if possible. Thanks

[LukeTowers]

If you can get terminal access you can run artisan winter:version. If you don't, you can try triggering the code by adding it to a new CMS page and then visiting that page in your browser:

title="Get Winter Version"
url="/version"
==
<?php
function onStart()
{
    $build = \System\Classes\UpdateManager::instance()->setBuildNumberManually();
    $this['version'] = $build['build'];
}
?>
==
{{ version }}

[prewebdesign]

Thanks Luke. I think the vast majority of my installs are currently running 1.1.9 on PHP8.0 – without terminal access, how can I update these? Do all of them have to be manual updates? i.e. rebuild the whole CMS with the latest version to get the built-in update?

[LukeTowers]

The easiest way right now would be to use the web installer to create new Winter instances and then copy over your config values (ideally you don't copy the files themselves as there have been some changes), plugins, themes, and storage folders from the old versions to the new versions.

Our goal once the marketplace is functional is to have an updater still working for the older versions of Winter (and October) so that you can one-click upgrade to the latest Winter and then use the new composer-based updates behind the scenes from then on, but that might get tricky as PHP versions continue to get deprecated.

[prewebdesign]

Thanks for letting me know. I have been doing that anyway, but I wondered whether there were plans to introduce the auto-update feature as it is time consuming when running multiple installations! With PHP8.0 community support ending in December this year, I need to get a move on…

[LukeTowers]

There definitely is plans to restore the auto-update feature, it'll just take some time :)

[prewebdesign]

Thanks Luke – re. updating config values – can I assume there are no database changes? I can continue to use the current DBs? Thanks Pete Peter Ellis • 07590 196914 • <https://www.prewebdesign.co.uk/> https://www.prewebdesign.co.uk We would love your feedback. <https://g.page/r/CXzXIBJu3w7ZEAg/review> Leave a review » From: Luke Towers ***@***.***> Sent: Thursday, August 3, 2023 7:08 PM To: wintercms/winter ***@***.***> Cc: prewebdesign ***@***.***>; Mention ***@***.***> Subject: Re: [wintercms/winter] PHP 8.1 issues (Discussion #843) There definitely is plans to restore the auto-update feature, it'll just take some time :) — Reply to this email directly, view it on GitHub <#843 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6AL3CZZWYB5ZKLXRDBKCQTXTPSJNANCNFSM6AAAAAAVBX37DI> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/A6AL3C5KBGXJV77EUEIDG2DXTPSJNA5CNFSM6AAAAAAVBX37DKWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAMUWRW.gif> Message ID: ***@***.*** ***@***.***> >

[LukeTowers]

You should always run php artisan migrate after running an update, but if you don't then logging into the backend should trigger it automatically for you.