Last post by radu81 -
If your provider will end up offering PHP 8.1, try to update to Elkarte 1.1.9 and use PHP 8.2. I'm not sure Elkarte 1.1.9 is fully compatible with PHP 8.3 or greater Regarding on how to change PHP version, are you using cpanel or any other panel? If so which one? Otherwise ask your host.
Last post by ahrasis -
You can even try php8.4 too if you are able to do that with your hosting. And yes, please report whatever version of php you are using, especially when there is any problem.
Last post by Mrs. Chaos - That may be the reason. Unless someone knows another reason, I will (finally) upgrade to at least 1.1.9 in the next few days. I will report later on whether the PHP update worked.
Last post by Zioclive -
Hi Mrs Chaos I'm a newbie indeed in this matters, but if I were you I would firstly upgrade from elkarte 1.1.8 to elkarte 1.1.9 and after that I would change from php 8.2 to 8.3 .
Anyway just for your info my provider does not force me changing my php version... some years ago i've changed my web/php provider for this very reason.
I'm currently still using PHP version 8.1 for the forum, but my webspace hoster will soon switch off 8.1 and 8.2. Now I'm trying to change my forum to 8.3, but it's not working. If I just change the version in my hoster's settings, the forum “disappears” from the net (empty page), so I can no longer access the administration center. I had already changed from 8.0 to 8.1 a long time ago, but I can't remember how I did it ... Can someone please write in which order I have to do what and where so that the change to 8.3 works?
Last post by Steeley -
Yea, and it happens at some point when the message count in a topic exceeds some value --that's something @Spuds is going to have to fix...
Seems like the # is getting changed to %23 Seems like something is getting mixed up, but not too sure if it's in the generator, or something in just that page. It's the only part of the forum that seems to have the issue. Never noticed before, due to lack of use of the page? This is confirmed to be 2.0 Dev only issue.
