Hello,

A very strange thing happens to me,

I was working with CSS of the APK user-profile, I don't know there was the good method but I was working into a file name 3fd2c3c6168b28afec2ff3f5f8e42c17.css into /www/sites/default/files/css folder. Why? Because working into my style.css of my theme folder wasn't working... no effect... (with css ID)
Everything was working fine, I could customize the user-profile.

5 minutes later, I upgraded the new dev. version of the date module. I run update.php.

and I go bac to my profile and no css. (screenshot_after)
and my 3fd2c3c6168b28afec2ff3f5f8e42c17.css file is gone...
So I sent it from my computer to my server without results...

It looks like the css files of the www/sites/default/files/css folder are generate each update.
So conclusion, we don"t have to work with these css files I think, don't we?

I disable the APK module, and my user-profile page looks good!! but without the my new css of course.
I enable the APK module but still "screenshot_after" still no css at all on the page.

So, I don't really know what's happens? I'm a newbe with css... It looks like really easy but never do it before.

How to fix all this?

Thanks :)

CommentFileSizeAuthor
screenshot_after.jpg48.68 KBjunro
screenshot_before.jpg50.54 KBjunro

Comments

vm’s picture

vm commented
Category: bug » support
Priority: Critical » Normal
Status: Active » Fixed

whatever changes you make make to the css file stored in the files folder you must also make to your style.css file in your theme.

there is a css file in yoru files folder because you are either using the color picker.module or the css aggregation in drupal.
if you had made all changes to style.css as well as the css file in your files folder the changes in style.css would be carried over.

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented
Title: Very Big Critical Bug with APK, I don't have a clue of what's happening! » Editing aggregated CSS file does not work
Status: Fixed » Closed (won't fix)

You have CSS aggregation turned on and are attempting to edit the aggregated file, which doesn't work and isn't meant to work. This has nothing to do with APK. If you want to edit your theme, you will need to turn the aggregation off. It's under performance.

Michelle

junro’s picture

junro commented

Thanks to reply me so quicky!

I'm not using Aggregator module but Color module, I disable it without results.
Still have screenshot_after.jpg

junro’s picture

junro commented

Why my user-profile page works when the APK module is disable et don't when enable?

Now all the css of my theme is not working :(.

I switched with Garlang, it's good, but still not the user-profile when APK is enable.

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented

I didn't say anything about the aggregator module. I said CSS aggregation. That's what makes those crazy files.

Both your before and after picture are with APK enabled so you need to be more specific about what doesn't work when it's enabled.

Michelle

junro’s picture

junro commented

All the CSS was not working now with my theme.

I restored a backup, but still the same thing with APK:

when APK is enable -----> screenshot_after.jpg (no css in the user-profile page)
when APK is disable ------> I've got the user-profile panel page without the APK blocks. CSS is ok.

I think is because I don't have the css file into /www/sites/default/files/css anymore.

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented

Ok, I can't really follow this but the bottom line is you can't edit the aggregated CSS files. You need to turn aggregation off to edit your theme. There's nothing more I can tell you there. This is core; not APK.

Michelle

junro’s picture

junro commented

I think I don't understand something, sorry.

I need to turn aggregation off?
What do I have to do this exactly??

vm’s picture

vm commented

administer -> performance

junro’s picture

junro commented

Oh! OK! f....g french translation! lol

junro’s picture

junro commented

Thanks Michelle, it's working.

Thanks for your patience, and sorry my english!

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented

@VeryMisunderstood: Thanks. :)

@Junro: Glad you got it working.

Michelle

junro’s picture

junro commented

Hello,

with aggregation turning off, under IE6, CSS is not working anymore with panel pages and some CSS code like Theme Fixed Width Size.

The link below explains why I had to turned it on.

http://drupal.org/node/336131

Actually, if I turn aggegation on again, CSS user-profile will not working (again screenshot_after.jpg) with the APK module enable.

If I disable APK with aggregation turning on , user-profiles CSS are good without the APK blocks and some configuration.

junro’s picture

junro commented

Conclusion:

I have 2 choices.

1 with Aggregation turning off
2 with Aggregation turning on

1 Everything is working except under IE6
2 CSS user-profile is not working (see (again screenshot_after.jpg)

vm’s picture

vm commented

what theme is in use?

junro’s picture

junro commented

Littlejazz but if I switch on Garland, it's the same problem.

vm’s picture

vm commented

Because it is also happening in a default theme, you may want to leave css aggregation off for the time being until such time as someone can check this.

css aggregation should be off while the site is bein developed. So this shouldn't be much of a problem for you at this time.

I'd take the time to reread the install.txt and/or readme.txt or APK, as I believe you may have missed a step along the way.

junro’s picture

junro commented

Ok, thanks.

ps: aggregation on, makes appear css files into /www/sites/default/files/css folder. But can we add some code in it?
Because my problem appears I added some css code in it (it was working), and the bug appeared after running update.php.
The css file where I was working on was not here anymore...

vm’s picture

vm commented

aggregation on, makes drupal consolidate all css into one file. This is NORMAL!
to make sure your changes to css stay in place you MUST, TURN OFF, css aggregation and make your changes to style.css in your theme.
When your site is FULLY DEVELOPED, you can then turn css aggregation ON, at which time the changes you make to style.css will ALSO be aggregated.

css aggregation IS NOT, an APK issue. if you have any more questions regarding css aggregation please create a post installation forum thread.

again, I state, turn OFF css aggregation during development of your theme. there is NO NEED for css aggregation to be enabled until your site is completed.

The same rule holds true for page caching. There is no need to have it enabled unless your site is finished.

If changes you make to style.css of the theme does not show ater changing. Clear your browser cache, and clear the drupal cache in administer -> performance

junro’s picture

junro commented

ok, thanks for these explanations ^^. Now this is very clear in my mind! :)

bcobin’s picture

bcobin commented

While you're on the subject of CSS Aggregation, be aware of the thread here. I see you're testing in IE6 - loading more than 30 external stylesheets (very easy to do) will break your layout in IE6 and 7. You really must have the CSS Aggregation turned on at the end - but only at the end - if you want your site to work in IE.

What VeryMisunderstood says is right on the mark - I would elaborate:

1 - Always develop in Firefox.

2 - Get the Firebug Firefox add-on - make sure your CSS and HTML validate before doing extensive cross-browser checking.

3 - When your site looks OK in Firefox, test it in IE 6 and 7. If it's OK in IE, you're done - you may want to turn on the CSS Aggregation to slightly accelerate performance, if you wish.

4 - If your layout is broken in IE, turn CSS Aggregation on and recheck the site. Your site should now display in IE fairly normally, with the differences you'd expect from their different standards.

5 - Turn Aggregation off and make whatever compromises you need to make in the base CSS to try to get the site to display properly across all browsers.

6 - Turn CSS Aggregation back on and check the site in IE.

7 - Repeat steps 5 and 6 until you've gotten things as close as you can in all browsers.

8 - If you still need more control over IE, make changes on your fix-ie6.css and/or fix-ie7.css stylesheets. (Just about all themes have these files, either with the names as described or similar. If you don't have them, there's documentation elsewhere that will tell you how to create them.) Disable and the re-enable CSS Aggregation and repeat Step 7 as necessary.

You may be able to keep the Aggregation on while you're changing the fix-ie.css - I forget. It will be easy enough to see if your changes are happening on reload.

I know this sounds like a real pain - it is. But there's no other way that I know of to ensure your site works in all browsers. Hope this helps; I was really going nuts until I found this IE limitation. Good luck!