Home / Plugin: Plugin Check (PCP) / Wrong warning: plugin readme.txt does not exist
Hi,
First, thanks for the new layout of the plugin check page.
Have version 1.0.1 installed. For all plugins a wrong warning is returned:
FILE: readme.txt
The plugin readme.txt does not exist.
Guido
Hi @guido07111975,
I would love to get some extra details, some times that can be a lack of permissions on your server, would you mind sharing a bit more about your environment.
Best Regards,
Hi Gustavo,
I’m working on a localhost install. No change when deactivating all plugins except PCP and 1 other.
Came to the conclusion that it works fine at my other live site. So I guess it’s a localhost thing. HTTPS perhaps?
Guido
It could be all kinds of things, but I would love to know more about your local setup so we maybe can pin-point the problem and fix so others can use if they are in a similar setup.
Hi Gustavo,
Using Wampserver 3.3.2 (64 bit) with PHP 8.1.26.
Have multiple local installs and same issue in all of them.
Even when deactivating all plugins except PCP.
As mentioned before, this does not occur on my live site, so guess it has something to do with a localhost install?
Guido
It happens the same to me. I am also using a local install in order to develop my plugin. My settings are:
Windows 10
App: Local (used to be called ‘Local by Flywheel’) Version 8.2.1+6583
https is enabled
The webserver is nginx
PHP v.7.4.30
MariaDB 10.4.10
WP v.6.4.3 single site
It also showing me same error “The plugin readme.txt does not exist.” But i have readme.txt file in my plugin directory. In the online checking it shows everything ok,but when i installed plugin checker in localhost,it showing this wrong error message.
This happens if the name of the plugin doesn’t match the slug, e.g.
https://wordpress.org/plugins/boaty-mcboatface
Plugin Name: Boaty McBoatface
The slug and name must match, but most plugins don’t, since the plugin name is used for the readme title, this changes either for SEO purposes or for the plugin name change with a better description.
The same would be for the text-domain, if your plugin slug is boaty-mcboatface then the text-domain should boaty-mcboatface as well.
Not a big deal.
This error may appear in some Windows setup due to path separator issue. This has been fixed in https://github.com/WordPress/plugin-check/pull/453
Hi guys. Did you check your readme.txt file with the WordPress validator tool?
https://es.wordpress.org/plugins/developers/readme-validator/
This is the best practice to find what exactly is missing in your readme.txt file.
Best!
It was not caused by the readme. But they just updated plugin. It’s fixed now.
Guido
Good to hear that is solved.
