• Resolved duanthse03268

    (@duanthse03268)


    i got 500 error with the tickets setting cannot access to all the page in tickets setting
    …./wp-admin/edit.php?post_type=ticket

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author melliesou

    (@melliesou)

    Hi @duanthse03268,

    Did you make any changes prior to the 500 error code appearing? If possible can you revert any changes and see if that solves the issue? If that isn’t an option or doesn’t solve the issue, can you enable debug mode:
    https://codex.ww.wp.xz.cn/Debugging_in_WordPress
    Once debug mode is enabled, can you report any relevant rows from the logfile? /wp-content/debug.log

    Hope this helps, and let me know if you find anything in the log file on debug mode.

    Thread Starter duanthse03268

    (@duanthse03268)

    this is log on my site

    [07-Jan-2019 05:37:41 UTC] PHP Notice: is_preview was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in D:\home\site\wwwroot\wp-includes\functions.php on line 4204
    [07-Jan-2019 05:37:41 UTC] PHP Notice: is_singular was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in D:\home\site\wwwroot\wp-includes\functions.php on line 4204
    [07-Jan-2019 05:37:41 UTC] PHP Notice: is_preview was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in D:\home\site\wwwroot\wp-includes\functions.php on line 4204
    [07-Jan-2019 05:37:41 UTC] PHP Notice: is_singular was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in D:\home\site\wwwroot\wp-includes\functions.php on line 4204
    [07-Jan-2019 05:37:41 UTC] PHP Fatal error: Uncaught Error: Call to a member function get() on null in D:\home\site\wwwroot\wp-includes\query.php:28
    Stack trace:
    #0 D:\home\site\wwwroot\wp-content\plugins\ht-knowledge-base\ht-knowledge-base.php(1511): get_query_var(‘ht_kb’)
    #1 D:\home\site\wwwroot\wp-includes\class-wp-hook.php(286): HT_Knowledge_Base->ht_kb_modify_kb_preview_pre_get_posts(Object(WP_Query))
    #2 D:\home\site\wwwroot\wp-includes\class-wp-hook.php(310): WP_Hook->apply_filters(NULL, Array)
    #3 D:\home\site\wwwroot\wp-includes\plugin.php(515): WP_Hook->do_action(Array)
    #4 D:\home\site\wwwroot\wp-includes\class-wp-query.php(1634): do_action_ref_array(‘pre_get_posts’, Array)
    #5 D:\home\site\wwwroot\wp-includes\class-wp-query.php(3230): WP_Query->get_posts()
    #6 D:\home\site\wwwroot\wp-includes\class-wp-query.php(3336): WP_Query->query(Array)
    #7 D:\home\site\wwwroot\wp-content\plugins\awesome-support\includes\functions-post.php(550): WP_Query->__construct(Array)
    #8 D:\home\site\wwwroot\wp-content\plugins\awesome-support\includes\admin\functions-mi in D:\home\site\wwwroot\wp-includes\query.php on line 28

    Thread Starter duanthse03268

    (@duanthse03268)

    I didn’t made any change to your plugin

    Plugin Author melliesou

    (@melliesou)

    Hi @duanthse03268,

    Are you using the latest version of the plug-in? Can you also try loading with other plug-ins temporarily turned off and see if that fixes the error and then re-enable the other plug-ins until you find the conflict? (I think it might be cause by another knowledgebase plug-in based on the error message from your logs.

    Thread Starter duanthse03268

    (@duanthse03268)

    ok i think it was caused by other plugins thank you

    Plugin Author melliesou

    (@melliesou)

    Ok, thanks for confirming that it was caused by a different plug-in. I’ll mark this thread as resolved. Let us know if you have any other questions.

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

The topic ‘Error 500 on Plugin Pannel’ is closed to new replies.