Forum Replies Created

Viewing 15 replies - 1 through 15 (of 46 total)
  • Thread Starter Lion73

    (@lion73)

    Every version after 8.4 is a disaster. These new cookies are the wrong choice. This is the only certainty at the moment.

    Thread Starter Lion73

    (@lion73)

    At the moment the version to keep is 8.4. The new cookies introduced quietly are not in line with the European GDPR guides and in any case it is absolutely necessary to add a dedicated and declared function to be able to deactivate them.

    • This reply was modified 10 months ago by Lion73.
    Thread Starter Lion73

    (@lion73)

    Considering all the bugs introduced with version 8.5 (and the resulting issues) and the introduction of these cookies for questionable purposes, I think I will stick with version 8.4 for a long time. A significant deterioration in product quality. Useless and invasive new features. I think woo is losing sight of what the purpose of the initial project was. Very bad.

    Thread Starter Lion73

    (@lion73)

    “but I think it’s optional and can be disabled”…I haven’t found any option to disable them in v8.5.0…

    Thread Starter Lion73

    (@lion73)

    These cookies make websites non-compliant with European legislation. I hope they are not introduced in the next release.

    Thread Starter Lion73

    (@lion73)

    I understood the problem. WordPress reported a WC update available. I updated the plugin. Version 8.5.0.
    Checking on www.remarpro.com I noticed that the latest version available is 8.4.0. I replaced the plugin and the cookie problem disappeared.
    Now I wonder how it is possible that an automatic updater was able to download an unofficial version of the plugin!

    Thread Starter Lion73

    (@lion73)

    By deactivating WC (v. 8.5.0) and deleting cookies, none of these cookies are reactivated. Once WC is reactivated the cookies return.

    • This reply was modified 10 months, 3 weeks ago by Lion73.
    • This reply was modified 10 months, 3 weeks ago by Lion73.
    • This reply was modified 10 months, 3 weeks ago by Lion73.
    Thread Starter Lion73

    (@lion73)

    Dear wp-buy,

    It is not my habit to leave a negative review for a product like your plugin, as I am also a developer, I understand the difficulties and compatibility issues.
    Nobody claims 100% compatibility of a plugin in a WordPress environment ad in different server environments. This is clear and perfectly normal.

    In the long chat with support I was very clear about the problems encountered with the theme I use (theme and not with other plugins) and the recurring answer has always been: our developer needs more time. And finally: we cannot solve the problem. Or rather, to be more precise, in a sarcastic tone: Have a good day!
    Not to mention the problem of plugin translation, where there is no compatibility problem with other plugins. My request was practically ignored.

    However, I almost managed to solve the problem of protecting images on mobile completely on my own by analyzing the code and making some simple changes (and it’s quite incomprehensible why you couldn’t do it).
    Considering that it is very clear that I cannot hope for your help, I will analyze the language problem as soon as I have some time.

    So, in short, the negative experience is due to the lack of willingness on your part to resolve the problems that, it is normal, may arise and, speaking of a commercial product, I believe it is due.
    If only you had spent the time of this message trying to solve the problem, this useless conversation would never have existed.
    The problem is how a commercial company presents itself towards customers. The customer is always the most precious asset, remember it.

    Best regards

    Thread Starter Lion73

    (@lion73)

    The paid version’s support only wastes time and does not solve any problems. We strongly advise against purchasing the Premium version which, moreover, is obsolete and has not been updated for many months. Very, very bad.

    Hi @paroleinlinea ,

    WPML 4.6.6 and WPML String Translation 3.2.8 are available with fixes for

    Performance problems with String Translation 3.2.7 on websites powered by WordPress 6.3, Missing list of translators in WPML → Translation Management on multisite setups, A problem with reusing string translations in A problem with reusing string translations in the Classic Translation Editor.

    Try installing new versions and see if they solve your problem.

    Lion

    Hi Cristina,
    as I wrote to you I think the problem is caused by the wpml plugin, but I’m not sure yet…
    It seems strange to me that you can’t change hosting even if there are less than 15 days left until the deadline. If you need help with the migration you can contact me here: https://capturelight.net/contacts/

    • This reply was modified 1 year, 2 months ago by Lion73.

    Hi Cristina,

    the problem from version 6.3 exists, I will try to understand why and solve the problem. I think the cause of the slowdown depends on the wpml plugin. However your site, even with version 6.2, has a page loading time that is too high, the server response is not as it should be. You should consider moving your site to a better performing hosting provider. Italian hosting providers promise you high performance but in reality they provide limited resources on shared hosting plans.

    Lion

    • This reply was modified 1 year, 2 months ago by Lion73.

    Same problem with all my websites wp based.

    WordPress 6.3 incredibly slows down page loading even on very fast servers.
    Highly not recommended to upgrade to version 6.3.

    Thread Starter Lion73

    (@lion73)

    The plugin (v 14.2) doesn’t work on iOS, and presumably on other mobile devices as well. Just press and hold on a photo to be able to save it.

    Thread Starter Lion73

    (@lion73)

    Hi…thanks, great implementation.
    Is it necessary to alter the table manually?

Viewing 15 replies - 1 through 15 (of 46 total)