Databases, designs, and other

Friday 05 September 2003 3:07:32 pm - 3 replies

3 replies

Author	Message
Paul Forsyth	Saturday 06 September 2003 2:31:08 am About the multiple databases. Ez 3.2 has a new package feature which allows classes to export and imported. Ez have used this feature to implement their demo designs, what you see when you execute the set up routine. Due to the fact that the package program is not due to be finished until Version 3.3 (no object/datatype etc support yet) they chose the multiple database option for their demo sites. This doesn't mean that anything has changed internally. Your sites can still co-exists in the same database through difference sections or different pagelayouts. Have a seach through the forums for packages and you will find discussions on that topic and what the system will eventually be capable of doing. I would suggest following the forums once 3.2 is released and you will see where the package system is going. About clean databases, there are sql files available with ez to do this. For example, inside the directory: kernel/sql/mysql/ you will find several files. 'kernel_scheme.sql' contains the ez sql tables, and 'cleandata.sql' contains fresh data to put into those tables. The same files exist for postsql. Take a look. Im not sure of how to refresh your systems on windows but you shouldn't have trouble here (im a linux person). I assume you have different pagelayouts for your different designs? Do you also have different sections for objects? If that is the case then it is relatively easy to check the section an object is in and deliver html with the correct css tag to display your content in the colour you need. Hope this helps! Paul
RW Wood	Saturday 06 September 2003 8:23:46 pm As to the last paragraph, perhaps I should have said that the only difference between the pagelayouts and languages is a different header image and minor differences in stylesheets. I don't want to have to change all the pagelayouts every time I want to make a change to the site. In other words, should I decide to have the site three column rather than two, I don't want to have to change templates for every design. My understanding is that with the override system built into ezP, I should be able to structure the site so that every design uses the same set of templates, but substitutes the different header images and style sheets as necessary. Take a look at www.every-nation.com to get an idea of what I'm trying to reproduce in ezPublish 3. Currently, the site uses version 2, and the problem I have is the one I described-- having to change too many files every time I want to make a minor change in design. There's probably a way to do what I want dynamically with php, but I'm don't know it well enough to know how to do it. Thanks for your input. RWW
Paul Forsyth	Sunday 07 September 2003 2:54:07 am I suggest reading up on what you can do with template logic. This is what you want to use to differentiate between site designs. For example: {section show=eq($node.section_id, 2)} <td class="design1"> {section-else} <td class="design2"> {/section} Note, that my eq code is from memory and may will very likely differ... But i hope you see my point. You can design your templates to work off different designs, and consequently change css whenever you need to without changing your templates. Read up on what you can do with templates. Since you mention doing what you need in php you will likely find you can do all you need in templates. You just need to spend a little time getting your head into the right mindset. Took me a while before it clicked :) Paul

Author

Message

Saturday 06 September 2003 2:31:08 am

About the multiple databases. Ez 3.2 has a new package feature which allows classes to export and imported. Ez have used this feature to implement their demo designs, what you see when you execute the set up routine. Due to the fact that the package program is not due to be finished until Version 3.3 (no object/datatype etc support yet) they chose the multiple database option for their demo sites.

This doesn't mean that anything has changed internally. Your sites can still co-exists in the same database through difference sections or different pagelayouts.

Have a seach through the forums for packages and you will find discussions on that topic and what the system will eventually be capable of doing. I would suggest following the forums once 3.2 is released and you will see where the package system is going.

About clean databases, there are sql files available with ez to do this. For example, inside the directory:

kernel/sql/mysql/

you will find several files. 'kernel_scheme.sql' contains the ez sql tables, and 'cleandata.sql' contains fresh data to put into those tables. The same files exist for postsql. Take a look. Im not sure of how to refresh your systems on windows but you shouldn't have trouble here (im a linux person).

I assume you have different pagelayouts for your different designs? Do you also have different sections for objects? If that is the case then it is relatively easy to check the section an object is in and deliver html with the correct css tag to display your content in the colour you need.

Hope this helps!

Paul

RW Wood

Saturday 06 September 2003 8:23:46 pm

As to the last paragraph, perhaps I should have said that the only difference between the pagelayouts and languages is a different header image and minor differences in stylesheets. I don't want to have to change all the pagelayouts every time I want to make a change to the site. In other words, should I decide to have the site three column rather than two, I don't want to have to change templates for every design.

My understanding is that with the override system built into ezP, I should be able to structure the site so that every design uses the same set of templates, but substitutes the different header images and style sheets as necessary. Take a look at www.every-nation.com to get an idea of what I'm trying to reproduce in ezPublish 3. Currently, the site uses version 2, and the problem I have is the one I described-- having to change too many files every time I want to make a minor change in design.

There's probably a way to do what I want dynamically with php, but I'm don't know it well enough to know how to do it.

Thanks for your input.
RWW

Paul Forsyth

Sunday 07 September 2003 2:54:07 am

I suggest reading up on what you can do with template logic. This is what you want to use to differentiate between site designs. For example:

{section show=eq($node.section_id, 2)}
<td class="design1">
{section-else}
<td class="design2">
{/section}

Note, that my eq code is from memory and may will very likely differ... But i hope you see my point. You can design your templates to work off different designs, and consequently change css whenever you need to without changing your templates.

Read up on what you can do with templates. Since you mention doing what you need in php you will likely find you can do all you need in templates. You just need to spend a little time getting your head into the right mindset. Took me a while before it clicked :)

Paul

You must be logged in to post messages in this topic!