Jump to content

Featured Replies

Posted

I've been using IPS for about 4 years now and have never had any issues upgrading, but am stumped on this one. When upgrading, everything goes fine and after the upgrader finished, I go to the admin panel. All is well and the background tasks begin to complete. When I try to "visit site" I get a blank page. I open up a different browser that I don't use regularly and I get the website is offline message, due to not being logged in. If I hit log in, I get a 500 error. I have no ads enabled, no addons, using the unmodified default theme, php 8.2 and also 8.3. Why would the admin panel work perfectly, and the public facing not work at all? Any clues?

Edited by rnorth6920

  • Community Expert

A 500 Internal Server Error is a lot like the check engine light of your car. It says something is wrong but not exactly what. You will need to fetch the 500 Internal Server Error from your server error logs in order to make sense of what is happening here.

  • Author

This appears to be the issue:

[Sat Apr 26 10:24:46.269866 2025] [proxy_fcgi:error] [pid 482085:tid 123131947644608] [client XXXXXXX] AH01071: Got error 'PHP message: PHP Fatal error: Type of IPS\\co re\\Statuses\\_Status::$commentClass must be ?string (as in class IPS\\Content\\Item) in home/XXXXXXXXXXX/web/XXXXXX.com/public_html/applications/core/sources/Statuses/Status.php on line 23'

  • Author

Line 23 of that file was:

class_ Status extends \IPS\Content\Item implements \IPS\Content\Lockable, \IPS\Content\Hideable, \IPS\Content\Searchable, \IPS\Content\Shareable

instead of:

class_Status extends \IPS\Content\Item implements \IPS\Content\Lockable, \IPS\Content\Hideable, \IPS\Content\Searchable, \IPS\Content\Shareable

That fix got rid of the 500 error.

  • Community Expert

Glad to see that you got the error fixed. It looks like to me that the file(s) were not overwritten properly for some reason.

  • Author
1 minute ago, Miss_B said:

Glad to see that you got the error fixed. It looks like to me that the file(s) were not overwritten properly for some reason.

I've reuploaded for a full upgrade at least 4 times. Now I'm left with some [[Template core/front/global/userBar is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]] errors, even though its a vanilla default theme. I'll get to the bottom of it though!

And in the admin error log:

ParseError: syntax error, unexpected token "extends" in /home/XXXXXXXX/web/XXXXXXXXX.com/public_html/applications/core/sources/Statuses/Status.php:23

This line 23 is a mess, for me anyway.

Edited by rnorth6920

  • Community Expert
3 minutes ago, rnorth6920 said:

I've reuploaded for a full upgrade at least 4 times. Now I'm left with some [[Template core/front/global/userBar is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]] errors, even though its a vanilla default theme. I'll get to the bottom of it though!

Can you try to rebuild the system cache from your Admin Panel and see if it would help? If that won't help, you can give the recovery mod a try. You can look that up here:

  • Author

Still no dice. I think one issue may be an issue with my Menu Manager. I get an error if I try to set it to default, add, etc.

Screenshot 2025-04-26 115049.png

  • Author

Can someone provide a sample of what their ParseError: syntax error, unexpected token "extends" in /home/XXXXXXXXX/web/XXXXXXXXXX.com/public_html/applications/core/sources/Statuses/Status.php:23 file?

Then maybe I can edit mine accordingly and fix my issue.

  • Community Expert
2 hours ago, rnorth6920 said:

Line 23 of that file was:

class_ Status extends \IPS\Content\Item implements \IPS\Content\Lockable, \IPS\Content\Hideable, \IPS\Content\Searchable, \IPS\Content\Shareable

instead of:

class_Status extends \IPS\Content\Item implements \IPS\Content\Lockable, \IPS\Content\Hideable, \IPS\Content\Searchable, \IPS\Content\Shareable

That fix got rid of the 500 error.

Statuses no longer exist in version 5. This may indicate you have something which is referencing it still in your instance.

  • Community Expert

You can delete that Status.php file since it's no longer used in v5.

Also, the correct edit for the line is:

class Status extends \IPS\Content\Item implements \IPS\Content\Lockable, \IPS\Content\Hideable, \IPS\Content\Searchable, \IPS\Content\Shareable

You must remove the underscore but keep the space. In the code you posted above, you did the opposite instead (kept the underscore and removed the space).

In any case, even if you correctly update the class name, everything else in the class will still throw errors without updates. The best choice is to simply remove this unnecessary file so the framework won't load it.

  • Author
29 minutes ago, teraßyte said:

The best choice is to simply remove this unnecessary file so the framework won't load it.

That did the trick. Thank you for the help.

  • Community Expert
On 4/26/2025 at 7:49 PM, teraßyte said:

The best choice is to simply remove this unnecessary file so the framework won't load it.

Just curious, shouldn't the upgrader itself remove the aforementioned file? i.e. do a proper clean up by itself.

  • Community Expert

No. The upgrade has never deleted old files. For major upgrades, the best choice is to remove the files yourself (except applications; and previously plugins) and upload a fresh set of all files.

Recently Browsing 0

  • No registered users viewing this page.