• Resolved webtent

    (@webtent)


    Only on our development site running latest WP 4.6, not a problem on the production server with 4.5.3, both servers run on PHP 7.0.9. Also, this is only happening on mobile devices :-/

    After deactivating all plugins and re-enabling one by one, we seem to have a conflict between Yoast SEO and this plugin. When Yoast SEO is activated, we get:

    [19-Aug-2016 16:36:13 UTC] PHP Fatal error: Uncaught TypeError: Argument 1 passed to Ai1ec_Exception_Handler::handle_exception() must be an instance of Exception, instance of Error given in /www/wp-content/plugins/all-in-one-event-calendar/lib/exception/handler.php:191

    With Yoast SEO deactivated, the error goes away and pages load. We also just upgraded this development site to WordPress 4.6 this morning as well and did not have the issue over the last week while testing.

    https://ww.wp.xz.cn/plugins/all-in-one-event-calendar/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter webtent

    (@webtent)

    Maybe not, I’ve received the error again since when making a syntax error, so perhaps it is uncovering something wrong with a custom script……

    Hi,

    I think you are the first user who reported this conflict, so it is possible that something else causes the issue.

    Thread Starter webtent

    (@webtent)

    Yes, I did find the error appears when any error in the code, but not an error with the plugin itself. For instance, again this morning working on some unrelated code for the same website and received this error in the debug log. If I disable the plugin, I can now see the actual error in my log causing the problem, which was related to using $this out of context in a plugin I was working on. Basically, every time I have an error in my own code, I get the error above instead of the error causing the problem, very frustrating, I have to keep the plugin deactivated on the dev site to avoid while debugging. So, you believe this only happens because of some other custom code?

    It’s hard to know without checking, but since you are the only user who reported the possible conflict, I think something else is causing this.

    Thread Starter webtent

    (@webtent)

    Yes, agreed, especially since we don’t have the issue on the live server. Maybe something to do with HTTP Basic Auth on the dev server, I had one plugin cause an issue with that before. Thanks!

    No problem, glad I could help.

    Take care,
    Ben

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

The topic ‘PHP Fatal Error’ is closed to new replies.