Chris Jean

I’ve been unable to figure out what issue you might be having. I thought you might be running an older version of WordPress or the plugin, but both are current. I think that the issue may be related to something specific to your hosting.

Unfortunately, I don’t think this plugin will work for you. I recommend working with your hosting company or whoever manages your website to get the theme updated.

This isn’t needed as the wp plugin install command supports a --force option that removes the directory if it already exists.

While the warnings being displayed show files paths for this plugin, this is not an issue caused by this plugin. I’ll give you what I know based upon the details however.

This plugin does not have a file named in1it.php, so I don’t know why something is trying to read information from that file. This indicates some kind of bug on the site, but there is insufficient information to know where the bug is.

It’s tempting to think that the bug could be in WooCommerce since the warnings are popping up on that page, but if the detail about the site running version 3.5.7 of WooCommerce is accurate, that can’t be the case. That’s because version 3.5.7 of WooCommerce does not call the get_file_data() function which is what is producing the errors.

So, a plugin, theme, custom code, or exploit on the site is using the get_file_data() function to request a file that does not exist and should not exist. That’s all I have. If you don’t know where to go from here, I recommend that you contact your hosting company for further assistance.

The plugin is multisite compatible. You will want to network activate it for it to work properly.

That message comes from a WordPress security system (called a nonce). It typically happens when you have a page loaded for a while and then try to take an action that requires an additional security check. It could also indicate an issue with your server’s clock.

I recommend retrying the upgrade as it could just be the result of triggering the update from a stale page. If you continue to run into issues, you should contact your host.

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:

1. 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.
2. The plugin has the same directory name as a plugin on wordpress.org. 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 wordpress.org’s Jetpack plugin, WordPress thinks that it is the wordpress.org’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 wordpress.org 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 wordpress.org plugin.
3. 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.

I updated the plugin yesterday to a new version. No code changed, but the update cleared the “this plugin has not been updated in…” message that wp.org was showing.

I assume that this update will also be seen by WordFence so that it will no longer send abandoned plugin emails about this plugin. I can’t do anything to prevent the emails being sent in the past, but I can bump this plugin periodically to prevent it in the future.

The “No valid plugins were found” error message comes from WordPress. It means that the zip file does not appear to contain a valid plugin. I can think of two likely causes of this problem:

1. The plugin zip that you downloaded is invalid either due to a mistake by the developer or the system that creates the zip files.
2. You have Mac that automatically unzipped the download resulting in your having to manually rezip the files. By doing this, you may have accidentally changed the contents resulting in the creation of an invalid plugin zip.

The contents of a valid zip file typically looks like the following:

plugin-name/plugin-name.php
plugin-name/readme.txt
plugin-name/other-file.php
...

If the plugin directory is missing in the zip, such as the following, the plugin zip is not valid:

plugin-name.php
readme.txt
other-file.php
...

If the plugin directory is double-nested in the zip, such as the following, the plugin zip is not valid:

plugin-name/plugin-name/plugin-name.php
plugin-name/plugin-name/readme.txt
plugin-name/plugin-name/other-file.php
...

From the information provided, I can’t tell if the issue is #1, #2, or something else such as just a bad download. That said, the problem is definitely due to the zip file not containing a valid plugin.