• Resolved fotske

    (@fotske)


    Hi,

    After updating WooCommerce to version 5.2.2. on my website, I had this message on my website:

    “Internal Server Error

    The server encountered an internal error or misconfiguration and was unable to complete your request.

    Please contact the server administrator at webmaster to inform them of the time this error occurred, and the actions you performed just before this error.

    More information about this error may be available in the server error log.

    Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.”

    There seems to be a problem with the new version.
    I had to restore a backup of my website.

    Why do I have this problem with version 5.2.2?
    I’m on WordPress 5.7.1, is it compatible?

    Thank you for your help.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Ross V. a11n

    (@rossviviano)

    Automattic Happiness Engineer

    Hi there,

    Usually, this is due to a rogue plugin – If you disable everything except WooCommerce, then update, do you still see the issue?

    Best,

    Ross

    Thread Starter fotske

    (@fotske)

    Hi,

    The problem was coming from the fact that the updating of the WooCommerce plugin made a modification in my .htaccess file and this created an internal server error.

    I detail here the lines of code of the .htaccess files that have been modified by the updating of the plugin:

    THIS IS THE .HTACCESS FILE BEFORE THE UPDATE OF THE WOOCOMMERCE PLUGIN TO VERSION 5.2.2:

    # BEGIN WordPress
    # The directives (lines) between "BEGIN WordPress" and "END WordPress" are
    # dynamically generated, and should only be modified via WordPress filters.
    # Any changes to the directives between these markers will be overwritten.
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    THIS IS THE .HTACCESS FILE AFTER THE UPDATE OF THE WOOCOMMERCE PLUGIN TO VERSION 5.2.2:

    # BEGIN WordPress
    # The directives (lines) between "BEGIN WordPress" and "END WordPress" are
    # dynamically generated, and should only be modified via WordPress filters.
    # Any changes to the directives between these markers will be overwritten.
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
    RewriteBase /en/
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /en/index.php [L]
    </IfModule>

    You can see that it added “/en” at some places.
    How is that possible?
    When I copy the old .htaccess code on my live website, the internal server error disappears.

    You should really try to understand how this could happen to prevent it from happening in future versions of WooCommerce.

    Thank you very much in advance for your answer.

    Thread Starter fotske

    (@fotske)

    Hi again,

    I see that this issue is known : https://wpml.org/errata/htaccess-is-rewritten-with-language-folder/

    It is not due to WPML but it is due to your plugin.
    The webpage that I sent you says: “The problem actually comes from certain third-party plugins calling flush_rewrite_rules(true) function too often.”
    and: “The proper fix is for the third-party plugin to flush the rewrite rules only once.”

    Please take the necessary actions in your plugin to avoid this issue from happening in the future.

    Kind regards

    Plugin Support AW a11n

    (@slash1andy)

    Automattic Happiness Engineer

    Hey again!

    It sounds like the wpml team is aware of the issue, and is looking to get updates out that will solve this.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Problem when updating to version 5.2.2.’ is closed to new replies.