sIFR Module blocks editing custom block regions
rickvug - July 13, 2006 - 21:54
| Project: | sIFR |
| Version: | 4.7.x-1.0 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
When using custom block regions in 4.7 (as per http://drupal.org/node/29139) custom block areas are not editable. For example, the site I built has no right sidebar but has two other additional regions. When I have the module enabled none of these are block areas are available in the blocks administration area. Moreover, Blue Marine shows up instead of the custom theme.
This bug is reproducible by simply turning the module off and on. The only non core modules enabled at the time of testing was Views and Path-Auto.
#1
It sounds like SIFR is trying to swap out something that you don't want it to be. Try changing or deleting your SIFR rules and see if that's the problem. My guess is that you need to have more CSS specificity in your SIFR rules.
#2
Sorry for taking a bit to get back to you about this. The chances that this is a CSS seclector issue is next to nil. This is my one and only selector: body.section-patterns #titlewrap h2. I changed this to #titlewrap and nothing changed.
With SIFR turned on my custom theme does not show up in the blocks page at all. It shows Blue Marine for my custom theme. When I disable SIFR the problem is gone. For the record (in case the information helps), the default theme is custom, when I am logged into admin, the theme is Blue Marine so everything fits.
Let me know if there is anything I can check for you to help debug.
#3
I've tried sympal theme with a clean Drupal 4.7 install and only sIFR enabled and it is working. Sympal theme implements only custom regions.
Could you please try the latest version of sifr module? And if still needed, try also disabling any other modules for testing, please.
#4
Without further information I'm obliged to mark this fixed.
#5
Just following - marking as fixed is right. No one else seems to have this problem and I was working with a fairly complex site. It was hard to tell where this bug was really coming from.
Thx,
Rick
#6