Page 1 of 1

Groups in SPv2

PostPosted: Mon Feb 06, 2006 12:19 pm
by Gangolf Haub
This weekend there was a db-upload from SPv1 to SPv2. It appears that after the upload the relationships between mountain groups and their respective mountains are a bit mixed up. Part of the reason for this is that some groups cannot be identified. All of you group maintaiers please check that the name contains the words "group" or "area". Prominent examples are

Dolomites Mountains -> Dolomites Mountains Group
Alps (Eastern Part) -> Alps (Eastern Part) Group

The switchover to SPv2 will occor sometime in the next two weeks so please change the names of your groups. After the swichover you can revert the names to their old forms.

One more suggestion: in SPv2 there is a table of contents at the beginning of the page. This interferes with the large panoramas in the overview sections (the panos get overlayed). Those of you who maintain pages with panos should remove them from the overview section. For my own pages I created new sections "Panoramic View".

Re: Groups in SPv2

PostPosted: Mon Feb 06, 2006 6:31 pm
by Gabriele Roth
Gangolf,
a wide pano joining some pics or even a single wide format photo ?

Re: Groups in SPv2

PostPosted: Mon Feb 06, 2006 6:58 pm
by Gangolf Haub
The problem actually is that with a screen resolution of 1024 x 768 even the 650px shots interfere with the toc. But that is taken care of by automatically placing them below the toc or by using the new medium size format (which is 500px wide). The worst thing that will happen is that you get a white space at the top.

Wide panos, or pictures embedded in div-tabs, are not recognized as pictures by the migration program and thus remain at the top of the page. In that case the toc is (partly) invisible. Therefore it would be better to move the panos to the end of the overview or to a special section somewhere below.

Anyway, Josh & co are not finished with the migration routines - I hope that the large 650px pics will be automatically converted to medium size which fits perfectly. It is a matter of coding (and time) though.