Opened 15 years ago
Closed 15 years ago
#13555 closed defect (bug) (fixed)
GUID and feed issues with custom post types
Reported by: | nacin | Owned by: | |
---|---|---|---|
Milestone: | 3.0 | Priority: | lowest |
Severity: | trivial | Version: | |
Component: | Posts, Post Types | Keywords: | has-patch |
Focuses: | Cc: |
Description
- With rewrite => true, all posts of a custom post type will get the same guid. Aside from being a Bad Thing, this breaks feeds in particular (looks like Safari cares deeply).
- With ugly permalinks, the feed won't validate. Seems to be annoyed with the underscore, or something:
<link>http://localhost/commit/?post_type=manager&p=45</link>
Attachments (1)
Change History (13)
#2
in reply to:
↑ 1
@
15 years ago
Replying to beaulebens:
In your example for 2), I imagine it's unhappy about "&" which needs to be encoded in XML.
That would make perfect sense.
#3
@
15 years ago
Yep. We've never previously had & there, even ugly links.
Currently tracking down the first issue. Looks like get_permalink() is returning just http://localhost/commit/manager/ when generating an auto-draft.
#5
follow-up:
↓ 6
@
15 years ago
Why can't we omit the post type altogether? using just ?p=<post_ID> in the url gives you the right page, and the post_ID is, de facto, unique.
#6
in reply to:
↑ 5
@
15 years ago
Replying to wmrom:
Why can't we omit the post type altogether? using just ?p=<post_ID> in the url gives you the right page, and the post_ID is, de facto, unique.
Hrm. It doesn't on my install, though it should. There should be a canonical redirect, the same way p=2 goes to page_id=2.
In your example for 2), I imagine it's unhappy about "&" which needs to be encoded in XML.