WordPress.org

Make WordPress Core

Opened 10 months ago

Closed 8 months ago

#24585 closed defect (bug) (duplicate)

WP 3.6 Multisite : category or tag links lead to 404

Reported by: imath Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.4.2
Component: Multisite Keywords: needs-patch
Focuses: Cc:

Description

Hi,

this is what i've found in WordPress 3.6-beta3-24432

If i have a regular config, the tag or category links are working.

If i enable the multisite mode, the tag or category links are leading to a 404, on the main blog or on the child blogs.

Example of tag link that leads to a 404 : http://siteurl.dev/blog/tag/random/

Change History (10)

comment:1 imath10 months ago

  • Severity changed from major to trivial

After updating the permalinks in the main blog and all the child blogs, it solved the problem. This was a thing i didn't need to do in 3.5.1. Don't know if it's a bug so i'll leave it as trivial, just in case.

comment:2 nacin9 months ago

Which kind of multisite? Subdirectory, or subdomain? And the child blogs are definitely affected too?

comment:3 imath9 months ago

Hi Andrew,

This is what i've tested :
1/ i've downloaded and installed WordPress 3.6 RC1
2/ Updated to nightly build ( WordPress 3.6-RC1-24776 )
3/ Added to wp-config.php WP_ALLOW_MULTISITE to true
4/ i've ran the network installation for a subdirectory one, copied the different constants in wp-config.php and saved the new .htaccess. Then i logged in again.
5/ I went to the first post on root blog updated it to add a random tag. Then once on front, if i click on the category or tag link under the post title : 404.
6/ Then i've created a child blog, went to his admin, updated a post to add a random tag, then once on front : same result for category and tag links of the post.
7/ Just to be sure, i've created another child blog and did the same as point 6, and had the same result : 404.

So the multisite config is Subdirectory and child blogs are definitely affected.

Then as in my first comment, i went to permalink settings of root blog and simply hit the Save Changes button to refresh the permalinks, and it fixed the trouble for the root blog. It had no effects on the 2 childs one, i needed to go in their dashboards to refresh their permalinks settings and it fixed the trouble.

comment:4 markjaquith9 months ago

Sounds like we should be doing a rules flush on network creation and also at site creation. Maybe the flushes we're doing are happening too early?

comment:5 follow-up: nacin9 months ago

  • Milestone changed from Awaiting Review to 3.6

Moving to 3.6 for investigation. imath, this definitely isn't something that you need to do in 3.5.1?

comment:6 SergeyBiryukov9 months ago

  • Severity changed from trivial to normal

Might be related to #16201.

comment:7 in reply to: ↑ 5 imath9 months ago

Replying to nacin:

imath, this definitely isn't something that you need to do in 3.5.1?

I'm Sorry Andrew, i've just checked in 3.5.2 and 3.4.2, and i was wrong, this is something you actually need to do. I don't know why i was so sure that the permalinks didn't need to be refreshed for categories and tags.

Maybe it can wait another release, and i might change this into an enhancement. Because, i think it can be interesting that once the network is set, we don't need to think about refreshing the permalinks for categories and tags.

comment:8 markjaquith9 months ago

  • Milestone changed from 3.6 to Future Release

Moving this to future as it's not a new bug and isn't going to get resolved in time for 3.6.

comment:9 jeremyfelt8 months ago

  • Keywords needs-patch added
  • Milestone changed from Future Release to 3.7
  • Version changed from 3.6 to 3.4.2

Moving this to 3.7, there should be a way to resolve this time around.

comment:10 duck_8 months ago

  • Milestone 3.7 deleted
  • Resolution set to duplicate
  • Status changed from new to closed

I think this duplicates #20171.

Note: See TracTickets for help on using tickets.