phirephoenix

Seekerman – I am, yeah! So far it makes the most sense for the way our content is set up and I’m pretty happy with it. There’s a little bit of extra hassle in terms of managing themes for the various subsites (I created a pseudo-grandchild theme for the subsites and imported the relevant styles from the child theme), but it’s definitely worth the clearer separation between sections, and gives us more freedom for doing creative things within one section only.

The main trouble I’ve run into is that moving multisites between servers is a little bit more work than moving a regular install, and not all plugins support multisite installs, especially the smaller and more esoteric ones. The latter is mainly an issue for site-wide activations, and the most important ones that we were using (Contact Form 7, Super Cache, etc) all worked fine.

Same error message here. It still lets me add jobs, but I’m not sure if they’re running correctly yet.

Ooh, awesome, I will dig into that and report back with the results. I’m not sure I understand why I need a separate action for non-logged-in users, though…?

Thanks for all your help Mika! We ended up going with a Multisite because we thought there might be situations where we would need multiple post types for each “section”, and we didn’t want to start with 4 CPTs off the bat for each section and keep expanding from there. This way what belongs on which section is also really obviously separated for the client, so they’re less likely to accidentally post things to the wrong section.

Hey Mika, thanks for that link. I actually came across that in my own research and found it quite helpful. It’s not entirely conclusive, though: If I want the subsites to look visually similar but have different widgets and content layouts but the content should be managed centrally, it seems like the arguments for either CPTs or a multisite are split down the middle.

More than anything else I’m concerned with the most elegant way of swapping out the header for each section to generate a different set of styles and main menu for each section. If conditional tags in CPT template files is the best way to deal with that, I could live with that, but I wanted to make sure I wasn’t overlooking anything.