• [26-Apr-2015 15:06:11 UTC] PHP Fatal error: Uncaught exception ‘Exception’ with message ‘Should not happen: User is not logged in’ in /home/xxxxxx/public_html/wp-content/plugins/key4ce-osticket-bridge/osticket-wp.php:141
    Stack trace:
    #0 /home/xxxxxx/public_html/wp-content/plugins/key4ce-osticket-bridge/templates/contact_ticket.php(20): require_once()
    #1 /home/xxxxxx/public_html/wp-content/plugins/key4ce-osticket-bridge/ost-bridge.php(69): require_once(‘/home/xxxxxx/…’)
    #2 [internal function]: addcontact(”, ”, ‘addoscontact’)
    #3 /home/xxxxxx/public_html/wp-includes/shortcodes.php(286): call_user_func(‘addcontact’, ”, ”, ‘addoscontact’)
    #4 [internal function]: do_shortcode_tag(Array)
    #5 /home/xxxxxx/public_html/wp-includes/shortcodes.php(200): preg_replace_callback(‘/\\[(\\[?)(embed|…’, ‘do_shortcode_ta…’, ‘<p>[addoscontac…’)
    #6 [internal function]: do_shortcode(‘<p>[addoscontac…’)
    #7 /home/xxxxxx/public_html/wp-includes/plugin.php(213): call_user_func_array(‘do_shortcode’, Array)
    #8 /home/xxxxxx/public_html/wp-includes/post in /home/xxxxxx/public_html/wp-content/plugins/key4ce-osticket-bridge/osticket-wp.php on line 141

    https://wordpress.org/plugins/key4ce-osticket-bridge/

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author m.tiggelaar

    (@mtiggelaar)

    Can you provide more information other then the error you receive?

    Meaning:
    osticket version
    plugin version
    wp version

    –> and how you produce the error.

    Thread Starter Interpolat Solutions

    (@jmdziba)

    I am using

    osTicket (v1.9.7)
    Plugin Version 1.2.9
    Wordpress Version 4.2

    Plugin Author m.tiggelaar

    (@mtiggelaar)

    Alright,
    i haven’t tested our plugin with wp 4.2 yet

    you get this error in general or doing something specific?

    Thread Starter Interpolat Solutions

    (@jmdziba)

    just noticed the error in the log. Also my hosting company is saying there are issues with the osticket database. Not sure what specifically.

    Thread Starter Interpolat Solutions

    (@jmdziba)

    Anything?

    Plugin Author m.tiggelaar

    (@mtiggelaar)

    No news on this issue sorry.
    We did check it out but so far unable to reproduce even with all error logging on.

    (fresh install of osticket / our plugin).

    We did find one thing that produces a notification in logs that we fixed up (did not yet publish that fix as it’s minor).

    my wordpress site is rodbarry.org/myblog and when I try to get to blog I see the following below:

    Fatal error: Uncaught exception ‘AWeberAPIException’ with message ‘Account Unauthorized. https://labs.aweber.com/docs/troubleshooting#unauthorized&#8217; in /home3/rodney/public_html/myblog/wp-content/plugins/pmpro-aweber/includes/aweber_api/oauth_application.php:478 Stack trace: #0 /home3/rodney/public_html/myblog/wp-content/plugins/pmpro-aweber/includes/aweber_api/oauth_application.php(119): OAuthApplication->makeRequest(‘GET’, ‘https://api.awe…&#8217;, Array) #1 /home3/rodney/public_html/myblog/wp-content/plugins/pmpro-aweber/includes/aweber_api/aweber.php(249): OAuthApplication->request(‘GET’, ‘/accounts’) #2 /home3/rodney/public_html/myblog/wp-content/plugins/pmpro-aweber/pmpro-aweber.php(57): AWeberAPI->getAccount(‘AgELRUhtayJcGkg…’, ‘V6FMwerZ39P5qGl…’) #3 [internal function]: pmproaw_init(”) #4 /home3/rodney/public_html/myblog/wp-includes/plugin.php(525): call_user_func_array(‘pmproaw_init’, Array) #5 /home3/rodney/public_html/myblog/wp-settings.php(392): do_action(‘init’) #6 /home3/rodney/public_html/myblog/wp-config.p in /home3/rodney/public_html/myblog/wp-content/plugins/pmpro-aweber/includes/aweber_api/oauth_application.php on line 478
    Please help!

    Plugin Author m.tiggelaar

    (@mtiggelaar)

    Hello,

    Your error isn’t related to our plugin but to the plugin: aweber_api
    if you just rename the directory it should automatically disable allowing you to log back into your wordpress setup.

    Regards,
    Marco

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

The topic ‘Fatal Error in WP error.log’ is closed to new replies.