George Botsev

Hey Andres,
Thank you for reporting the slowness.
As you have identified – the problem may be related to String Translations. We are going to check it with our teammates from the String Translation team – there are some pretty big performance improvements coming there in that plugin. Once we have some news, we will get back to you.

No problem for the extra folders.
I think that I located one things that may help you speed up the site.
You have enabled two options that are known to cause big loads.
These options are:
1. Track where strings appear on the site
2. Auto-register strings*

They are located in WPML -> String Translation – below all strings.
Please see my screenshot here: http://imgur.com/KhLUZtW

In my tests – your site takes from 5 to 8secs to load.
After that an ajax requests is sent – ?wc-ajax=get_refreshed_fragments that can take from 1.24secs (if the options are disabled) up to 6seconds on my install.

So I would suggest you to try and disable these options.

I am sorry, I did not get the part that this is a problem in the front-end.
In that case, because this forum is not very secure, I would like to ask you to open a new ticket in our forum at wpml.org and let’s debug the performance issue there.

Also, I see one issue reported for WooCommerce here: https://github.com/woothemes/woocommerce/issues/7777 – is this the problem that you are experiencing?

Hello,
Would you mind sharing your versions that your client is using, please?

We are currently working on optimizing the performance for WooCommerce Multilingual and WPML. We just released new versions – WPML 3.4 and WooCommerce Multilingual 3.8 – as you can read here: https://wpml.org/2016/06/wpml-3-4-woocommerce-multilingual-3-8-released/ in the next releases, we are going to concentrate on the performance.
For now, I can suggest you to try and go to Products > Products > Screen Options – and uncheck the option with the flags.
This might improve the performance, once it is done.
In the new versions, that will follow – we are going to optimize the performance as mentioned in the blog post that I quoted above.

Hello,
You have mentioned that the string might be in your theme.

Did you re-scan the strings for your theme from WPML > Theme and plugin localization? – maybe the correct string was not being yet detected.
As far as I see, in the ticket that you provided below, the problem might be because the translation is missing from the .mo file – possibly because of the status of the translated string.

I would suggest you to take a look at your theme – if you can see where the string is used, and if it is used correctly – wrapped in a gettext call.

You can see more information about troubleshooting string translations here: https://wpml.org/documentation/support/troubleshooting-string-localization/

I had the same problem – the button is not working.
I had to modify slightly the code in order to make this work.
Changed:
$('#pea_cook_btn, .eucookie').on('click', function () {
to:
$('#pea_cook_btn, .eucookie').live('click', function () {

Hello,
Error 500 is very general error, and the reasons for this error appearance can be related to a vast array of possibilities.
Please check your error log for the server, for PHP and if you have enabled debugging in WordPress – check that log as well.
If you don’t have any logs, you can enable debugging by setting this options in wp-config.php

// Turn debugging on
define('WP_DEBUG', true);

// Tell WordPress to log everything to /wp-content/debug.log
define('WP_DEBUG_LOG', true);

// Turn off the display of error messages on your site
define('WP_DEBUG_DISPLAY', false);

// For good measure, you can also add the follow code, which will hide errors from being displayed on-screen
@ini_set('display_errors', 0);

and then attempting to reproduce the error by doing the same actions as before.

As always, if you need any more help regarding this, it is recommended to open a new post in our forum at wpml.org where our specialists can help you debug this further.

Thank you very much!