Incompatible with Translate press
-
The plugin is quite heavy and makes conflict with translate press. Variations and titles of products disappeared in the second language. After disabling all is back to normal.
-
Hello @leopap,
To better understand and address the conflict you are experiencing between our plugin and Translate Press, we ask that you create a support topic with more detailed information. This will allow our team to thoroughly investigate the issue of product variations and titles disappearing in the second language.
If you are a SiteGround customer, you can also consider contacting our support team through the Help Desk in your Client Area.
Best Regards,
Daniela IvanovaTo elaborate further on the conflict with TranslatePress, the issue seems specifically tied to one of this security plugin’s core protection features – the one designed to ‘Lock and Protect System Folders.’ While this is a valuable security concept, its implementation caused significant problems with TranslatePress on my site.
When this ‘Lock and Protect System Folders’ feature was enabled, it consistently blocked a crucial AJAX file belonging to TranslatePress (specifically,
wp-content/plugins/translatepress-multilingual/includes/trp-ajax.php). This block resulted in Apache server errors logged asAH01630: client denied by server configuration, and as noted, it impacted the display of translated content like product variations and titles.Following the plugin provider’s own official documentation on “Custom Filters” (specifically the guide found at
https://my.siteground.com/support/tutorials/wordpress/security-optimizer/filtri-personalizzati/), I attempted to whitelist this legitimate TranslatePress file using the suggested PHP filter hook,sgs_whitelist_wp_content. This was done by adding the recommended PHP snippet (via Fluent Snippets, ensuring it was active and all caches were cleared after each change).Unfortunately, despite meticulous attempts and trying various formats for the file path within the whitelist array:
- The full relative path from the
wp-contentdirectory (i.e.,'plugins/translatepress-multilingual/includes/trp-ajax.php'). - Just the base filename (i.e.,
'trp-ajax.php'), following a literal interpretation of the simplified examples in the provider’s guide.
None of these documented methods successfully whitelisted the file. The
trp-ajax.phpfile continued to be blocked, and theAH01630errors persisted as long as the “Lock and Protect System Folders” feature remained active.Interactions with the provider’s AI support channels were also unhelpful in resolving this, as the AI primarily reiterated the same documented solutions that had already been tried and proven ineffective in this specific scenario.
Ultimately, the only way to restore full TranslatePress functionality and eliminate the server errors was to completely disable the “Lock and Protect System Folders” feature. This is a significant drawback, as it forces users to sacrifice a key security hardening feature to ensure compatibility with other widely-used and legitimate plugins.
This experience indicates a potential issue with the
sgs_whitelist_wp_contentfilter’s effectiveness for files nested within plugin directories, or that the official documentation is insufficiently detailed or misleading for such common real-world use cases. For a security plugin, having a reliable and clearly documented method for whitelisting legitimate files is crucial. I hope the developers will look into this to improve compatibility and the user experience when customizing these security features.”Regarding your suggestion to “create a support topic” or “contact our support team through the Help Desk,” this raises a pertinent question about how SiteGround handles feedback on its own products, like the Security Optimizer plugin.
The issues detailed in my review, and in previous troubleshooting attempts, stem from the plugin’s “Lock and Protect System Folders” feature conflicting with TranslatePress, and the apparent ineffectiveness of the documented “Custom Filter” (
sgs_whitelist_wp_content) to whitelist the necessarytrp-ajax.phpfile. This points to a potential limitation or documentation flaw within the Security Optimizer plugin itself.When users identify such issues with a SiteGround-provided tool, and the documented solutions fail, it would be helpful if there were a clear, free-of-charge channel to report these product-specific problems directly to your development or plugin maintenance team. Currently, the standard support channels do not seem to offer a specific category for “Reporting a bug/issue with a SiteGround plugin” that would differentiate it from a general hosting support request, which might be perceived as (or actually be) a paid service.
The concern is that users might be directed to paid support avenues for issues that are fundamentally about the functionality or documentation of a SiteGround product. This feedback is offered in the hope of improving the plugin and the support process for such cases.
Hello @seventhose ,
First and foremost, please allow me to thank you for the thorough investigation you have conducted. I wish to clarify that the request made by the TranslatePress plugin occurs over the web, classifying it as an insecure request. The primary goal of our ‘Lock and Protect System Folders’ feature is to prevent unauthorized or harmful scripts from being executed in your system folders via web requests. For optimal security, the request to ‘plugins/translatepress-multilingual/includes/trp-ajax.php’ should be executed internally, rather than over the web.
To maintain the ‘Lock and Protect System Folders’ feature while allowing specific scripts to run, you may add an .htaccess file in the directory containing the desired PHP script with the following configuration:
<FilesMatch "\.(?i:php)$">
Require all granted
</FilesMatch>This configuration should permit the execution of PHP scripts within the folder housing the .htaccess file, without compromising the security of other folders.
Please understand that directing our users towards paid support channels is never our intention. The paid support channels are intended only for website maintenance solutions that are beyond conventional hosting support.
Our recommendations to “create a support topic” or “reach out to our support team via the Help Desk” were made with the purpose of gaining access to the application. This enables us to replicate and examine the reported issue firsthand, allowing us to provide more precise and targeted advice.
We deeply value your input and wish to assure you that it will be carefully considered.
Best Regards,
Stefan Stefanov - The full relative path from the
The topic ‘Incompatible with Translate press’ is closed to new replies.
