WP 3.0 multisite Constructor
Hello! First of all – constructor is a great, awesome tool!!!
Is there any chance to clone completely all theme setting to all sites in sites network?
I use WP 3.0 and have over 10 sites, every time when I creating new site, I need to do a lot of thing to theme it with my default theme.
You can save your changes as custom constructor subtheme and use it for all sites.
Awesome tip! 🙂
Yeah, tip is awesome, and really helps me. But, it impossible to assign constructor-subtheme to all sites in one click =(. It is possible only for main theme – constructor!
I haven’t looked, but if Consturctor makes a custom theme as a child theme, just set that as the default for all new sites.
It’s currently not possible to assign a specific theme to all blogs from the backend in one click.
Further to my post the theme customisation options don’t display for non-Super-Admins on a WP3.0 install. To get the options to display requires the following: In Admin.php replace edit_themes with edit_theme-options. Unfortunately this leaves “edit_themes” displaying at the top of the theme customisation page. Hopefully someone will come up with a more elegant solution.
And the problem with the solution in my post above is that, on a 3.0 site, allowing non-Super Admins to access to the theme customisation options also gives them access to the CSS. The theme could end up very messy, very quickly once a few users start editing it. Is their a solution to this mess?
There is a problem with this solution. When I click to chose one of the 5 themes a message displays: The page at…says: All data was reloaded from theme config. Continue?..
Clicking OK leads to a page that says: edit_themes
Warning: Cannot modify header information – headers already sent by (output started at /home/realesta/public_html/wp-content/themes/constructor/libs/Constructor/Admin.php:1) in /home/realesta/public_html/wp-includes/pluggable.php on line 890
Oh the joy of upgrading early 🙂
allowing non-Super Admins to access to the theme customisation options also gives them access to the CSS. The theme could end up very messy, very quickly once a few users start editing it. Is their a solution to this mess?
It depends on where the css is stored. A separate custom option? Because they should not have access to the theme files themsevles. If it;s a custom option, if done correctly, should save copies specifci to that site somewhere.
Warning: Cannot modify header information – headers already sent by
This usually means you’ve got a blank space after the last ?> somewhere, probably in the last file you edited. 😉
Wouldn’t be an upgrade issues either, as a new install would have the same issues with this particular theme. The dev is going to have to account for multiple sites.
replace edit_themes with edit_theme-options
I think it should be switch_themes.
Yeah, pick one.
I think it should be switch_themes.
It does work with switch_themes.
constructor/libs/Constructor/Admin.php line 246
This “trick” works with most themes
BRILLIANT! Was searching all over about this issue with another theme – not displaying the theme specific options for the subsite users.
Replaced edit_themes with switch_themes in a corresponding PHP file did it!
Anyone care to elaborate a bit what that actually does? Any potential drawbacks? Any other consequnces I may not be aware of right now?
It’s a user permission level.
In 3.0 only Super Admins can edit themes. If you have one site, there’s no problem. It only really shows when you have a network, and now have multiple admins. they shouldn’t be able to edit themes anyway, not on sub-sites.
so there’s this quasi role permission thing that fixing that options page does. Any user that *should* be able to switch the theme on the blog, shoudl also be able to access the options page.
Andrea, are you saying subsite admins should not be able to edit the site’s theme? How else would they make needed changes. For example, my theme allows in it’s options to place certain images in a slideshow on hte home page. Those images are not generic, really are part of the website’s content, which should be controlled by the subsite Admin.
Or does it mean that the theme developer did not implement it correctly by including content related operations in the Theme Options section?
I got the workaround I needed, just trying to clarify if I am thiking about this the right way…
- The topic ‘WP 3.0 multisite Constructor’ is closed to new replies.