I do not know Spanish, but I’ll try my best to help.
I believe that you are saying that after updating the plugin, the plugin still shows that it has an update available. I can think of three possible explanations for this:
- The zip you are using to update the plugin has an older version of the code. For example, if the latest version if 5.1.3, and you update to 5.1.2, it is natural that a message showing that an update is available would remain. The solution in this case is to get the zip for the 5.1.3 version and update to that.
- The plugin has the same directory name as a plugin on www.ads-software.com. For example, let’s say that you update a custom or premium plugin with the directory name of “jetpack”. Since this “jetpack” directory uses the same directory as www.ads-software.com’s Jetpack plugin, WordPress thinks that it is the www.ads-software.com’s Jetpack plugin. If the latest custom/premium “jetpack” plugin version is 5.2, WordPress will still report that an update is available since the current version of the www.ads-software.com Jetpack is 6.7. The solution in this case is to install the custom/premium plugin in a directory that has a name that is not shared with a www.ads-software.com plugin.
- The developer of the plugin forgot to update the plugin version number when releasing the new version. Each plugin has a main file that contains the File Header. This file header has details about the plugin, such as the name, description, version number, etc. If the latest version of the plugin is 5.2, it is possible that the developer forgot to update this version number in that main file. The result of this is a zip file that contains the version 5.2 code, but the plugin tells WordPress that the version of the plugin is 5.1. I’ve seen this issue many times over the years as it is a very easy mistake to make. The result is that WordPress will endlessly say that there is an update available for the plugin since installing the zip file for version 5.2 results in a plugin declaring itself to be version 5.1. This issue can be fixed by manually updating the main plugin file’s file header to change the version to the correct version number or contact the developer to notify them of the issue and wait for a new version to be released that has the fix.