Hi, I'm facing a rather weird problem with the guestbook plugin: as soon as it is actived the "edit plugins" page turns empty. Empty means, even the page source is completely empty. I have tried using a custom heading for the guestbook to avoid umlauts and I had a look at the source of the custom text field of the plugin to lock out any unwanted HTML fragments from there. No effort.
Any suggestions?
Edit Plugins page defunct when guestbook is active
Edit Plugins page defunct when guestbook is active
BTW: Ich heisse Tom - "ax11" klingt halt doch etwas seltsam im Gebrauch zwischen Menschen.
Jabber: ax11@jabber.ccc.de
Jabber: ax11@jabber.ccc.de
-
garvinhicking
- Core Developer
- Posts: 30022
- Joined: Tue Sep 16, 2003 9:45 pm
- Location: Cologne, Germany
- Contact:
Re: Edit Plugins page defunct when guestbook is active
Hi!
That blank page usually means there's a fatal PHP error that your webserver configuration hides from you. Can you either enable the php-setting "display_Errors" or see in some logfiles what's happening?
The most usual case is running out of available RAM, then you must remove some plugins or raise the memory limit by your provider.
HTH,
Garvin
That blank page usually means there's a fatal PHP error that your webserver configuration hides from you. Can you either enable the php-setting "display_Errors" or see in some logfiles what's happening?
The most usual case is running out of available RAM, then you must remove some plugins or raise the memory limit by your provider.
HTH,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
Re: Edit Plugins page defunct when guestbook is active
The default for apache is to create a file called error_log in the directory that the script is located. For quite a few servers the file will be located at /home/username/public_html/error_log if you have s9y in another directory it will be in /home/username/public_html/serendipity/error_loggarvinhicking wrote:or see in some logfiles what's happening?
Disabling public errors is a good thing for security, but can make it a hassle to troubleshoot. My personal suggestion is to only have public errors shown if you are doing development work, for production servers turn them off.
PHP error_log
OK, I've got php error logging on my php.ini - and special logfiles active in my httpd.conf. So I'll reinstall the plugin and check the errorlogs as soon as I'll find some time during the not-so-busy hours.
BTW: Ich heisse Tom - "ax11" klingt halt doch etwas seltsam im Gebrauch zwischen Menschen.
Jabber: ax11@jabber.ccc.de
Jabber: ax11@jabber.ccc.de
Solved
OK. It was indeed a memory problem - the 8M that are defined in /etc/php4/php.ini seemed to be not enough for serendipity. As it tried to acquire just little more than 8 megs I just put 16MB there, which seems to do it without affecring anything else on the server.
BTW: Ich heisse Tom - "ax11" klingt halt doch etwas seltsam im Gebrauch zwischen Menschen.
Jabber: ax11@jabber.ccc.de
Jabber: ax11@jabber.ccc.de