WordPress.org

Make WordPress Core

Opened 3 years ago

Closed 8 months ago

#17095 closed defect (bug) (wontfix)

format or validate author url from api.wordpress.org

Reported by: wycks Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: WordPress.org site Keywords: needs-patch
Focuses: Cc:

Description (last modified by westi)

The author url from api.wordpress.org does not seem to do full format checking. Not apparent in browsers since they will understand malformed urls but is a problem when outputting elsewhere.

Example:

<author type="string"><![CDATA[<a href="http:www.artificium.sk">Stanislav Gunčaga</a>]]></author> 


Change History (7)

comment:1 nacin3 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

You'll have to try WordPress.com support. This Trac is for the open source project at WordPress.org.

comment:2 westi3 years ago

  • Milestone set to WordPress.org
  • Resolution invalid deleted
  • Status changed from closed to reopened

Actually he means api.wordpress.org :)

e.g.

http://api.wordpress.org/plugins/info/1.0/WP-Custom-Pages.xml

comment:3 westi3 years ago

  • Description modified (diff)
  • Summary changed from format or validate author url from api.wordpress.com to format or validate author url from api.wordpress.org

comment:4 nacin3 years ago

Looks like this is data straight from the plugin: http://plugins.svn.wordpress.org/wp-custom-pages/trunk/wp-custom-pages.php.

Not sure if we should adjust the parser to correct this. It's quite the edge case.

comment:5 ocean903 years ago

  • Version 3.1 deleted

nacin: Maybe we can use the new malware check here? (16923#comment:7 )

comment:6 nacin3 years ago

That's not the issue.. It's the validity of the URL: "http:" versus "http://".

comment:7 Otto428 months ago

  • Milestone WordPress.org deleted
  • Resolution set to wontfix
  • Status changed from reopened to closed

Too edge case, I'd say. If we decide that we want to support odd formats for this sort of thing, we can make a new ticket in meta for it.

Note: See TracTickets for help on using tickets.