• Resolved Anonymous User 21052670

    (@anonymized-21052670)


    We have been using this plugin since it’s beginnings and we are grateful for all the work done on it. Currently we have some major concerns related to the new version 2.3-beta.

    The new version 2.3 (beta) which you advised to update as a patch for the issue reported by security plugins is not only a patch but replaces the entire functionality of the plugin with different already existing plugin from www.remarpro.com. The differences that this new version comes with are quite major, namely: different database structure, different programming api, different REST API and mostly different UI.

    By looking at the credits in readme.txt in 2.3-beta I determined that you copied large chunks of functionality (if not all) from the Digital License Manager plugin which is early fork of your License Manager for WooCommerce as per the developer, Darko G. It seems to evolved quite differently from License Manager for WooCommerce despite being a fork.

    The problem is that the update caused a lot of trouble for us and broke all the custom integrations that we did. Also, it failed converting the old data to the new structure leaving us with half-broken database (luckily we have hourly backups). Also lots of other fatal-error showing in this version.

    My question are as follows:

    • Why there is no update(patch) for a week or so on the stable release? This seemingly simple update caused a lot of trouble.
    • Why do we need clone of Digital License Manager when we can use directly that plugin? Is the direction that you really decided to take?

    At this point, I am starting to look for alternatives and if I have to migrate, I will probably just use Digital License Manager directly or another I tested.

    I am really sad and confused because this once beautiful plugin becoming a copycat of existing and no features being added for over two years, also delayed security patches. However, I feel that I need to warn the users of the issues they are possibly going to face.

Viewing 2 replies - 1 through 2 (of 2 total)
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Concerns related to version 2.3-beta from long-time user/supporter’ is closed to new replies.