Sort order of exhibitions on front page

[macke]

Hi,

Is there a way I can automatically have my exhibitions listed on my front page sorted by the latest/newest one first?

As it stands, it sorts them by their ee_order ID. If none has been entered, i.e. defaulted to '1', it will list these as oldest first, newest last.

Since my logic is reversed from ee's, it's a bit of a pain to go in each time I create an exhibition and make sure the sort sequence lines up.

It would be easier if a similar sort mechanism as with the sequence of photos in the exhibition (i.e. mouse clicks) could be implemented. Or something similar to pbase, where the sequence is specified by numbers, e.g. 10, 25, 20, 13, 19, 15 etc, but each time the index page is reloaded the script recalculates them to 10, 20, 30...

--max

[cferrero]

If you use the 'set exhibition order' page (under 'EXHIBITIONS'), you can enter the display order for all your exhibitions.

[macke]

Correct, but then I have to go in and update this each time I add a new exhibition. And as EE defaults the exhibitions to the newest one last, I have to shuffle them to get the newest one to the top of the page.

What I was looking for was a simple way to not have to worry about the set exhibition order and rather have the latest exhibition defaulted to the top of the page, i.e. first.

In the future, ideally, I'd like to see a more developed method of re-arranging exhibitions. With groups and subgroups, easy arrangement (either by the mouse-click method of arranging images within an exhibition or the pbase styled re-calculated "sort index", or ee_order).

--max

[MMCM]

I'd like to have better ways to order exhibitions & photos, too :-)
Currently I enter the shooting date of an exhibition in the 'set exhibition order' page as a NEGATIVE value, e. g. "-20050717" (without quotes). Using this method, the latest exhibition (by shooting date, not by creation) is shown first.
If you have more that one exhibition per day, you have to use fake values, including the time is not possible, since the value is only 32-bit wide.

Martin

[macke]

Thanks Martin, this worked like a charm for me and should be easy enough to maintain.

--max