• JaxJames

    (@jaxjames1)


    Hello, my client is using a translation plugin that requires PHP files to be executed in a directory that Sucuri blocks by default when activating all “hardening” features.

    For some reason, the Allow Blocked PHP Files section in the Sucuri plugin sections doesn’t allow you to simply enter the entire path of the file, so I need to know how to add the following files to the allow list:

    • /wp-content/plugins/gtranslate/url_addon/gtranslate.php
    • /wp-content/plugins/gtranslate/url_addon/config.php

    Sucuri only seems to give /wp-content as a directory option.
    Any help is greatly appreciated.

Viewing 2 replies - 16 through 17 (of 17 total)
  • Thread Starter JaxJames

    (@jaxjames1)

    Hi @sucuri1 , is there an update on this? This is still causing the 403 issue.

    There was no .htaccess file in the /wp-content directory, so I just created a new file and entered the code provided.

    Here’s the /wp-content/.htaccess file content:

    <FilesMatch "^(gtranslate.php|config.php)$">
    Allow from all
    </FilesMatch>

    Is there anything incorrect in this?

    Thread Starter JaxJames

    (@jaxjames1)

    Hi @sucuri1 , is there an update to this yet?

Viewing 2 replies - 16 through 17 (of 17 total)
  • You must be logged in to reply to this topic.