Database error – re comments entered via neo

  • Anonymous

    #7742

    I am seeing error messages as per error log extract below. Comments appear to work OK in graphene and in graphene NEO.

    However, those entered through NEO generate error messagess. Support forum shows a fix for a similar error to this one, but it is only for graphene and not for NEO.

    http://www.papamayhem.com

    using WordPress 3.5.2. Graphene 1.9 Neo 1.4 (I have checked database with mysql and it is OK)

    The “SELECT stuff” is in the error log once, followed by many entries entries like the one below which is preceded by a datestamp.

    EXTRACT FROM ERROR LOG

    SELECT

    COUNT(comment_ID)

    FROM

    wp_comments

    WHERE

    comment_type = “” AND comment_approved=”1″ AND comment_parent=”0″ AND

    comment_post_ID= made by require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), include(‘/themes/graphene/category.php’), get_header, locate_template, load_template, require_once(‘/themes/graphene/header.php’), wp_head, do_action(‘wp_head’), call_user_func_array, wp_enqueue_scripts, do_action(‘wp_enqueue_scripts’), call_user_func_array, graphene_localize_scripts, graphene_get_comment_count

    [10-Jul-2013 09:24:32] WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘LIMIT 1’ at line 1 for query SELECT post_id FROM wp_postmeta WHERE meta_key like “_menu_item_menu_item_parent” AND meta_value= LIMIT 1 made by require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), include(‘/themes/graphene-mobile-neo/single.php’), get_header, locate_template, load_template, require_once(‘/themes/graphene-mobile-neo/header.php’), gmneo_dropdown_menu, wp_nav_menu, call_user_func, gmneo_default_menu, wp_list_pages, walk_page_tree, call_user_func_array, Walker->walk, Walker->display_element, call_user_func_array, GMNeo_Default_Select_Menu_Walker->start_el, apply_filters(‘nav_menu_css_class’), call_user_func_array, gmneo_add_ancestor_class

    Admin

    Syahir Hakim

    #39206

    OK, we’ll fix this in the next update. In the mean time, the solution outlined for Graphene here would apply for GM Neo as well:

    https://forum.graphene-theme.com/bug-report/wordpress-database-error-since-upgrading-to-wordpress-352

    Anonymous

    #39207

    I implemented your suggestion. It stops the “SELECT stuff” from appearing in the error log. THANK YOU.

    However – I am still seeing the messages about database error. I see 50 lines just like the following one:

    [10-Jul-2013 17:38:41] WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘LIMIT 1’ at line 1 for query SELECT post_id FROM wp_postmeta WHERE meta_key like “_menu_item_menu_item_parent” AND meta_value= LIMIT 1 made by require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), include(‘/themes/graphene-mobile-neo/single.php’), get_header, locate_template, load_template, require_once(‘/themes/graphene-mobile-neo/header.php’), gmneo_dropdown_menu, wp_nav_menu, call_user_func, gmneo_default_menu, wp_list_pages, walk_page_tree, call_user_func_array, Walker->walk, Walker->display_element, call_user_func_array, GMNeo_Default_Select_Menu_Walker->start_el, apply_filters(‘nav_menu_css_class’), call_user_func_array, gmneo_add_ancestor_class

    Admin

    Syahir Hakim

    #39208

    OK, that’ll be fixed in the next update as well.

Viewing 4 posts - 1 through 4 (of 4 total)

  • You must be logged in to reply to this topic.