phpwcms Support Forum

Hallo

I'm using Vers. 1.2.1 with Pagelayout CSS-DIV and here I have a 3 Columns, no Problem so far.

But now I want to make a second Layout for some Pages with 2 Columns (Left and Main)- and here is my Problem, cause for the Mainblock it uses the same mainBlock-Class from the frontend.css. My first 'solution' for that is to make a Copy of the frontend.css with another mainBlock-Class and select this in the Template for this Pages.

Is there a better way to do this, without to have 2 different frontend.css Files? cause I can't edit the second frontend2.css not from Backend.

Hi,

I think the best way to work with div and css in phpwcms is to choose custom (from template main block) in the page layout. Then you can easily do a tableless layout in your favorite editor and just paste one time in the main block in template section, with your own classes for the different blocks.

Much easier to work like this I think. Easier to see what you have done in a separate editor because the phpwcms form-fields are so small.

If you do not know how to set the div and css yourself, here's templates for you. http://intensivstation.ch/css/template.php

/ Gnolen

Hello Gnolen,

thank you for your Informations, but this is not what I want to do - I'm shure that it will work with Custom-Layout, but I'm testing now the CSS-DIV Method to see what is possible and what not.

So my question was more to find out, how it is possible to solve this in this Mode of the wcms - it makes no sense to me, that there is a feature what I can not use in all instances.

Maybe OG reads this and appends the functionality of the CSS-DIV Layout, so this will work too. I think it should possible to add the Classes something like a Prefix from the Layout-Name

Aha, so you mean that you want to use two phpwcms-made layouts? And the class .mainBlock should change according to this page layout?

Hmm, I prefer to set the layout totally outside phpwcms. So much easier to test designs then I think..

But we will see what Oliver will bring in the future. I hope that he will go for a xhtml-valid tableless(not tablefree but less) approach. I think that it will then fill a big hole on the cms market. And I think we can see this his resent releases a bit more..

Looking forward to dev 2!

/ Gnolen