CSS not generated for default site template(s) when using install profile

Hi Merlin,

Thanks for your reply.

It seems indeed that the css files are not generated on install. I tried copying the files that get generated when I 'touch' the default site template into my profile files but that doesn't work either. In short, if the files are provided along with the install profile from the start I see the same issue.

My install profile flushes all caches and runs a full database update when it finishes. It uses feature modules to fire the contrib module installs, provide the template, node_view, etc and configurations.

What would be a fail-safe way of asking ctools to generate the CSS on install?

I'll delve into the caching that's going on. I'll see if something gets exported or is included in some other way in the profile files that's preventing the re-generation.

I am exporting a variable called 'cache' but I'm under the impression that this is a performance setting and not something containing cached information. However, I'll put on some gloves start dissecting.

Thanks again and I'll post back as soon as possible.

Hi Merlin,

I have done some digging but I'm not having a lot of success.

I started out with removing certain elements from my install profile. I removed the update db part, I removed additional flushing of js and css, and finally removed the reverting of my features that happens at the end. Neither of which solved the issue. All of the above are not really expendable from my profile, but that aside.

The status message does display that the folder sites/default/files/ctools was created. Also, if I open up the sites/default/files folder in my ftp client, I see:

- A folder called 'css' and a folder called 'ctools' created during install.
- The first sites/default/files/css directory contains several files with hashstrings.
- The ctools folder also contains a folder called css and a folder called style.
- The css directory in the ctools directory contains one hashlike file
- The style folder has a sub directory called _temporary with a folder sporting a hashed name inside it.
- Inside of that _temporary folder are .png images.

So this is all looking quite well. Except for the fact that I'm wondering if the sites/default/files/css folder is supposed to be created, since there is also a css folder inside sites/default/files/ctools. But still, when I create content I get the distorted display. This is immediately resolved by saving the default site template without actually changing a single thing. What happens after I've done this, is the appearance of one extra hashed .css file in the sites/default/ctools/css folder.

The default site template has a flexible layout without sidebars and such. It is used by several node_view variants that have flexible regions and also 1 fixed sidebar on the right. Preceded by 1 flexible left sidebar and a flexible content region.

I hope this info brings to mind an insight and I'm looking forward to your reply

Hi Merlin,

Feeling both a bit silly and utterly delighted as well, I just upgraded to the latest .dev version and the problem went away.

So in light of this I can at least indicate that this is an issue with the 1.1 version and the css is not generated on install there.

Thanks for your time and not to say the least for yet another brilliant module!

This issue http://drupal.org/node/906436 has motivated me to re-inspect this specific issue. I'm marking it as a bug report, for as it turns out, my default site templates no longer work when I use the latest .dev. For I have no regions at all in my template, I prematurely thought the css got generated on install. Which is probably not the case; the templates are no longer functional because of the mentioned issue with overriding page.tpl files.

I have to say 'probably' because if I use the patch provided my install profile fails to install due to a strongarm failure. So I can't test it out because my issue is specifically relating to the install process.