A weird problem:
In 7.x-2.0-beta2+28-dev I could not use bootstrap in profiles/myprofile/themes/bootstrap so I moved it to sites/all/themes/bootstrap and could use the theme AND create a subtheme. Neat stuff.
Now when I download latest dev (7.x-2.0-beta3+12-dev) I can use Bootstrap in an installation profile but the subtheme doesn´t render any css. I also tried putting both in sites/all/themes but no success.
Comments
Comment #1
busla commentedUpdate:
A serious noob mistake. Forgot to disable CDN.
The status is that neither Bootstrap or my subtheme work in an installation profile.
Comment #2
busla commentedThe problem seems to be related to beta3.
I installed 7.x-2.0-beta2 (from december '2012) and everything works fine, both in sites/all/themes and profiles/myprofile/themes
I can also create a subtheme without a problem.
Comment #3
markhalliwellHonestly, I cannot reproduce this. I have had the bootstrap base theme located in
profiles/myprofile/themesfor a while now, I do not believe this is a bug in this project. I place all sub-themes created insites/all/themes, it sounds like maybe your install profile didn't install correctly or something and the system isn't including the profile in the search directories maybe?Verify that your install has the correct
install_profileset in the{variables}table or if you use drush:drush vget install_profile._system_rebuild_theme_data() calls drupal_system_listing() which includes the profiles directory in the search dirs:
Comment #4
busla commentedwell, I´m not using the bootstrap base theme project.
Comment #5
markhalliwellI honestly don't get what you're trying to do. Not to sound insensitive, but you are creating issues in this project (Bootstrap, which is a base theme) and are claiming that things aren't working when in fact they do. I am curious what it is you are trying to achieve. Marking this issue appropriately.
I'll grant you this, yes, there has been some confusion over where the project should live and how to get sub-themes working, but a lot of this has already been solved and/or waiting to be committed.
Comment #6
busla commentedI apologize for not being clear. What I´m trying to do is to make my own sub theme of Bootstrap (not the starter kit) and use it in my custom distribution (profile). For some reason I was able to do this using beta2 of Bootstrap but not latest dev.
I´m not able to reproduce this now after a couple of clean installs, so I´m kind of lost. The Bootstrap theme works in both profile and sites/all/themes.
Everything works as designed and I should make proper tests before I post an issue.
Thanks for a great project :-)
Comment #7
busla commentedOk, I want to open this up again. What I wrote above was a mistake since my custom feature turned on CDN again on my fresh install.
I´m reverting back to beta2. I have no idea why it works, but it does, while the latest dev does not work without CDN.
With beta2 the theme works when located in profiles/themes and my subthemes work aswell.
Again, I apologize for spamming the issue queue :-) please let me know if there are some tests that I can do to help figuring out why this is happening.
THanks.
Nonni.
Comment #8
markhalliwellThe sub-theme starter-kit was committed to dev yesterday. There is a ton of documentation included with it. Before this, implementing sub-themes was rather difficult and hard to understand (which is what you're encountering). Prior to #1957620: [META] Refactor code to allow for either CDN or sub-theme source files. and #1846736: Remove jQuery CDN setting in favor of using jQuery Update module being committed, this project also made a lot of assumptions in where the Bootstrap framework lived. This caused a lot of headaches for sub-themes. So unfortunately, I am re-closing this as "works as designed" because that's how prior releases were designed. A lot of these problems you're encountering has already been addressed and fixed in the latest dev.
I understand that from your perspective it is frustrating that a stable release is hard to work with and contains several bugs for creating sub-themes. This is why I made the effort to clean them up and became part of this project. Until a new release can be made, I recommend you work from the development branch. It isn't that I cannot help you figure out the issues in the prior releases, but rather that I do not want to. Implementing sub-themes will be far easier in future releases and this will be the direction of this project moving forward. Any issues you encounter should be against the latest dev, not prior releases.
Comment #9
busla commentedI totally agree.
I started using the starter theme kit a week ago but encountered problems that I didn´t know how to fix so I reverted back to beta2. I´ll look at the starter kit again.
Nonnni