Hi,
is there a reason why you did not put all the *.tpl.php files in a /templates/ subfolder?
This is a common habit when creating themes in Drupal as it allows to have a cleaner file structure.
Thanks,
Hi,
is there a reason why you did not put all the *.tpl.php files in a /templates/ subfolder?
This is a common habit when creating themes in Drupal as it allows to have a cleaner file structure.
Thanks,
Comments
Comment #1
tlattimore commentedI really like this and take is best practice on all themes I develop currently. My only hesitation is that it would require a flush-ing of the theme registry after update, but I think I will just make strong note of that in the release notes and do it anyway.
Comment #2
tlattimore commentedCommitted to branch
7.x-1.xand will be included in next release.http://drupalcode.org/project/boron.git/commitdiff/9dbc83d
Comment #4
geerlingguy commentedI'm now getting a WSOD on my dev site after trying to update to Boron 7.x-1.4. I tried clearing all caches via drush, and even tried Registry Rebuild, but I'm still getting the white screen.
I just get a bunch of errors like the following until I downgrade to 7.x-1.3:
Can you explicitly outline the steps needed to upgrade a site to 7.x-1.4? Running update.php, clearing all caches via drush, and doing a registry rebuild didn't do it for my site...
Comment #5
tlattimore commentedRe geerlingguy #4: I unfortunately cannot replicate your issue. In my tesitng the upgrade I upgrade the theme, and then clear all the caches (drush cc all) and I do not run into any errors. Are there any other caching mechanisms in place on your site that could be causing these errors?
Comment #6
geerlingguy commentedMaybe it's APC's cache; I have cache_bootstrap in there, and that is probably not getting cleared when I do a
drush cc.Comment #7
geerlingguy commentedYep, that was it; I had cache_bootstrap and cache in APC, and when I was doing
drush cc all, those two caches weren't cleared.