When using 2 Omega subthemes (one as front end theme, one as backend theme) visiting /admin/appearance/THEME/settings completely breaks the system. :)

A better description of this could be provided, but it's an issue fubhy and I have already been discussing.

#1 backend-frontend-theme.patch7.49 KBfubhy
Members fund testing for the Drupal project. Drupal Association Learn more


fubhy’s picture

Status: Active » Fixed
7.49 KB

There was indeed a bug in Omega that caused the function that builds the theme trail to fail. But that's not all. There is a Drupal core "bug" (something noone has thought about before I believe) which occurs when the frontend and the backend theme use the same base theme. This "bug" causes the hook_theme_settings_alter function to be invoked TWICE in some cases (once for the backend theme and once for the frontend theme) even though we only want to display the frontend theme settings. This causes the backend theme settings form to override the frontend theme settings form => Saving settings for the frontend theme becomes impossible. I added a workaround to omega and alpha. However we might want to fix that in core too.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

fb-multimedia’s picture

This patch work for me thanks a lot !

2pha’s picture

manually adding the changes to 3.1 worked, thanks