This is the same for both 1.3 and latest 2.5 beta1 :

During Browse images (1 img/page) images in previous a next links are not sorted in weight order but previous is newer img and next is the older one. That's confusing.

Previous is misspelled - previou

Thank you for your previous answers too.

Comments

eastcn’s picture

eastcn commented

The new or the old order of priority, just different habits. This is not a mistake.
In both documents (photos_imageview.tpl.php, photos_imageblock.tpl.php) can be adjusted in order.

vidda’s picture

vidda commented
Priority: Critical » Normal

Maybe some misunderstanding. I will try to explain.

Order in album page, where you see all images, is user defined by the weight parameter of each image. That is ok and logical. When I click on the first image in the row, I go to detail page with that image, then I can see just 1 link - PREVIOUS. That is confusing - why previous if this is the first image. I should see NEXT I think. The browsing order shoud be the same on both pages (Album and Browse images), that is the problem. Now each page shows different order and that would be good to unify.

I may change it for me, of course, but only to next update. Better way is to change this disunify in your source. And to say the true, I don't know PHP, I am just a beginner in www development. Just tryin to develop my first web.

Other things are working well now I think.

eastcn’s picture

eastcn commented

Unity is the order of the picture. The new priorities, such as:
101 (prev) <- 100 -> 99 (next)
100 (prev) <- 99 -> 98 (next) ....
This not a mistake, just a different browsing habits.

vidda’s picture

vidda commented
Version: 6.x-1.3 » 6.x-2.5-beta1

Yes, and the order is done by the weight. Browsing habits are adjusted by this weight. This is common in drupal, I thing, in stories, menus, pictures, everywhere. Everybody may have different habit, so weight is the way how to do it. And object browsing should be done by that order.

And it works here http://vidda.ic.cz/?q=alba-buben2008 . First 51, second (it means next) 52, then 53 and so on. This is the order defined by me by the weight. Do not care of the numbers, these are only IDs, see the pictures just as ordinary user.

Then you click on the FIRST image in the row http://vidda.ic.cz/?q=photos/image/51. If this is the FIRST image, then I would expect the SECOND one on the NEXT link. There is no such link, just PREVIOUS.

This PREVIOUS http://vidda.ic.cz/?q=photos/image/52 is the SECOND image.

And that is confusing - SECOND is PREVIOUS of the FIRST. This is independent of the browsing habits, it is logical nonsens I think. You can order ascending or descending, but in each ordering type SECOND has to be AFTER the FIRST, not BEFORE the FIRST.
FIRST is not LAST. FIRST has no PREVIOUS, this is beginning, LAST has no NEXT, this is the end.

vidda’s picture

vidda commented

A total of 132 albums under the image

should be

A total of 132 images under the album

or maybe better

A total of 132 images under this album

hmorgan’s picture

hmorgan commented

I found the misspelling of "previou" is in two places in the code:

photos_imageblock.tpl.php line 30
photos_imageview.tpl.php line 31

I'm looking at the code from version 6.x-2.5-beta3

nathaniel’s picture

nathaniel commented
Status: Active » Closed (duplicate)

#695304: Image Sorting Does Not Match Image Pager Block or Image View