Sections are not working for specific content types
valuewing admin - December 24, 2008 - 12:08
| Project: | Sections |
| Version: | 5.x-1.2 |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
We have installed section module. We have defined certain paths(for ex, content*) to have separate themes using sections module. It is working as expected expect certain content types. For blog content types, it is not picking the new theme assigned in the section. For other content types, it is choosing the new theme assigned in the sections settings page. We are using path module. but all content types are stored under the path "content" only. Any ideas?
#1
While the module name doesn't suggest it, you can specify themes per node type using Taxonomy Theme. And it works like a charm. I, too, didn't get sections to work for content types...
#2
To assign a theme to single nodes you don't need "Taxonomy Theme". Sections only does not provide you a theme selector in the node edit form (what Taxo theme does), but this will come in a future version in sections... but nevertheless - you can add the internal URL to the path filter texarea. No difference in functionality.
I need to test this myself with blog content, but wonder why this should not work. Maybe a different section with higher priority or so...
#3
I confirm this bug, a custom content type will not 'hold' the sections settings and will revert to default theme. (Version 6.x-1.2)
#4
Could you explain us what a "custom content type" is, please? There is no logical difference between content types. What modules have you installed? Please try to disable on by one or repro on a test system and find out what module cause this incompatibility. All modules doing anything with theme switching should the be the first to test.
#5
I'm having this problem too. It seems that the path_to_theme() function is still returning the default theme name, which causes my main theme's "node-story.tpl.php" file to be loaded rather than the special theme's "node.tpl.php". I'm still looking into this, so I'll post if I figure out the details or find a workaround.
#6
Please provide a list of your active modules.
#7
I still cannot repro. Here is what I've tried:
1. I've created a node type "test1"
2. Created a new node with this type and some dummy text (nid 70)
3. Created a section "Test1" with path "node/70" with garland
4. Tested if theme switching works - success
5. Added a node-test1.tpl.php to the garland folder
6. Edited the node-test1.tpl.php and added some Dummy text inside to provide an identifier that the template has been loaded
7. Reloaded node/70 again
8. Garland theme is still used and the dummy text from node-test1.tpl.php is shown - success
Sum up - nothing seem to be wrong. If you have a different repro case let me know... also don't forget to provide a list of active modules as I expect there is a incompatibility caused by modules order...
Only to note - "Taxonomy Theme" may be incompatible with sections (untested myself) like Sections may be incompatible with Taxonomy Theme!
#8
Automatically closed -- issue fixed for 2 weeks with no activity.