SHREDDERz
Did you bought the previous plugin from code caneyone?
Thanks
Aftabul Islam
Yes. It appears that the plugin is no longer associated with the WordPress file-manager slug id. What’s going on?
SHREDDERz
Unfortunately the name of this plugin and the plugin that you bought from code caneyone is the same.
wordpress plugin updater confuses your paid plugin with this free plugin.
Solution, Just roll back to your previous plugin via ftp(hope you know how to do that). And don’t update the plugin again.
It should fix your problem.
Thanks
Aftabul Islam
Why is this marked resolved? Why is this WordPress plugin slug now associated with a different plugin?
Try this page http://codecanyon.net/item/file-manager/8999688/comments
If you need any other assistance please ask.
Thanks
Aftabul Islam
Seems like it might be more honest if you post a message to your front page plugin description, changelog, and FAQ page that clearly states this is not the plugin previously associated with the same WordPress slug id.
This seems necessary due to the fact that WordPress users of the other plugin will be seeing notifications that prompt them to update to the “new version” of the plugin. This update would actually lead them to installing your plugin. There is clearly an incentive for you to do otherwise (i.e. not post the notification) but I hope you consider placing such a disclaimer in some prominent location of your plugin description.
SHREDDERz
First of all, I find no dishonesty in developing a GPL licensed plugin which is free to use and also free to hack(please remember hacking and cracking is two different things).
The similar plugin name(in your word slug) issue is totally a co-incident and not intentional from my part.
I will add this information to my FAQ page to avoid further misunderstanding. But I find no reason to add this on my plugin description and change log.
Thanks
Aftabul Islam
