Problem with DMSGuestbook on WordPress 3.0

  • Resolved reedjholmes

    (@reedjholmes)


    15 years, 12 months ago

    Hi there,

    First off, thanks for a great plugin.

    I realize it’s not compatible up to WP 3.0 yet, however, I updated one of my websites yesterday and received this error when I tried to delete a guestbook entry:

    Warning: session_start() [function.session-start]: Cannot send session cache limiter – headers already sent (output started at /home/motor/public_html/wp-content/plugins/dmsguestbook/admin.php:3425) in /home/motor/public_html/wp-content/plugins/eshop/eshop.php on line 914

    WordPress suggests the error would be related to DMS (see “How do I solve the Headers already sent warning problem?” on this page: http://codex.ww.wp.xz.cn/FAQ_Troubleshooting)

    According to WordPress, the error is likely on line 3425 of admin.php. The error seems to be interfering with another plugin I use called eshop, which is compatible with WP 3.0.

    I tried to remove any hidden spaces around the code, but was unable to fix the problem.

    Any help would be much appreciated. Thanks.

    Reed

    P.S. I should note that the entry was deleted and it does not appear as though my eshop was negatively affected.

    http://ww.wp.xz.cn/extend/plugins/dmsguestbook/

Viewing 8 replies - 1 through 8 (of 8 total)
  • DanielSchurter

    (@danielschurter)

    15 years, 12 months ago

    Hi reedjholmes

    I’ve installed WP 3.0, eshop 5.4.1 and DMSGuestbook 1.16.0 on my testing environment and no error occurred by deleting any guestbook messages, even when I set error_reporting(E_ALL | E_STRICT); on admin.php.

    Are you using DMSGuestbook in the latest version?

    Greetings,
    Dani

    Thread Starter reedjholmes

    (@reedjholmes)

    15 years, 12 months ago

    Hi Dani, thank you for your response.

    Yes, I’m using the latest version of DMSGuestbook (1.16.0) and eshop (5.4.1).

    When I deactivated eshop, I did not get the error when I deleted an entry from DMS.

    I think this is unrelated, but I did get this error when I activated the latest version of a plugin called cforms II (http://www.deliciousdays.com/cforms-plugin/):

    “The plugin generated 569 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.”

    I tired deactivating the plugin but when I tried to delete an entry from DMS I still got:

    Warning: session_start() [function.session-start]: Cannot send session cache limiter – headers already sent (output started at /home/motor/public_html/wp-content/plugins/dmsguestbook/admin.php:3425) in /home/motor/public_html/wp-content/plugins/eshop/eshop.php on line 914

    Reed

    DanielSchurter

    (@danielschurter)

    15 years, 12 months ago

    Hi reedjholmes

    There is a problem when developers are writing code with an editor where using utf-8 and BOM (Byte Order Mark).

    I’ve checked this on my editor (Notepad++) and I’m using ANSI not utf-8. Otherwise it would looks like this: \xef\xbb\xbf<?php at the beginning of admin.php when you open that file with a editor like “vi”.

    Greetings,
    Dani

    Thread Starter reedjholmes

    (@reedjholmes)

    15 years, 12 months ago

    Hi Dani,

    So, what are you suggesting I do?

    Thanks.

    Reed

    DanielSchurter

    (@danielschurter)

    15 years, 11 months ago

    Hi reedjholmes

    This could help you:
    1.) Check with an texteditor like “vi” admin.php (dmsguestbook) and eshop.php whether there are chars like \xef\xbb\xbf at the beginning of file.
    2.) Check in your FTP program that data upload is set on binary and not text stream.

    Greetings,
    Dani

    Thread Starter reedjholmes

    (@reedjholmes)

    15 years, 11 months ago

    Hi Dani,

    I checked both files using the vi command on PuTTY.

    There were no strange characters at the beginning of the files.

    Thanks again for your help.

    Reed

    DanielSchurter

    (@danielschurter)

    15 years, 11 months ago

    Hi reedjholmes

    If you don’t want to see the error any longer you can disable it by set
    error_reporting(0); on the admin.php file after the <?php code.

    This command will only hide the notice.

    Greetings,
    Dani

    Thread Starter reedjholmes

    (@reedjholmes)

    15 years, 11 months ago

    Thanks Dani.

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘Problem with DMSGuestbook on WordPress 3.0’ is closed to new replies.