-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
s9y current master: language constants already defined #798
Comments
@fe-hicking Could this be related to the upgrader fixes? |
I don't see how my commits should cause this; they don't affect the normal operation? @bauigel maybe you can roll back to master before my commits, see if that changes. To me it looks like the language handler is the culprit; I remember it being called multiple times for fallback - maybe a check is missing for an existing constant?! |
If I go back to 2.4.0 release everything works like a charm again. Seems the errors depends on changes in the meantime. |
Hmm...nothing like a charm. Maybe there has been a cache shown? Now I get a 500 on start page with 2.4.0. The admin page still works. |
2.4.0 release has no extra debugging. You might see the same error like before. What are your language settings, especially charset related? Check serendipity_config_local.inc.php and the serendipity_config table for authorid=0....? |
Could it be you're using PHP 8.1? I'm not sure s9y is compatible with PHP 8.1 yet? The lang framework uses @onli Do you know something about the 8.1 compatibility? |
At least from the official documentation, I don't see a deprecation for Best regards, |
I just checked, a simple PHP:
only raises a warning on PHP 8.1. I also checked with PHP 8.2RC3 and there also only a warning is issued. And suppressing a warning with
So basically, the error with a
should never throw such an uncaught exception from a warning. The only way I imagine it erroring is, if the code at some point calls @bauigel Could you search your deployed code for Regards, |
For now I'm only aware of #784 and that in https://board.s9y.org/viewtopic.php?t=25716 commenting stopped working with PHP 8.1. PS: I only thought the last fixes could be related because of the utf8mb4 thing, that maybe now an upgrade task works again that sets the LANG_CHARSET in some file. I had no specific code in mind though that could be responsible. |
FYI : PHP 8.0
As far as I can see, every define has an @ in front. My config:
|
Funny. In my backend I get another error message...
|
To be sure, my installation is not broken, I switched back to php 7.4 and everything works fine. Seems to be an php 8 issue. |
The backend JS-Error is just if you open said URL in a window you'll see the PHP error message you get in the frontend, so that's expected. I don't know how to debug this. Are you maybe able to setup a copy of the installation and temporarily give me SSH access to it, so I could debug stuff? Or maybe in a ddev/virtualbox VM image... |
I can reproduce with
|
Putting Anyway, the error handling should be rewritten. The S9Y error handler is currently hard to understand (see Technical debts) and should be rewritten. Setting |
With current master (4.12.2022) I get a lot of errors and warnings and the webpage doesn't run. Following you will find the debug log.
The text was updated successfully, but these errors were encountered: