I have an older version of my project with 3 pages. Then I built in the same project a new page nr 4 and saved it in a new project version. Now I found, that in the new version something went wrong with the other pages (no problem with the one that's new).
So I would like to use the older project version with the good working pages 1-3 and import only the new made page nr. 4 - without having to rebuild everything in the elder version.
But when i make a Component of the page or of parts of the page I always get a mismatch after importing. Worse to repair page 4 than to rebuild all.
Yes Inger, it's the project where you built the index... Will I have to make all class names new in page 4 ? (It's a lot)?

Yea SD is very version specific. Best practice is when you want to upgrade a file to a new version make a seperate folder and copy the .rsd file there. Then open it and convert.

If you don't do this you are correct it converts the file and you will not be able to open in older versions of the software.

Thanks Steve - good hint - but I have another problem:I made an english / german site. So I have 2 seperate projects. Now I'm making a new page using the english project. How can I get the whole page into the german version - tried to make a component from the "all-inside" container - but didn't work. Is there a cheap way ?

The copying of whole pages as components usually works fine as long as all the elements in the page are wrapped in one container, and that container is used to create the component.

When adding any component to a page, there are some things to keep in mind, which I believe (please correct me if I'm wrong) are as follows.

1. For settings made in the Styles panel, Site Designer (SD) uses just one CSS file (main.css) for the whole of a project. The matters below flow from that fact.

2. If an element, say a paragraph element, has settings applied to a class name, those settings will affect all the project's paragraph elements which have that same class name. On may, of course, change some of the settings of an individual such paragraph element by giving it an ID and applying settings to that ID.

3. If an element, say a paragraph element, has settings applied to its ID, those settings will affect all the project's paragraph elements which have that same ID.

4. If one adds a component to a page in a project, and the component includes class names or IDs already in use within the project, SD protects one from the mess the above facts might make, by adding where necessary a suffix (e.g. '-1') to the component's shared class name or ID.

5. One should not remove such suffixes unless one is sure by reference to the above information that one will not upset the settings of other elements in the project.

Frank

I think I have been a bit careless with class names. Your explanation ist very helpful. Thanks Frank.