Database Error Not Displaying Bugs

  • Resolved jackofallvices

    (@jackofallvices)


    9 years, 6 months ago

    Hi,
    I installed your plugin, and everything on the reporting end works fine.

    However, when going to the bugs page to display the bugs, i get database errors from my apache log and nothing but the report a bug and filter options appear. The submitted bugs do not appear when filtered either. Here is the output from the apache log

    [Thu Sep 10 14:52:45.682962 2015] [fcgid:warn] [pid 18324] [client 127.0.0.1:1024] mod_fcgid: stderr: 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 '52,44 and ttt.term_id = 43,53,54,55,56 and ttpr.term_id = 45,57,58 order by bugs' at line 1 for query SELECT count(*), tpr.name as priorityname FROM wp_posts bugs LEFT JOIN wp_term_relationships trp ON bugs.ID = trp.object_id LEFT JOIN wp_term_taxonomy ttp ON trp.term_taxonomy_id = ttp.term_taxonomy_id LEFT JOIN wp_terms pt ON ttp.term_id = pt.term_id LEFT JOIN wp_term_relationships trs ON bugs.ID = trs.object_id LEFT JOIN wp_term_taxonomy tts ON trs.term_taxonomy_id = tts.term_taxonomy_id LEFT JOIN wp_terms st ON tts.term_id = st.term_id LEFT JOIN wp_term_relationships trt ON bugs.ID = trt.object_id LEFT JOIN wp_term_taxonomy ttt ON trt.term_taxonomy_id = ttt.term_taxonomy_id LEFT JOIN wp_terms tt ON ttt.term_id = tt.term_id LEFT JOIN wp_term_relationships trpr ON bugs.ID = trpr.object_id LEFT OUTER JOIN wp_term_taxonomy ttpr ON trpr.term_taxonomy_id = ttpr.term_taxonomy_id LEFT OUTER JOIN wp_terms tpr ON ttpr.term_id = tpr.term_id WHERE bugs.post_type = 'bug-library-bugs' AND ttp.taxonomy = 'bug-library-products' AND tts.taxonomy = 'bug-library-status' AND ttt.taxonomy = 'bug-library-types' AND ttpr.taxonomy = 'bug-library-priority' AND pt.term_id in ('42,46,47,48,49,50,59,60')  and tts.term_id = 51,52,44 and ttt.term_id = 43,53,54,55,56 and ttpr.term_id = 45,57,58 order by bugs.post_date DESC made by require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/themes/spacious/page.php'), get_template_part, locate_template, load_template, require('/themes/spacious/content-page.php'), the_content, apply_filters('the_content'), call_user_func_array, do_shortcode, preg_replace_callback, do_shortcode_tag, call_user_func, bug_library_plugin->bug_library_func, bug_library_plugin->BugLibrary, referer: https://mysite.com/bugs/
