• Resolved bcrab

    (@bcrab)


    Hey there… nice to see your plugin doing well.

    My client has a paid Private Content plugin from LCweb through Codecanyon. When we logged into our dashboard, WP notified us that our paid cc plugin had an update.

    When we updated, it installed your plugin – removed our users and settings since those features aren’t part of your plugin and well, they’re different… really odd. We restored and all is well now.

    I’ve notified the developer on CodeCanyon too… wanted to make sure that I told you in case someone else has an issue.

    Honestly, I’m not sure how WP calls the updates, as I thought there was a specific callback to defined URLs in the plugin.

    Took some screenshots to show that our “Plugins” display our paid version installed and activated, but the update displayed is yours – just in case anyone needed it.

    Not sure what’s up or if developers really have anything to do with it, just wanted to let you all know.

    Thanks!

    https://www.ads-software.com/plugins/private-content/

Viewing 1 replies (of 1 total)
  • Plugin Author Aldo Latino

    (@aldolat)

    Hi,
    thank you for your report. I really appreciate it.

    Unfortunately a plugin of Code Canyon has the same name as mine, private-content. This causes that, when a new release is published, all users of Code Canyon private-content plugin are notified. When they update their plugin, they receive a totally different plugin.

    This tells us that the WordPress mechanism of checking for new plugin releases is not totally safe. WordPress developers should change this.

    Currently, a temporary solution could be that users check which plugin has a new release before updating. Or a radically better solution would that one of the developers (me or the other dev) do not make any new release, create a new plugin with different name and ask users to switch to the new plugin.

    Thanks again for the report.

Viewing 1 replies (of 1 total)
  • The topic ‘CodeCanyon plugin updated to your plugin’ is closed to new replies.