#20065 closed defect (bug) (invalid)
Spoiled page structure in new WP version
Reported by: | tazogamer | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | General | Keywords: | |
Focuses: | Cc: |
Description
hello,
in earlier version i could set permalinks structure as i wished. (i.e.
/company/%postname%
and published page will be www.mysite.com/company/testpage
but now it publishes all posts at www.mysite.com/testpage
why?
also, why
$_getpage_id?=testpage;
can't get the page's(testpage) content? it did in earlier versions.
Change History (2)
#1
@
13 years ago
- Milestone Awaiting Review deleted
- Resolution set to invalid
- Status changed from new to closed
#2
@
13 years ago
Sorry, seems I misread you.
But yes, /company/%postname%/ permastructure still works in WordPress 3.3, However, if you have any plugins that affect the Permastructure, they may have broken with the %postname% changes in !WordPRess 3.3.
Trac is not a support avenue, please use the Support Forums for further support cases, if a bug is identified and reproducible, then a Trac ticket can be filed.
Note: See
TracTickets for help on using
tickets.
The permalink settings only apply to posts, they have never applied to pages. Pages are always published starting from /. If you have a page parent called 'company' and you make this page a child of that, then it'll be /company/testpage.
As explained in the last ticket, page_id only accepts the page ID. To pass a page slug, you are required to use the 'pagename' parameter.
If either of these worked in a earlier version, it was unexpected buggy behaviour.