8
Quote:
Zap_English wrote:
...
And I'm using clones of Publisher, which xBootstrap doesn't handle.
...
xBootstrap's look comes from override templates in the theme. The theme's templates need to be cloned, too. The publisher clone process does NOT do that.
When you clone publisher, it creates clones of all of its templates under the new name. You would have to manually make a copy of the xbootstrap/modules/publisher folder and templates to match the new cloned name.
For example, if you clone "publisher" to "pubclone" then you need to copy xbootstrap/modules/publisher to xbootstrap/modules/pubclone and then rename all the templates from publisher_*.tpl to pubclone_*.tpl. Also, there are things in most of the templates which will need to be adjusted, too - variables like $publisher_url, included templates like db:publisher_header.tpl, css class names publisher-*, and constants _MB_PUBLISHER_* would all need to be changed too.
The clone function makes a lot of little changes to the files. It would probably be possible to make a "clone publisher templates in a theme" function based on the existing cloning code, but it could get messy.
Crazy idea that should work. You could copy the xbootstrap/modules/publisher templates directly into the publisher/templates directory and then clone it. That way the cloning process would make all the needed changes. The only downside would be that any clones would be locked into xbootstrap -- not really a problem if that is what you are using. Might be worth trying.