not understanding overrides

[lucoral]

Aloha!

 

I am trying to correctly modify core css files, but I am finding the only way to have the change take effect is to modify the core files. When I copy core css files to either /themes/my theme/css/modules/folder I want to change/file I want to change.css or alternatively to /themes/my theme/modules/folder I want to change/file I want to change.css, no change occurs when I edit. (The spaces are merely for legibility, not in the directory structure, of course.) The core css file is read.

 

If I am understanding the procedure correctly, the override folder is only for changing classes and controllers. Reading nethercottconstructions.com's advice about best practices, he recommends the /themes/my theme/modules/ approach to changing .tpl files, and not touching the .php files. I try that without success for css files. So then I thought to try the /css/modules/ approach, still no success.

 

I dump all the files in smarty/config, no success. I have the force compile=yes and cache=no set in performance. I refresh and ensure my browser's cache is off, showing the current real page, no success.

 

Is there a good standard tutorial on this whole overrides issue? I'm running 1.4.8.2 on bluehost.com, Apache 2.2.22, PHP 5.2.17 on a dedicated server.

 

Piggyback question - how soon will 1.5 be ready for real use? A month, a year? Just curious if I should wait to learn the newest release.

 

Thanks!

 

Martin

[lucoral]

Bueller? Bueller?