• Resolved cpudoc

    (@cpudoc)


    In the Jetpack panel in admin I am getting this error since installing the beta:

    mysql_real_escape_string() [function.mysql-real-escape-string]: Access denied for user …

    I don’t believe it has any effect outside the Jetpack plugin

Viewing 10 replies - 1 through 10 (of 10 total)
  • It might be worth mentioning this to the Jetpack support team via the plugin’s dedicated sub-forum.

    @cpudoc – mysql_real_escape_string() is not used anywhere in Jetpack, so this is more likely an issue with core.

    mysql_real_escape_string() [function.mysql-real-escape-string]: Access denied for user …

    Can you paste in the full error message so I can take a closer look? Also, what version of Jeptack are you using? Does temporarily deactivating your plugins/theme clear up the message?

    Thanks ??

    Thread Starter cpudoc

    (@cpudoc)

    Here is the full text that appears inside the Site Stats Dashboard Widget:

    Warning: mysql_real_escape_string() [function.mysql-real-escape-string]: Access denied for user '[...]' (using password: NO) in [...]/wp-content/themes/crisp/functions/admin-interface.php on line 111
    
    Warning: mysql_real_escape_string() [function.mysql-real-escape-string]: A link to the server could not be established in [...]/wp-content/themes/crisp/functions/admin-interface.php on line 111

    The […] is the site specific info.

    I see that the code references is in the theme files. The problem definitely goes away when I turn off Jetpack. It also throws a lot of similar errors upon restarting it and trying to get it reconnected.

    Thanks for the response!

    I see that the code references is in the theme files. The problem definitely goes away when I turn off Jetpack. It also throws a lot of similar errors upon restarting it and trying to get it reconnected.

    Looking at the error messages in detail it seems like your theme is the culprit here, with the error message being about how your theme interacts with Jetpack somehow, rather than an issue with the code in the Jetpack plugin itself.

    Have you tried switching your theme to one of the default themes (like Twenty Fourteen) to see if you have the same issue still?

    Thread Starter cpudoc

    (@cpudoc)

    I haven’t, but I will. It was just odd that it started happening once I updated to the 4.0beta bits.

    Thanks again. I’m going to go tinker with it some more.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Using jetpack on the nightlies, I don’t see this issue.

    I’ve tagged the post for Jetpack, but as Jerry said, this is likely your theme more than Beta.

    What version of PHP are you using?

    Thread Starter cpudoc

    (@cpudoc)

    I’m using PHP 5.2 right now. I have opened a a ticket with the Theme folks to see what’s up.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    AHAH! Okay there ARE issues in PHP 5.2 and WP 4.0. Can you possibly try updating to the nightly release? Or … wait till Beta 2 is out soon.

    Thread Starter cpudoc

    (@cpudoc)

    I am getting the nightly releases already.

    I have some work to do to get the blog to 5.4. It doesn’t run cleanly on it yet. Sounds like a good idea to consider doing that though.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    WP should be running okay on 5.2.3 and up, but I can’t speak for ALL themes and plugins. I would very much consider sorting out upgrading, though, since if you’re having problems on 5.4 then it sounds more like a one-off issue with your site and PHP ??

    Tagging resolved as I’m reasonably sure it’s not actually a core issue (and we had others on 5.2 report issues were resolved).

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Error in Jetpack’ is closed to new replies.