btw. despite it seems to be working, 3.2.5 throws the following error:
Deprecated: Function create_function() is deprecated in /home/huggenbe/www/singkreis.digi-tales.ch/wp-content/plugins/private-content/login_widget.php on line 97
Notice: Die verwendete Konstruktor-Methode für WP_Widget in PrivateContentLogin ist seit Version 4.3.0 veraltet! Verwende stattdessen
. in /home/huggenbe/www/singkreis.digi-tales.ch/wp-includes/functions.php on line 4503
you are using another plugin that has the same name as mine. You can ask the developer for support in the CodeCanyon site.
Please, let me know, if you need further help.
thanks, I realized that there were different dev names, but you should know that looking at the detail page shows the one of your plugin and the update of that plugin loads your plugin!
See these screenshots:
thank you for the screenshots.
This is a known problem that affected other users. The WordPress upgrading process overwrote the Private Content folder of CodeCanyon plugin, installing my plugin over the CodeCanyon plugin. So, now the best way is to manually restore the correct Private Content folders and files in your website using an FTP or SSH connection. Your current data in the database should be fine.
Why does this happen?
As already said, my plugin and CodeCanyon plugin share the same folder name
private-content, so WordPress looks into its repository for this folder name, sees if there is a new version, and suggests the upgrade if applicable.
What to do next time?
Before launching the upgrade process, make sure that the version published in CodeCanyon matches the new version indicated by WordPress in the dashboard.
The best solution would be that CodeCanyon should adopt an internal upgrading management system that looks for possible upgrades only for the plugins that are stored in its repository. Honestly, I do not know CodeCanyon, but this should be a way to follow, just to prevent situations like this.
Let me know, please.
thanks for the explanations. I’ll have to pay a fee for the new version of the plugin and will download it from CodeCanyon and install it manually, thus there will be no problem with automatic update this time. I’m curious if after this automatic update is gonna work. Maybe the new version has another folder name – will let you know.