Delyan Delov

Since your site is hosted at SiteGround, could you please create a ticket regarding the issue so our advanced technical support could further investigate it.

This is the solution described by @slaffik that resolved the PHP warning. To avoid duplication, please check my reply in your other thread.

Hi @siddjain,

Could you please try disabling the Memcached option within our plugin? Then ensure the Memcached service in SiteTools is activated before enabling it back from within the plugin.

Hi @siddjain,

Our developers applied a fix which was released with version 7.6.4. However, you may need to disable the Memcached option within the plugin and enable it again manually.

Hi @polozatka,

It seems that the issue is related to the JS code being duplicated after its combination. You can try disabling the JS Combination functionality in our plugin or exclude the duplicated JS file from the combination:
https://www.siteground.com/tutorials/wordpress/speed-optimizer/custom-filters/
More information on how to use the custom filters can be found here:
https://www.ads-software.com/support/topic/how-to-use-sg-optimizers-filters-procedure/
If you are not sure which JS script should be excluded and your are a SiteGround customer, please open a support ticket from your account at SiteGround and we will assist you with that.

Hi @show-up-strong,

I am sorry to hear you are experiencing an issue with some of our plugin’s functionalities.
To review the case further, could you please create a new support thread and provide more details on how to recreate the issue on our end? If you are a SiteGround client, you can also post a ticket to our advanced technical support team and they will review your case.

Hi @joe-bloggs,

Unfortunately, I am unable to recreate the issue you are experiencing because the GTranslate plugin is a paid one. However, the issue is most probably caused by the rules added by our plugin to the wp-content/.htaccess file:

<FilesMatch "\.(?i:php)$">
  <IfModule !mod_authz_core.c>
    Order allow,deny
    Deny from all
  </IfModule>
  <IfModule mod_authz_core.c>
    Require all denied
  </IfModule>
</FilesMatch>

You can easily exclude the Gtranslate PHP file from the above rules by adding the following code at the end of the wp-content/.htaccess file:

<FilesMatch "gtranslate\.php$">
    Require all granted
</FilesMatch>

This way the WordPress content will be protected and the Gtranslate plugin will work properly.

Regards,
Delyan Delov

Hello @generosus,

Since your request for implementing a functionality of excluding only certain content on a page is quite specific, I do not believe we will implement it in our plugin.

Still, I have passed your suggestion to our developers.

Hi @generosus,

I am afraid that there is no direct way to load a script using our plugin.

Did you try adding “loading=async” into your Googlemap script tag?
https://maps.googleapis.com/maps/api/js?key=xxxs&loading=async&language=en&callback=awbMapInit&ver=xxx

Hello @antoniop80,

I am afraid that our plugin does not have such functionality, however, you can do that by creating an .htaccess file under the plugin folder:
wp-content/plugins/translatepress-multilingual/includes/
and “exclude” the files that should be accessible.

For example, if you want all PHP files under the above directory to be accessible, you can add the following directives to the newly created .htaccess file:

<FilesMatch “\.(?i:php)$“>
  <IfModule !mod_authz_core.c>
    Order deny,allow
    Allow from all
  </IfModule>
  <IfModule mod_authz_core.c>
    Require all granted
  </IfModule>
</FilesMatch>

Hi @migster,

the special characters were intentionally disallowed in the custom login page’s field in version 1.3.7. This is why you should perform the encoding manually as mentioned above by @plamenm.

I have already brought your suggestion to the attention of our developers and they will consider whether to allow using special characters in the Custom Login field again in future versions of the plugin.

Hi @entumas,

The latest plugin release (1.4.13) should address the issue you are describing. Please make sure you have updated the plugin.

What else you can try is to disable the 2FA via WP-CLI using the following command:
wp sg secure 2fa disable
and then use the reset link to set up the 2FA anew. You can do that using another administrator user if needed.

Hello @mickhele,

the provided logs are not the actual error but only part of the error message. It seems that there is some incompatibility between our plugin (and specifically the Memcached functionality) and Hotel Booking from MotoPress plugin which is hard to look at without access to your WordPress site.

In order to investigate the issue further, could you please open a ticket from your SiteGround account so our support team can recreate the error on their end. They will examine your site directly as the Hotel Booking is a paid plugin and we cannot recreate the error on a test environment. Thank you for your cooperation.

Hola @webnas3575,

Si tiene un problema específico con nuestro complemento, cree un nuevo hilo de soporte y proporciónenos los pasos detallados sobre cómo recrear el problema por nuestra parte. Alternativamente, si es cliente de SiteGround, puede abrir un ticket de soporte para que podamos investigar más a fondo el problema.

Hi @plexsites,
I understand your point but converting the images to .webp requires they to be duplicated in order to avoid any data loss.
You can delete the converted images but note that all .webp files will be deleted no matter if they are generated by our plugin or not.