Context Navigation

Changes between Initial Version and Version 1 of Ticket #46938, comment 21

initial	v1
4	4	> Historically, the readme.txt for plugins has only been used by the WordPress.org directory. This provided a clear separation. WordPress reads the PHP file, the directory reads the readme.txt file for other things not in the PHP file's headers.
5	5
6		Thanks for the context. Just to clarify, the `Requires PHP` header was introduced in #meta2952 for the directory first, so it made more sense to have it defined in the same place as `Requires at least`, which only exists in `readme.txt`. Otherwise it would confusing and inconsistent to define requirement headers in two different places, one in `readme.txt` and one in the plugin's main PHP file, especially if each only works in that specific place.
	6	Thanks for the context. Just to clarify, the `Requires PHP` header was introduced in #meta2952 for the directory first, so it made more sense to have it defined in the same place as `Requires at least`, which only exists in `readme.txt`. Otherwise it would be confusing and inconsistent to define requirement headers in two different places, one in `readme.txt` and one in the plugin's main PHP file, especially if each only works in that specific place.
7	7
8	8	> So, my 2 cents is to instead add reading these headers to the plugin's PHP file, and give precedence to that instead of the readme.txt file.