Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author Ahmed Kaludi

    (@ahmedkaludi)

    Hi @validhtml

    That’s extremely strange, can you please let me know if you are using any related posts plugin because I don’t see how it’s coming from our end.

    Can deactivate the plugins to test if that fixes the issue?

    Thread Starter validhtml

    (@validhtml)

    We are using nginx on our site. Maybe the problem with it. We have this problem after letest updates of your plugin.

    Thread Starter validhtml

    (@validhtml)

    On all our sites we have same problem. On all our sites we use nginx.
    [an error occurred while processing the directive]
    This error indicates that an error occurred while processing SSI

    Thread Starter validhtml

    (@validhtml)

    I find the problem. You use this code:
    https://joxi.ru/v29WXk0f3DEkBr?d=1
    <!–#930–>
    When i remove it it works fine. Do you need this code in your file?
    /accelerated-mobile-pages/templates/design-manager/design-2/elements/related-posts.php
    This format <!–#930–> uses for SSI. Can you remove this in your future updates iif it’s not important? Because everyone who uses nginx will have the same problems. THX

    Plugin Author Ahmed Kaludi

    (@ahmedkaludi)

    That’s really helpful of you! I have created a ticket for this: https://github.com/ahmedkaludi/accelerated-mobile-pages/issues/1179

    We will make sure that it gets resolved in the next update.

    Are you having this issue any other place as well?

    Thread Starter validhtml

    (@validhtml)

    This is only one issue what I found and we have it on all sites, because they all using nginx. We will wait for new updates. Thank you very much for your help.

    Plugin Author Ahmed Kaludi

    (@ahmedkaludi)

    Hi @validhtml

    Sure, the next update will be released on 7th Oct. This will be fixed in that one.

    In one of my website on nginx it is showing the below error in amp url, is this same error? will this also be fixed in the next release?
    Screenshot: https://prntscr.com/gs6j5k

    Fatal error: Uncaught Error: Class ‘DOMDocument’ not found in /home/WEBSITE/wp/wp-content/plugins/accelerated-mobile-pages/includes/vendor/amp/includes/utils/class-amp-dom-utils.php:7 Stack trace: #0 /home/WEBSITE/wp/wp-content/plugins/accelerated-mobile-pages/includes/vendor/amp/includes/class-amp-content.php(98): AMP_DOM_Utils::get_dom_from_content(‘<p>WordPress 4….’) #1 /home/WEBSITE/wp/wp-content/plugins/accelerated-mobile-pages/includes/vendor/amp/includes/class-amp-content.php(85): AMP_Content_Sanitizer::sanitize(‘<p>WordPress 4….’, Array, Array) #2 /home/WEBSITE/wp/wp-content/plugins/accelerated-mobile-pages/includes/vendor/amp/includes/class-amp-content.php(46): AMP_Content->sanitize(‘<p>WordPress 4….’) #3 /home/WEBSITE/wp/wp-content/plugins/accelerated-mobile-pages/includes/vendor/amp/includes/class-amp-content.php(22): AMP_Content->transform() #4 /home/WEBSITE/wp/wp-content/plugins/accelerated-mobile-pages/includes/vendor/amp/includes/class-amp-post-template.php(242): AMP_Content->__const in /home/WEBSITE/wp/wp-content/plugins/accelerated-mobile-pages/includes/vendor/amp/includes/utils/class-amp-dom-utils.php on line 7

    Even though the error message is the same, the reasons are different. It is recommended to create a new topic in this case.

    Anyway, your server is missing php-dom and / or php-xml. Please know that it may be named php5-dom, php5.6-dom, php7.0-dom, php7.1-dom or something similar. You may consult with your host on it and to install it.

    @validhtml If you can modify the server configuration, adding the line ssi on; inside the server block would resolve the issue. By default, ssi is turned off in Nginx. More info at https://nginx.org/r/ssi .

    @pothi Thank you so much, installed php7.0-xml fixed the issue.

    Plugin Author Ahmed Kaludi

    (@ahmedkaludi)

    Hi @sathyavpk

    Glad to hear that the issue was fixed

    Thank you @pothi for the help

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘[an error occurred while processing the directive]’ is closed to new replies.