Opened 4 years ago

Closed 4 years ago

#5502 closed defect (bug) (fixed)

Plugin Directory: Readme Validator thinks valid Readme is invalid

Reported by: ipstenu's profile Ipstenu Owned by: otto42's profile Otto42
Milestone: Priority: normal
Component: Plugin Directory Keywords:


If you paste in (or use it as the link) it thinks it's wrong and tells you it's missing values that are, in fact, there.

Also tested it with Hello Dolly - - and it says that the tested up to field is missing. Which it's not.

Change History (3)

#1 @Ipstenu
4 years ago

  • Summary changed from Plugin Directory: Readme Validator thinks the example Readme is invalid to Plugin Directory: Readme Validator thinks valid Readme is invalid

#2 @Otto42
4 years ago

In my testing, this is not the case.

For the example file, it specifically doesn't like "=== Plugin Name ===" and this is intentional, since we expect authors to change the plugin name line in their readme, so the parser fails for that specifically. It also complains about the Contributors line not having valid ID's in it. Once you make those changes, then it passes.

For Hello Dolly, it doesn't complain about the tested up to line. Instead, it says these:

The Requires PHP field is missing. It should be defined here, or in your main plugin file.
No == Frequently Asked Questions == section was found
No == Changelog == section was found
No == Upgrade Notice == section was found
No == Screenshots == section was found
No donate link was found

All of which are true.

Version 0, edited 4 years ago by Otto42 (next)

#3 @Otto42
4 years ago

  • Owner set to Otto42
  • Resolution set to fixed
  • Status changed from new to closed

In 10430:

Plugin Directory: Readme Parser: Allow data:text/plain streams to pass through parse_readme() also, to allow them to become plain contents before parsing them. Fixes #5502, corrects [10429].

Note: See TracTickets for help on using tickets.