| Re: How to use one concrete theme only for a module? |
by fiammybe on 2012/5/22 2:57:43 Could the theme to use become an attribute of a symlink? Then it would be very easy to do this kind of thing. I think that's in the direction the defacer module works. If you change enough code (HTML, CSS or PHP), you can accomplish anything. That's not what people choose a CMS for, most of the time they don't want to (or can't) change the source files. So we should look into making requested features available in the ACP when they have enough interest for our projected user base (the 80% rule). |
| Re: How to use one concrete theme only for a module? |
by skenow on 2012/5/21 12:12:09 Quote:
To override the theme completely on a page or for a module, you'll have to do the logic in the theme - the way a site renders starts with the theme, then cascades down to the module and then to the blocks. When you change the theme_set in a block or module, the theme has already started rendering. |
| Re: How to use one concrete theme only for a module? |
by debianus on 2012/5/20 7:20:04 Quote:
Yes, but it is a hard work and it seems strange that code is not working. Better wait the great Boiler theme and its skins options. |
| Re: How to use one concrete theme only for a module? |
by Will on 2012/5/18 13:57:01 you can create a big brother theme with just logic like if module == wiki include this else that. This is much easier in Boiler because of skins. :) |
| Re: How to use one concrete theme only for a module? |
by skenow on 2012/5/10 5:28:29 Does your theme for the wiki use a different HTML markup, or just different CSS? If it is just different CSS, you could conditionally include the CSS in the theme based on $icms_dirname Smarty variable. You could probably also do the same for the HTML portion, too. |
ImpressCMS is a multi-language content management system for the web. It is community-built, an open source project and based on the common web technologies of PHP and MySQL.
More information
