Serendipity Forums

I just upgraded to 1.2.1 and seems I'm no longer able to upgrade plugins. If I press the plugin upgrade button I get

"Trying to open URL package_event_en.xml...
Fetched 257249 bytes from already existing file on your server. Saving file as /www/lynoure.org/blog/templates_c/package_event_en.xml..."

and no upgrading of the plugin seems to happen at all. Similar thing happens when I try to install a new plugin.

What can I do?

Hi!

Do you get no other output after that? If so this sounds like a fatal PHP error, maybe a "out of memory" or so. Can you check your Server's PHP Error log?

Regards,
Garvin

No errors in the log at all, just some unrelated warnings (other people trying some other stuff).

Hi!

If you view the HTML Sourcecode of your page, does it stop in between? OR do you get until the "</html>" part?

You did check the *PHP* (=CGI) error log, not the Apache ErrorLog, which only contains 404 errors, right?

Regards,
Garvin

Seems my PHP logs into apache's log file, at least the warnings I mentioned above were PHP warnings related to s9y*. I checked and I have

error_reporting = E_ALL

in php.ini, that should catch all, unless I'm mistaken.

Just looked at the html code of the page, and no, it does not continue to the </html> but ends with </div> <br /><br />


I'm grateful you are helping me. I'm open to anything that might help, short of throwing away all of my entries.


*) stuff like this, in case you are curious:
[error] PHP Warning: parse_url(/blog/index.php?url=http://evil.spammer.
.example.net/images/cs.txt?) [<a href='function.parse-url'>function.parse-url</a>]: Unable to parse url in /www/lynoure.org/blog/include/functions_permalinks.inc.php on line 713

Hi!

Hm - is your templates_c directory still writable? And does the package_event_em.xml file exist? Try to delete it, and see if it get recreated.

Since the output stops at <br> it means that PHP fatally bails out because of some error. Usually those are firewall or write-error related, so I'm curious why they do not show up in your log. In some cases, coredumps or other things could show up in the provider's syslog file, that might be the last place to look?

If all above fails, if you can give me temporary FTP access to your machine I could add some debug strings to find out what exactly is breaking.

Regards,
Garvin

This is quite a bit embarrassing, I was looking at the wrong log altogether (forgot that the https connections log elsewhere).

Seems that the cause was increased memory use. The php.ini setting memory_limit = 9M was now just barely too small, so it needed to be upped a tiny bit.

Sorry for the hassle. Anything I can do to repay you? (Not just asking to be polite.) Something for Serendipity, perhaps?

Hi!

You're welcome!

You don't need to repay me, that's what I'm here for. We have no official project donation page, only my Amazon Wishlist or Paypal account.

Best regards,
Garvin