stay away³

  • neralex

    (@neralex)


    9 months, 2 weeks ago

    I came across along here because a client’s website with this plugin crashed completely because it is adding to each db-entry inside of the _postmeta, _options and _posts table brackets like {:de}…{:pl}…{:}.

    The deinstallation-routine of this plugin was not able to remove it, what it has stored into the database. The result after running the deinstallation-routine ended in completely removed styles and content-blocks, which were created with Elementor. All menue-eintries got broken too. The website was built as onepager and this plugin blowed up the wordpress-database with this those shitty brackets to more than 130 MB. All revision were affected too.

    After 5 times of try&errror without any solution and rolling back, I got today this plugin finally removed with WP-CLI and a lot of regex-sql-updates along sql-backups after each step. The database got shrinked to 4 MB after the cleaning from WPGlobal.

    I have never seen so much hazzle to remove a plugin. This is a very bad example how it can ends, when the developers doesn’t follow the wordpress codex. It’s a shame that the developers of this plugin are still selling licenses for it, which is not more maintained anymore.

Viewing 1 replies (of 1 total)
  • Plugin Author TIV.NET INC.

    (@tivnetinc)

    4 months ago

    @neralex

    1. First, we are sorry to hear that you had a bad experience with WPGlobus.
    2. The language marks is how WPGlobus works. The texts are duplicated. There are other plugins that use different techniques, but still each translation adds megabytes to the database. Where else to store those texts?
    3. The clean-up tool was tested with the standard posts and pages, but – yes, there could be problems, and that’s why we have a BIG RED WARNING there.
    4. Elementor specifically – we have to admit – it’s too complicated for us to fully support. Sorry.
Viewing 1 replies (of 1 total)

You must be logged in to reply to this review.