Hi,
We upgraded to the V5, while i thought all was running fine we experiment a lot of issue with our member who can't login the forum they have after an error 500.
https://www.loom.com/share/3aa832e2cef24762ae4a1a9bb104f696?sid=faac9823-ae10-472f-8865-6b29839a11c5

What i don't understand is : i don't have the problem ☹️
And some others user too.
If i go tho his profil and try to login as user : it causes an error 500 too !!!

Also less urgent we have a problem with the links of the reactions image who have been modified : example : https://www.patrol-gr.net/uploads/https://www.patrol-gr.net/uploads/reactions/merci.png

Thanks for your help.

Olivier

Are there any logged errors in your server log?

1 hour ago, Daniel F said:

Are there any logged errors in your server log?

Hi, i have a lot of this in system log and nothing in error logs

TechSmith Screencast

2025-05-02_12-17-06

World's leading screen capture + recorder from Snagit + Screencast by Techsmith. Capture, edit and share professional-quality content seamlessly.

I tried to change his usergroup but no

Its your server error logs my colleague is referring to. So those would be on your server somewhere. If you are unsure where to obtain those, you would need to speak to your hosting company

Here it is :

2025-05-02 11:38:23.290952 [NOTICE] [233678] [90.23.148.61:57857:HTTP2-1#patrol-gr.net] [STDERR] PHP Fatal error: Type of IPS\core\Statuses\_Status::$commentClass must be ?string (as in class IPS\Content\Item) in /xx/xx/public_html/applications/core/sources/Statuses/Status.php on line 23

2025-05-02 11:38:37.023924 [NOTICE] [233678] [90.23.148.61:57857:HTTP2-5#patrol-gr.net] [STDERR] PHP Fatal error: Type of IPS\core\Statuses\_Status::$commentClass must be ?string (as in class IPS\Content\Item) in /xx/xx/public_html/applications/core/sources/Statuses/Status.php on line 23

2025-05-02 11:38:53.120133 [NOTICE] [233678] [90.23.148.61:57857:HTTP2-11#patrol-gr.net] [STDERR] PHP Fatal error: Type of IPS\core\Statuses\_Status::$commentClass must be ?string (as in class IPS\Content\Item) in /xx/xx/public_html/applications/core/sources/Statuses/Status.php on line 23

2025-05-02 11:38:54.920619 [NOTICE] [233678] [90.23.148.61:57857:HTTP2-15#patrol-gr.net] [STDERR] PHP Fatal error: Type of IPS\core\Statuses\_Status::$commentClass must be ?string (as in class IPS\Content\Item) in/xx/xx/public_html/applications/core/sources/Statuses/Status.php on line 23

2025-05-02 11:39:36.066053 [NOTICE] [233683] [90.23.148.61:57862:HTTP2-1#patrol-gr.net] [STDERR] PHP Fatal error: Type of IPS\core\Statuses\_Status::$commentClass must be ?string (as in class IPS\Content\Item) in /xx/xx/public_html/applications/core/sources/Statuses/Status.php on line 23

2025-05-02 11:39:55.245891 [NOTICE] [233683] [90.23.148.61:57862:HTTP2-5#patrol-gr.net] [STDERR] PHP Fatal error: Type of IPS\core\Statuses\_Status::$commentClass must be ?string (as in class IPS\Content\Item) in /xx/xx/public_html/applications/core/sources/Statuses/Status.php on line 23

2025-05-02 11:39:57.230042 [NOTICE] [233683] [90.23.148.61:57862:HTTP2-9#patrol-gr.net] [STDERR] PHP Fatal error: Type of IPS\core\Statuses\_Status::$commentClass must be ?string (as in class IPS\Content\Item) in /xx/xx/public_html/applications/core/sources/Statuses/Status.php on line 23

That's the same issue I had. Take a look there for the fix.

Basically the fix was to: You can delete that Status.php file since it's no longer used in v5.

Edited May 2May 2 by rnorth6920

27 minutes ago, rnorth6920 said:

That's the same issue I had. Take a look there for the fix.

Basically the fix was to: You can delete that Status.php file since it's no longer used in v5.

I think this should be reported as a bug. The upgrader itself should remove the aforementioned file. i.e. do a proper clean up by itself.

46 minutes ago, rnorth6920 said:

That's the same issue I had. Take a look there for the fix.

Basically the fix was to: You can delete that Status.php file since it's no longer used in v5.

18 minutes ago, Miss_B said:

I think this should be reported as a bug. The upgrader itself should remove the aforementioned file. i.e. do a proper clean up by itself.

Many Thanks, deleting the file made the trick :)
Same opinion as Miss_B, i don't understand why the upgrade didn't deleted the file and in same way i disabled the status system before made the upgrade :s

Upgrades will not tend to delete anything but I will see if we can get that handled a bit better