No problem. Honestly, this change should have seen more testing, so I was very interested in seeing this resolved.

As a help for others: We figured it out. The site did not have https, and the fallback did not work because the site's baseURL was configured as www.example.com, but visited under example.com. Changing the url or adding a ssl certificate would fix the backend.

That browser is definitely new enough. And the fallback header would also work. If it does not work on multiple browsers like that it has to be related to the server setup (or trigger some bug in serendipity). Though I'm not aware of anything that would explain this, like a setting or something.

I ...

We changed how the XSRF protection works and now rely on a browser header - but the expectation was that the error won't happen then in normal use (no timeouts). Which browser do you use, including the version?

New ones?

In 2.6. there were a couple changes related to thumbnails:

1. Jpeg thumbnails got new creation settings (setting their quality)
2. WebP and AVIF images are supported now, and also have new setting for their creation

But I'd guess what hits you are the responsive images, that the ...

We are happy to announce the availability of the next stable release, Serendipity 2.6.0. It provides support for PHP 8.4 and includes many fixes, updated bundled libraries and some new features, like an optional two factor authentication on login and a faster cache, as well as security fixes for ...

Thanks for reporting back :)

Welche Version lief von s9y lief da genau? 2.6-beta1 oder die Version aus dem Github-Master?

Von der codestelle ist das die gleiche, die bei dee in https://board.s9y.org/viewtopic.php?p=10459895#p10459895 schieflief. Ich hatte das bei mir reproduziert, hängt von der Konfiguration ab, aber im nl2p ...

Schau bitte mal in das PHP error log, welche Fehlermeldung bei dem 500er geloggt wurde. Dann wissen wir mehr.

Aber ja, Plugin als Ursache ist wahrscheinlich.

Right, if you were under PHP 7.4 the bug would not have happened. The code was compatible with it. But the fix will help under PHP 8.

Btw, great to see that Serendipity 2.5.0 still really worked with PHP 7.4! :)

For php-intl, exactly. That's for the server hoster to activate. I'm surprised it isn ...

And was that under PHP 7.4, where it worked before, or did you switch back to PHP 8, the bug occurred and changing line 261 to array() fixed it? Edit: Doesn't matter anymore, I could reproduce the bug. Yes, changing false to array() in line 261 fixes that problem. I committed that fix as well to the ...

The plugin has two modes of operation, nl2br and nl2p. I assume you used nl2p before - line 737 is part of the nl2p function. When you uninstalled the plugin it probably reset the configuration, and now your blogs uses nl2br mode. Change it in the plugin configuration, set "Use P-Tags" to "Yes ...

For the log, exporting an RSS file was a good option. One would have to check the error message that would have been logged when the 500 error occured to see what went wrong. Maybe a timeout.

And exporting the database would also work, like you tried. The text is in the body column, but you could ...

Super. Zeig hier vll den diff der Änderungen an der mysqli.inc.php, damit du es dokumentiert hast und wir schauen können was genau nötig war. Vielleicht hilft es auch jemandem.

Please :) Ideal would be both, but I guess most important is the error you run into now. Then we can probably fix it.