Using Sections Module for two groups (created with Organic Groups) to be themed differently. One is a green theme (node/5) the other brown (node/2). Sections works properly with both nodes but with only their home page.

The issue is that when the path is specified as node/5 and when I am in the green theme and then select comment, reply or some other node, the theme changes back to the default (no longer green). I assume that the path is not stated or correct. The path for accessing a comment when in the green theme is:

http://localhost/drupal/node/18#comment

Note: This page 18#comment returns to the default theme when selected from node/5.

The plan is to set up Drupal for a number of groups each with their own theme yet using only one Drupal installation. Thus the need for Sections to theme each individual group.

Looking information from someone with experience in using these two packages together (Sections Module and Organic Groups) or assistance with establishing the path to maintain the correct theme identity for all pages attached to a specific theme.

Jim

Comments

Bèr Kessels’s picture

Sections module uses the regexp engine, so the regular expressions will be similar to those for blocks. Read more here: http://drupal.org/node/17170

Alaska’s picture

Title: Sections Theme Not Moving With Content » Sections Content
Category: support » feature

Yes, I printed out that page a few days ago. However in thinking through the logic it would appear that Sections was not designed to perform the function that I have in mind in that it can not distinguish between blogs and other common entries submitted by different groups while all on the same site.

The DB would have to be modified to make sure that when an entry is made that it is tagged to a certain group. i.e. blog entry on node 12 is made by the green group - with comment 21 by the blue group, etc. Or any blog entry by the greens will be tagged corrected to their group, etc.

Then when the page is displayed the correct theme is applied to the correct page by consulting the DB table. This looks like a future feature request rather than an issue with the present Sessions Module.

Jim

Bèr Kessels’s picture

Status: Active » Fixed

in the latest version the regexp engine has been updated. and we allow PHP input.

Anonymous’s picture

Status: Fixed » Closed (fixed)