[Erm… This is probably obvious, but I don’t notice it in this forum…]
Is there a way to reverse the populating process so that posts from child blogs don’t show up on the main blog’s frontpage?
Tried out SWT on one multisite network, to see if it’ll work for a project on another. (Sounds like it will.)
Thing is, I end up with unwanted posts on the main blog’s frontpage, even after switching to a tags site or after disabling the SWT plugin. Does it have anything to do with caching? How can I keep these posts “out of the loop”?
Just to confirm (in case somebody else ever wonders about the same thing): moving these posts to trash from the main site’s dashboard only removes them from the main site. To delete quickly, using the list of posts, screen options to show as many posts as possible, then select all (checkbox at the top of the checkbox column, deselect posts which were originally from the main site, bulk action “move to trash”, and “apply” button. In my case, it went quickly. Had 86 posts (from 17 sites), only three of which were from the main site.
It might be a good idea to add a quick warning. Most effects form plugins are easy to reverse and some other people may try out the plugin without being clear on what effect it’ll have.
Thanks again, Andrea!
Viewing 3 replies - 1 through 3 (of 3 total)
The topic ‘[Plugin: WordPress MU Sitewide Tags Pages] Depopulate on Disable’ is closed to new replies.