• like your code is using an __autoload() function. log4php uses spl_autoload_register() which will bypass your __autoload() function and may break autoloading. in /home/kentexca/public_html/blog/wp-content/plugins/fb-instant-articles/vendor/apache/log4php/src/main/php/LoggerAutoloader.php on line 22

    Messed my website

Viewing 1 replies (of 1 total)
  • Hi @portalshops. Thanks for submitting a review. We’ve been slow to respond because we are short-staffed to keep up with all activity in the community but we do care about difficulties you are having and we’ll try our best to resolve issues that may be caused by our plugin.

    This warning message you received comes from the Apache log4php logging framework which our plugin uses. More specifically, line 22 of the LoggerAutoloader.php file.

    It is obviously conflicting with something else in your WordPress installation. Perhaps another plugin? It might be difficult to track exactly what other part of your WordPress environment is causing the conflict.

    Can you tell me a little more about your WordPress installation environment?

    1. Is it installed on a shared environment?
    2. How many other plugins do you have installed?
    3. Are you able to disable error and warning messages?

    I think we could actually solve this problem based on your answer to #3 above. The reason is: this is purely a warning message. Most production environments have warning/error messages disabled so this could safely be occurring and the plugin would still likely work if the message isn’t showing. There is an interesting discussion around this being “just a warning message” here. Let me know what you think.

    Thanks again for sharing your experience so far and we hope we can improve things for you as soon as possible.

    • This reply was modified 7 years, 6 months ago by Paulo.
    • This reply was modified 7 years, 6 months ago by Paulo. Reason: link formatting
Viewing 1 replies (of 1 total)
  • The topic ‘Garbage plugin’ is closed to new replies.