hi,
can someone quickly explain the nature of the parentid in the album table ?
I either miss a link or the last upgrade has fiddled with it.
I would have thought that the parent id is always the next album level up.
Please see my dump below.
Why does 'Boquete' have a parent id of a dynamic album ?
That seems wrong to me. I think it should link to 155.
If that is correct than the upgrade from RC to 1.2.8 must have done that I haven't touched this table manually. Should I correct this ?
Not sure this is really a bug because in the admin section the hierarchy looks correct.
i.e. 'Boquete' is shown under '2008' as I want it.
I discovered this working on a custom SQL...
What is going on here ? Shouldnt 'Boquete' have parentid = 155 ???
id --- parentid --- folder --- name
17 --- NULL --- rooms --- rooms
155 --- 17 --- rooms/2008 --- 2008
269 --- 276 --- rooms/2008/Boquete --- Boquete
276 --- 17 --- rooms/Cheap_Hotels.alb --- Cheap_Hotels
Comments
This is corrected in the nightly builds. But for now, if you re-run setup it should re-fix the parent id.
How come the hierarchy is maintained in the admin & viewer then ?
Is it derived from the folder tree not the parent id ?
If yes that is a good approach !
Too often I have seen poorly replicated a filesystem hierarchies
instead of just using the file system
So upgrading to the nightly build will fix this ?
I rather avoid this, any alternative ?
well other than that the
function printSortableAlbumLink($text, $title, $class=NULL, $id=NULL)
seemingly did get abandoned, but that is fine with me
Cheers
P.S. : also the distorted landscape thumbs from portrait images are gone and the law of the thirds looks loads better !