Posted by spatical on April 3, 2010 at 7:41pm
6 followers
| Project: | Service links |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (works as designed) |
Issue Summary
Service links appears to have an issue with nodes that have been set to a custom theme via the module ThemeKey, I'm not sure whether the problem needs to be handled in ThemeKey or here in Service Links. The custom theme is not used when the content-type is selected to display service links.
I have also posted the note on the ThemeKey module: #754970: Skipped rule checking because another module already initialized the theme engine
Comments
#1
Confirmed the bug and changed priority to Normal - while this doesn't break the site, it does prevent me from using themekey and service links together.
I'm investigating and I'll post back if I find anything, but if anyone has any light to shine on this... Hints would be welcome! Thanks.
#2
As soon as I enable the "service links" and the "general services" module (version 6.x-2.0), one of my theme switching rules taxonomy:vid -> "whatever theme" becomes nonfunctional, whereas other theme switching rules continue to work.
#3
Could be a configuration trouble, here seem to work...
#4
I have to amend what I wrote in my comment #2 above:
It has nothing to do with rule taxonomy:vid -> "whatever theme". Actually for every content type configured to show service links, themekey did not work anymore. Themekey kept switching only for taxonomy listings, admin pages, etc. were service links are not being displayed anyway.
In the end I had to disable option "Menu Access Checking" in module Global Redirect to make Service Links and Themekey work together. I could easily reproduce this problem on another very different Drupal installation.
On the Global Redirect admin page it says for "Menu Access Checking":
... well, obviously I did experience very unexpected behavior. I have not analyzed in detail why this is happening.
#5
I have changed weight of ThemeKey module (database table "system"), i.e. -10, so ThemeKey runs before Service Links, and the problem dissapeared.
#6
Everything about theme initializing, has been fixed in dev long time ago.
#7
Cool could you deploy an official release as it took me quite a while to debug why Themekey wasn't working only to determine it was b/c of the Service Links module.
Thanks
#8
Hrm this is still an issue with the latest to be honest. I tried this out with the latest release and until I set the weight of service_links to something lower then themekey then it takes over the theme everywhere. This also conflicts with Organic Groups and other modules in their setting of theme -- so it's a bit more serious then one module.
Could you just change your install to lower the weight of your module to 10 or something?
#9
Tried again and don't see any issue, the problem was about the code in nodeload->load section, now this code has been removed, so could you provide the steps for reproduce your error?
#10
should be fixed in dev