I tried Theme Settings API 5.x-2.x-dev, 5.x-2.5 and 5.x-2.4. Neither current stable versions of Zen nor Denver will display any theme specific settings. I tried deleting cache to no avail.

Comments

johnalbin’s picture

johnalbin
they/他
Primary language English
Location Taipei, Taiwan
commented
Version: 5.x-2.x-dev » 5.x-2.5
Status: Active » Postponed (maintainer needs more info)

FYI, the theme settings forms are never cached. So it's not a Drupal cache issue.

I'm the developer for both Theme Settings API and Zen, so you're definitely talking to the right person.

If you use Zen 5.x-0.8 and Theme Settings API 5.x-2.5 and enable the theme and the module, you don't see any settings in admin/build/themes/settings/zen or admin/build/themes/settings/zen_classic? Do you get any error messages?

webavant’s picture

webavant commented

I realized that the problem was caused by the path not being matched as a result of using the i18n module. The theme specific settings show up fine when I access the path you suggest, but i18n rewrite the path to be en/admin/build/themes/settings/zen_classic.

Thanks! Great stuff.

johnalbin’s picture

johnalbin
they/他
Primary language English
Location Taipei, Taiwan
commented
Title: problems with zen and denver » incompatible with i18n
Component: Miscellaneous » Code
Category: support » bug
Status: Postponed (maintainer needs more info) » Active

i18n adds a language-specific prefix to all paths and themesettingsapi checks the path before loading the main body of the code (since 5.x-2.4.)

Specifically, themesettingsapi.module checks arg(0) == 'admin' before HOOK_init() calls are made. But i18n doesn't remove it's language-specific path prefix until i18n_init() is called.

johnalbin’s picture

johnalbin
they/他
Primary language English
Location Taipei, Taiwan
commented
Version: 5.x-2.5 » 5.x-2.x-dev
Status: Active » Fixed

Fixed in 5.x-2.6.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)

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