Hi and Happy New Year, SomebodySysop;
i'm using 2.6 of og_user_roles with the latest version of og_user_roles.module.5.x-2.7.patch.
i just started reinstalling OG and OG User Roles on our test site and noticed that with OG User Roles switched on and without any groups defined on the site, all the various themes that were defined with the taxonomy_theme module plus the Administration Theme, no longer show up and everything is the default system theme for both anonymous and authenticated users. Turn off the module and all the themes show up again.
Is that an effect of the intended behavior of the module? If so, how should i assign themes to various nodes, views etc.?
thanks,
b
Comments
Comment #1
somebodysysop commentedI have never installed nor used the Administration or Taxonomy theme modules. The OGR module obviously causes problems with these modules. I do know OGR was modified recently to support theming by group:
Not knowing anything else, my guess is that this is probably causing the problem. So, the question is, how to resolve it? As I don't use these themes, but you do, I would suggest you dig a little deeper into what should be done to accomodate them on our end. Point me in the right direction, and I'll see what I can do on my end.
Fair enough?
Comment #2
ben soo commentedYep, fair enough. i'm not a programmer though and it'll take me time to get anywhere.
However, "Administration theme" is in the Drupal core:
admin/settings/admin
i tested that with OG User Roles, without the taxonomy_theme module installed, and that combo also shows the same problem.
b
Comment #3
somebodysysop commentedThen, let's start with the Administration Theme. When I go to admin/settings/admin, and change the default admin theme, it changes and stays changed while I am logged into admin pages.
When I log out, the pages I see are the theme selected for the site.
In short, everything works as expected.
What happens when you change the admin theme on your site?
Comment #4
ben soo commentedThe admin pages default back to the system theme when i turn on OG User Roles, from the separate theme i picked for them.
i know i haven't got my observations well factored out: will report back with clearer progress notes on Saturday or Sunday. Must attend to other stuff in the meanwhile.
i'm running the Dec.28th Drupal 5.x-dev core, patched for memcache and menu_per_role. i started building stuff in this install before the official D5.0 release; while i've kept the code free of obsolete patches and discarded modules, and i try to remove left over tables from discarded modules, there may well be traces of my module trials still in the database.
Also i likely have too many modules still enabled.
Recently had various unexplainable problems with this site, including one triggered by the domain module where anonymous users got edit rights to all nodes. That module is currently removed.
Right now the Views RSS stuff don't work, among other minor annoyances.
Am starting to consider starting a fresh install and putting the existing content into it. A big enough job i don't want to think about it.
Comment #5
somebodysysop commentedUnfortunately, this is not my observation. OGR is already installed when I change the admin theme, and the admin theme stays changed. I can also select individual group themes that are maintained when OGR is turned on. As stated before, I can't speak to the Taxonomy Theme module because I don't use it.
I'm running the Druupal 5.5 update (all core files updated to 5.5).
Sometimes what happens is that Module A will have an effect on Module B that will cause a problem that goes away when Module B is disabled. The problem is trying to figure out if, in fact this is the case, and if so, what is Module A?
I would recommend putting up a test site so that you can more easily install/uninstall modules to test the various effects.
Comment #6
ben soo commentedApologies for the week's delay: it took longer than i thought to sort that start-of-the-year stuff off into the right tracks.
i've messed with our site for the last couple days, turning modules off and on, removing as many as i can without losing content.
It's running OGR 2.7, OG 5.0 and Drupal 5.6, with all other modules that i can't remove updated to the latest versions.
What i'm seeing is that with OGR turned on the anonymous user see all the themes that the site has implemented, whereas any authenticated user only see the main system theme. Doesn't seem to matter what other modules are enabled.
Next i'll start working on moving the site content to a fresh Drupal installation, but that isn't going to be easy.
b
Comment #7
somebodysysop commentedWith which theming? Administration or Taxonomy?
Comment #8
ben soo commentedEither one. i even uninstalled Taxonomy Theme completely and it's still happening.
HOWEVER. i started up a new, content-free D5.6 installation, with
OG5.0
OGR2.7
latest Memcache, Image, Pathauto, Panels, Views, CCK and Domain modules
-- all the stuff i don't think i can do without, and nothing else. Theming seems to behave as expected with all that.
It's still being set up though, no heavy testing yet: no subdomains, no blogs, no defined taxonomy or path themes, no content.
Comment #9
somebodysysop commentedThen, just need to find the module that we're conflicting with.
Comment #10
ben soo commentedi'll be damned. The problem isn't resurfacing. Have run some not-very-extensive tests.
Am in the process of making a list of all the DB tables that have our content in them. Then i'll start exporting and importing them, pretend like i actually know what an SQL statement is.
--btw i'm seeing that at least one module, Viewtheme, throws up SQL warnings to the page even when it's disabled, and the warnings only stop when the module is uninstalled. So, even when a module is disabled it still interacts with the Drupal core?
b
Comment #11
ben soo commentedOK, i've gotten our site, under its new installation, back up to the same level of complexity that the old installation had, and have gone farther with subdomains and content, and everything pretty much works except for what looks like a conflict between the Domain Theme submodule and the Taxonomy Theme module. That still messes up theming, but that ain't an OGR problem.
Onwards and upwards (with the occasional upside-downwards)!
b
Comment #12
somebodysysop commentedComment #13
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.