Elli_K

Certainly you CAN manage it on a closed network, but it’s hard.

My main site has 10 categories. None of the subsites will not be using a name that is same than a main site category. Even if there was a blog -slug present, those category names will be names, that subsite could not have as it’s directory, because it would be just confusing.

This is getting better in 4.0, we’re allowing for some taxonomy changes and dupe page URLs as long as they’re not on the same level.

When will 4.0 be released? Any estimates, in case I could wait for that? ??

Thanks for the hint. I’ll have look into that another thread. And luckily, I still have month to go to till beta launch and two months to public launch, so there’s still time to solve this issue. I have my own server, so that makes setting up things easier. Thou I have no experience on apache settings etc., so help will be needed and is welcomed.

Without the blog slug, WordPress can’t really distinguish between your-domain.com/%category%/%postname%/ and your-domain.com/subfolder/permalink when %category% = subfolder.

What comes to possible conflicts, atm the plan is, that blogs don’t even use or need categories, posts will be sorted on monthly archives and with tags.

Only possible conflict I see, is if main site had for example url
domain.com/movies/prometheus and there would be subsite named movies posting about Prometheus as well. Am I right?
But then again, it is highly unlike, that the registration will be free any time near in the future, so basically I’m setting up child sites manually. And to be on safe side, there’s already a field, where I can set desired names for not being used as blog names.

What comes to not using /%category% on main site, it’s doable naturally, but in this case I don’t see it as on option, since the whole idea of the main site is that is has posts around different themes and beeing such a firm believer, in what comes to usability, I want to keep end users informed always, in any possible ways, where they are. And urls are one of the ways to do it.

Ok, sorry not being clear enough ??

Sorry, I’m not sure, if I understand your question. Those 404:s I was talking about, happened frontside.

Yes, I was able to remove blog slug, and looks like if permalink structure is set to https://domain-name.com/?p=123, it works. But that url structure is something, that is imo even worse, both usalibility and seo wise.

I have another clean multiblog istallation just for testing, I’ll give it a try in order to see, if this could be a conflict with some existing plugin. Theme is based on twentyfourteen on main site.

Not stupid. You have to actually go to the options tab, scroll down till you find permalinks, and edit there.

Boy that was difficult. Only now realized, that there is that separate Site Settings for mothersite also. Tbh, that is not very handy usability wise; might be worth considering combining that to mothersite general settings.

I set the permalinks first on the actual blog site, and then went to Network Admin to change the permalink structure there.

Result: URLs display correctly, but I am getting a 404 error, and not displaying the content of the post.

Same here, only 404:s

I added this one and it works:

Could you walk me thru the settings? Installed plugin, still 404:s

No, the refresh isn’t heavy. We’re talking about doing it on every page load actually.

Ok, good to know, since if nothing else works, I guess that is the only option.

Okay, so the Yoast bit is working. Good, now try to edit the blog slug in Network Admin.

Sadly, the slug is hard coded into WP so That’s why it’s hard to remove.

Here’s what’s done know:

– On the main (root) site I’ve set custom structure /categoryname/postname/. Optional are empty.

– With Yoast ‘Strip category base’ is set.

– On a single blog permalink structure is set to /postname/. Optional are empty.

On a risk of being idiot (I’ve used to that).. should there be some other section, where to edit settings? I’ve checked gazillion times, and in network admin > network settings, there is no option to edit permalink settings. My installation is one week old 3.9.1.

Am I missing something from my config-file? Or is this because childsites are set to runon sub-directories?

Isn’t that refresh quite heavy on server?

I’m running on a quite fresh 3.9.1 multisite install, and stripped categorory base with Yoast SEO. Site permalinks are set to /%category%/%postname%/. Optional settings are now empty, since Yoast handles that.

Blog -slug is still there. And I really need to solve this issue before going live with my site, as I see it as a usability issue. Current structure being too confusing to site users, since the main site is collection of articles, and multisite blogs are, well blogs ??

If it just absolutely not can’t be removed, then I’d like to at least rename the slug to something more logical like section/. That is not preferred, but better anycase.

I usually just use alternative phrases. For example ‘Navigation’ can be called ‘Menu’. That’s the easy way out.

Also could setting ‘max-width’, or restricting characters in post titles help?