Hello Anamaria,

I did what you ask me for, but the warning is still their. I’m using Complianz premium as CMP and it still working well (as I said it’s just a warning) That I was thiniking to be the reason for the problem faced and shared on that post.

Thank you.

Hello Anamaria,

Thank you for your feedback.

Sorry, but I didn’t understand much in what you did. Actually, I have no technical background, but I do my best to get things done.

So finally, am I supposed to do something on my side please?

Thank you!

Hello,

I just want to notify that it seemes that there is JS problem that can brake Jquery function. I identify that because I’m using a CMP that gives warning on their dashboard for everything that can cause problem with their plugin (that needs Jquery to run correctly).
Can you check it from your side please?

the error is : Uncaught_TypeError:_fbq_getState_is_not_a_fucntion on line 6 of https://www_mondedestoutous_com/wpcontent/plugins/td_composer/legacy/Newspaper/js/tagdiv_theme_min_js

Hello Anamaria,

Thank you for your advices. Finally, everything get fine without any changes or check from my side.

Regards,

Thami

Hello Calin,

You are right! it’s an amazing feature that you just add and I understand that it must take some time to be improved but not for translation and here is why in my opinion. We are all yours customers, and I think it’s not fair that some can enjoy all the benefits of the updates and not the others. We all paid the same price “I think” and in US dollars too.

That’s all. So, Just keep this in mind for next updates please and thak you for your understanding too.

Have a nice day too.

• This reply was modified 5 years by Thami.

Hello Calin,

thank you for your feedback.

In fact I opened another ticket specifying other elements to translate on the templates, thinking that this ticket was already closed.

I apologize for getting a bit carried away, but I regularly have to deal with this translation problem with other extension developers and this, I don’t hide it from you, annoys me a bit.

Anyway, you can close it, since we have already continued our exchange here.

That said, I maintain that I can’t pay a year of support to send you alerts about malfunctions that don’t come from me. I hope you will understand my position and that you’ll take care of your non english customers as welle as the others.

Have a nice day sir !

• This reply was modified 5 years by Thami.

At the same time, a filter is added to the Woo loop sorting option: Sort by sales rank.

I may have missed some others. Anyway, I hope it will help to speed up the process.

Hello Vlad,

It seems to be the only thing missing (if we consider that the cart translation depend of Woo and not you).

I wich you a nice weekend and I hope that this little change will be done soon.

Hello Vlad,

Thank you for taking into consideration the constraints of non-English speakers. By the way, it seems to me that this is not the only non-translatable element. I’m still redesigning the store and am figuring it out as I go.

Have a nice day!

Hello Vlad,

I was able to find out the reason : PHP version 7.3

Thank you.

Hi,

I’m facing the same issue with fatal error message and i’ve tried everything you said. I opened a post like 3 hours ago but no one reply.

Can we expect a solution today please ?

Regards..

• This reply was modified 5 years by Thami.

“Sorry I did not saw your requests earlier”

• This reply was modified 5 years by Thami.

Hello Vlad,

Here is the problem I encountered and how I solved it.

I use LSCache in parallel to improve the performance of the website. This solution offers the possibility to generate a mobile cache dedicated to the mobile version and not the responsive sites. So by activating the mobile theme with display for Mobile+AMP and keeping the mobile cache activated everything is fine but if the choice of activating the mobile theme is only for AMP pages you have to deactivate the mobile cache if not the site is distorted, that’s all.

Thanks.

Hello Vlad,

Thank you for your reactivity and sorry for the delay in response.

In fact I had disabled the configuration because the website was under review and I can’t tweak it too much during this period.

Finally, it was my cookie solution provider that didn’t offer integration with AMP and I changed it. Since then everything has been fine.

Thank you for your availability.