WordPress.org

Ready to get started?Download WordPress

Forums

Google Sitemaps Error (5 posts)

  1. dinhluong
    Member
    Posted 6 years ago #

    I get a plain screen with this error every time I try to publish or save a post:

    "Warning: mysql_fetch_object(): 135 is not a valid MySQL result resource in /home/.maricara/dinhluong/dinhternet.com/wp-content/plugins/google-sitemap-generator/sitemap.php on line 2075

    Warning: Cannot modify header information - headers already sent by (output started at /home/.maricara/dinhluong/dinhternet.com/wp-content/plugins/google-sitemap-generator/sitemap.php:2075) in /home/.maricara/dinhluong/dinhternet.com/wp-includes/pluggable.php on line 390"

    The "Publish" button seems to work, but "Save"d drafts disappear.

  2. arnee
    Member
    Posted 6 years ago #

    Hi,

    Could you post a list of other plugins you have currently activated? Maybe one of them doesn't use the WordPress API to make MySQL queries.

    Best regards,

    Arne

  3. dinhluong
    Member
    Posted 6 years ago #

    I believe the conflict is with Popularity Contest. I changed the scoring system to Comment Count instead of Popularity Contest and no longer get the error.

  4. dinhluong
    Member
    Posted 6 years ago #

    Oh, and I was just informed by a reader that after he posted a comment, he got this error message:

    "Warning: mysql_query() [function.mysql-query]: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) in /home/.maricara/dinhluong/dinhternet.com/wp-content/plugins/popularity-contest.php on line 544

    Warning: mysql_query() [function.mysql-query]: A link to the server could not be established in /home/.maricara/dinhluong/dinhternet.com/wp-content/plugins/popularity-contest.php on line 544
    Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) on line: 544"

    I still have both plugins activated, but Google Sitemaps Generator shouldn't be using Popularity Contest anymore.

  5. ultramalcolm
    Member
    Posted 6 years ago #

    I am getting this error as well, the one on line 544. Is this a conflict with Google Sitemaps? Updating to the latest version of the plugin didn't seem to help. Any ideas?

Topic Closed

This topic has been closed to new replies.

About this Topic