css control for ezpages? header graphics

[atracksler]

what do I need to name the css files to control things like the header graphics in my ezpages pages?

here is one:
http://216.246.55.121/~obaby/shop/in...id=1&chapter=0

Thanks in advance, ad

[kobra]

Start by reading the css readme.txt in your css folder as it outlines the use of different css per page or group of pages

[atracksler]

I can control all the ezpages with the pages.css, but I want to control each ez page with a seperate stylesheet.

How do I control the ezpage with the ID of 1 aand the ezpage with the style of 2?

Thanks in advance, ad

[irischant]

I wanted this functionality too & did the following to achieve it...

Copy html_header.php from includes/templates/template_default/common/html_header.php & place in your custom template's common/ directory. Edit around line 65, put a comma after $tmp_products_id & on the next line insert the following for seperate ezpage & chapter styles:

                        '/chapter_' . $chapter_id,
                        '/' . $_SESSION['language'] . '_chapter_' . $chapter_id,
                        '/ezpage_' . $ezpage_id,
                        '/' . $_SESSION['language'] . '_ezpage_' . $ezpage_id

Now you can make a new stylesheet for each chapter number that you want styled named chapter_1.css , chapter_2.css , etc. AND for each ezpage id that you want styled named ezpage_10.css , ezpage_20.css , etc. (Note: ezpage styles will override chapter styles if the same element is styled in both.)

Hope this helps!

Christina

[fierystorm]

I'm curious about one thing that does not appear to be found anywhere else in the forum save for something similar within this thread.

Just what would you name a .css to control all of the ez-pages? I've tried multiple combinations and checked out all of the read-mes but without much success. What I am attempting to do is control the background images on all of my ez-pages.

Any takers? I would appreciate this obviously simple step that is eluding me

Thanks!

[fierystorm]

Ahh nm, I found the problem. It was described as pages.css when it should have been page.css

Got it fixed now!