I now realize the two things are unrelated as far as the actual database structure is concerned, but I certainly made the connection and I assume others would as well that resetting the theme registry (or clearing all caches) should update the theme.info stuff as well. I spent quite a bit of time yesterday trying to get scripts I added to theme.info to show up before someone told me you had to visit the theme settings page. From a usability standpoint, there should be a more logical way to refresh that data that is clearly exposed in the UI, and I think the theme registry reset is the most logical place a parson might expect to find it (unless you add a separate menu item). I created a patch to add system_get_theme_data(); to drupal_theme_rebuild(), but I'm not sure if this is the best approach.
| Comment | File | Size | Author |
|---|---|---|---|
| theme.inc_.patch | 529 bytes | seanr |
Comments
Comment #1
seanrComment #2
moshe weitzman commentedGood idea. But calling that function does not rebuild anything AFAICT. You want to add a $reset param to both system_get_theme_data() and _system_get_theme_data()
Comment #3
seanrMoshe, that function fetches the .info files, parses them, and updates the database. See here:
http://api.drupal.org/api/function/system_get_theme_data/7
That should be sufficient shouldn't it? It appeared to work for me. Otherwise, please let me know what you mean by adding a reset parameter.
Comment #4
catchI don't think this especially needs committer feedback.
Comment #5
catch