[Thu Sep 10 14:52:45.682998 2015] [fcgid:warn] [pid 18324] [client 127.0.0.1:1024] mod_fcgid: stderr: 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 '52,44 and ttt.term_id = 43,53,54,55,56 and ttpr.term_id = 45,57,58 order by bugs' at line 1 for query SELECT bugs.*, UNIX_TIMESTAMP(bugs.post_date) as bug_date_unix, pt.name as productname, pt.term_id as pid, st.name as statusname, st.term_id as sid, tt.name as typename, tt.term_id as tid, pt.slug as productslug, st.slug as statusslug, tt.slug as typeslug, tpr.name as priorityname FROM wp_posts bugs LEFT JOIN wp_term_relationships trp ON bugs.ID = trp.object_id LEFT JOIN wp_term_taxonomy ttp ON trp.term_taxonomy_id = ttp.term_taxonomy_id LEFT JOIN wp_terms pt ON ttp.term_id = pt.term_id LEFT JOIN wp_term_relationships trs ON bugs.ID = trs.object_id LEFT JOIN wp_term_taxonomy tts ON trs.term_taxonomy_id = tts.term_taxonomy_id LEFT JOIN wp_terms st ON tts.term_id = st.term_id LEFT JOIN wp_term_relationships trt ON bugs.ID = trt.object_id LEFT JOIN wp_term_taxonomy ttt ON trt.term_taxonomy_id = ttt.term_taxonomy_id LEFT JOIN wp_terms tt ON ttt.term_id = tt.term_id LEFT JOIN wp_term_relationships trpr ON bugs.ID = trpr.object_id LEFT OUTER JOIN wp_term_taxonomy ttpr ON trpr.term_taxonomy_id = ttpr.term_taxonomy_id LEFT OUTER JOIN wp_terms tpr ON ttpr.term_id = tpr.term_id WHERE bugs.post_type = 'bug-library-bugs' AND ttp.taxonomy = 'bug-library-products' AND tts.taxonomy = 'bug-library-status' AND ttt.taxonomy = 'bug-library-types' AND ttpr.taxonomy = 'bug-library-priority' AND pt.term_id in ('42,46,47,48,49,50,59,60')  and tts.term_id = 51,52,44 and ttt.term_id = 43,53,54,55,56 and ttpr.term_id = 45,57,58 order by bugs.post_date DESC LIMIT 0, 11 made by require('wp-blog-header.php'), require_once('wp-includ, referer: https://mysite.com/bugs/
[Thu Sep 10 14:52:45.709009 2015] [fcgid:warn] [pid 18324] [client 127.0.0.1:1024] mod_fcgid: stderr: es/template-loader.php'), include('/themes/spacious/page.php'), get_template_part, locate_template, load_template, require('/themes/spacious/content-page.php'), the_content, apply_filters('the_content'), call_user_func_array, do_shortcode, preg_replace_callback, do_shortcode_tag, call_user_func, bug_library_plugin->bug_library_func, bug_library_plugin->BugLibrary, referer: https://mysite.com/bugs/

    any ideas of how to fix this? I guess I could use it for reporting bugs initially because I get the info in the admin section, but I would prefer to follow up and close and such so I don’t have to explain things individually.

    my active plugins are as follows (WP Super cache is active but currently disabled)

    `
    AG Custom Admin
    Version 1.4.8.2 | By Argonius

    All In One WP Security
    Version 3.9.9 | By Tips and Tricks HQ, Peter, Ruhul, Ivy

    bbP topic count
    Version 1.3.1 | By Robin Wilson

    bbPress
    Deactivate | Settings | About
    Version 2.5.8 | By The bbPress Community

    bbPress Multi Image Uploader
    Version 1.0.3 | By Ankit Gade |

    bbPress Notices
    Version 1.0.1 | By Pippin Williamson |

    BuddyPress
    Version 2.3.3 | By The BuddyPress Community |

    BuddyPress Forum Editor
    Version 1.0 | By Taehan Lee |

    Bug Library
    Version 1.3.9 | By Yannick Lefebvre

    Coming soon and Maintenance mode WpDevArt
    Version 2.1.2 | By maintenance mode GG, wpdevart, big ben keeper

    Content Aware Sidebars
    Version 2.6.3 | By Joachim Jensen, Intox Studio |

    Featured Post Widget
    Version 4.1.2 | By Waldemar Stoffel

    GD bbPress Tools
    Version 1.7.1 | By Milan Petrovic |

    Jetpack by WordPress.com
    Version 3.7 | By Automattic |

    Merge + Minify + Refresh
    Version 1.5.1 | By Launch Interactive |

    Redis Object Cache
    Version 1.2 | By Till Krüss |

    Remove Dashboard Access
    Version 1.1.3 | By Drew Jaynes (DrewAPicture) |

    rtMedia for WordPress, BuddyPress and bbPress
    Version 3.8.16 | By rtCamp |

    Scrollbar Designer
    Version 1.0 | By Zia Imtiaz |

    Steam News Widget
    Version 1.1.1 | By Softsultant |

    Use Google Libraries
    Version 1.6.2.1 | By Jason Penney |

    WP Change Default From Email
    Version 1.1.0 | By Subodh Ghulaxe |

    WP Clone by WP Academy
    Version 2.1.8 | By WP Academy |

    WP Super Cache
    Version 1.4.4 | By Automattic |

    WP ULike
    Version 2.3 | By Ali Mirzaei |

    WPS Hide Login
    Version 1.1.2 | By WPServeur

    Theme is Spacious V1.3.3 FREE https://themegrill.com/themes/spacious/
    https://www.ads-software.com/plugins/bug-library/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter jackofallvices

    (@jackofallvices)

    I disabled all the parameters in the shortcode and it seems to be working now. Will test further, but I would like to display the descriptions (which is what I assume your parameters would display). If I am misunderstanding, please elaborate on what functionality I lose omitting that.

    Thanks

    Plugin Author Yannick Lefebvre

    (@jackdewey)

    Ah, I see. That would explain it. There are 4 parameters that can be send to the shortcode. Namely, bugcategorylist, a comma-separated list of categories, bugtypeid to only display bugs of certain types, bug statusid and bugpriorityid.

    To see the descriptions, you can click on the bugs to see their full page where the description will be displayed.

    Let me know if you have other questions.

    Please consider supporting this plugin’s development.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Database Error Not Displaying Bugs’ is closed to new replies.