• Resolved Pieter

    (@wizzard_)


    There seem to be some issues with your plugin on recent Apache versions (2.4.x). This prevents users to access backups and/or exports. Steps to reproduce:

    • Install and activate the All In One WP Migration plugin.
    • Open the plugin page.
    • Create a new export or a new backup.
    • Go to the backups section and click download on any of the .wpress files.

    All you’ll get is a server error, instead of the requested .wpress file. Meanwhile, the following gets logged into the Apache error logs (IP and domain redacted for privacy):
    [Tue Feb 11 11:33:29.713295 2020] [core:alert] [pid 9439:tid 139924891756288] [client 123.45.67.89] /data/www/example.com/www/wp/wp-content/ai1wm-backups/.htaccess: Invalid command 'Order', perhaps misspelled or defined by a module not included in the server configuration, referer: https://www.example.com/wp/wp-admin/admin.php?page=ai1wm_export
    This is caused by the following section from the .htaccess you are using:

    <Files web.config>
    Order allow,deny
    Deny from all
    </Files>

    As you’ll find on https://httpd.apache.org/docs/2.4/upgrading.html this syntax is incorrect and causing these issues. I’d advise using mod_access_compat to avoid these issues.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Pieter

    (@wizzard_)

    Actually, instead of using mod_access_compat it would be better to use the following .htaccess code, which should work on all servers:

    <Files web.config>
    	# Apache 2.2
    	<IfModule !mod_authz_core.c>
    		Order Deny,Allow
    		Deny from all
    	</IfModule>
    
    	# Apache 2.4
    	<IfModule mod_authz_core.c>
    		Require all denied
    	</IfModule>
    </Files>
    Plugin Author Yani

    (@yaniiliev)

    Thank you, Pieter.
    We have identified the issue and will make a release tommorow to fix it. If you allow I would like to include your name in the changelog.

    Thread Starter Pieter

    (@wizzard_)

    Sure, no problem! Thanks for the quick fix 🙂

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Apache 2.4 compatibility?’ is closed to new replies.