Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
When using theme = theme_name in your profiles .info file causes the named theme to be set as the default but it is not enabled. This means that while the theme will display on the site you can not actually navigate to any settings pages for the theme until you enable it.
Comment | File | Size | Author |
---|---|---|---|
#1 | profiler-enable_theme-1149572-1-eojthebrave.patch | 691 bytes | eojthebrave |
Comments
Comment #1
eojthebraveComment #2
eojthebraveThis is a problem in the 6.x branch as well. Something gets called after profiler_install_theme() that causes the status of the theme to be reset to 0 despite the fact that profiler sets it to 1. Still haven't been able to track down what is causing this though.
Comment #3
eojthebraveSo here's what I think is going on in D6.
The second call to
drupal_flush_all_caches()
inside ofprofiler_install_components()
which causessystem_theme_data()
to get a called and in this context it disables all themes.So, we can either remove the second call to drupal_flush_all_caches() set MAINTENANCE_MODE = 'update' for drupal_flush_all_caches() or make our own version of drupal_flush_call_caches which uses _system_theme_data() instead of system_theme_data().
Thoughts?
Comment #4
mxmilkiib CreditAttribution: mxmilkiib commentedsubscribaa
Comment #5
q0rban CreditAttribution: q0rban commentedThanks! Committed.
http://drupalcode.org/project/profiler.git/commit/e9aa8e8
Comment #6
q0rban CreditAttribution: q0rban commentedMarked #923266: Using drupal_flush_all_caches() disables all themes as a duplicate of this issue.
Comment #7
jhedstromI don't see this on the latest 7.x branch, but oddly, it's in the latest release tarball.
http://drupalcode.org/project/profiler.git/blob/refs/heads/7.x-2.x:/prof...