I know that some work has been done on this but there is still a problems.

When you go into the photo gallery link the bread crumb is corrent

Home > photo galleries

Then when you select a term it is still correct

Home > photo galleries > term

but when you click on an image the breadcrumb should be

Home > photo galleries > term > image

but instead it is

Home > Image

Because of this there is no way of getting back to the photo galleries from the bread crumb.

Comments

moshe weitzman’s picture

That is a tough one to fix. In order to know which gallery you are in, we have to track where you came from. That probably means stashing your navigation history in the Session object.

The only other alternative I can think of is to change the album navigation urls such that you don't go to node/view/x when viewing an image but rather to node/view/x?breadcrumb=3,4. That querystring instructs image module to set the breadcrumb path as term3 => term4

dries’s picture

Most (if not all) images are part of a single gallery in which case we can print the correct breadcrumb trail. If the image is part of multiple galleries, we can use the current behavior. -1 for keeping a navigation trail in the user session or for pollluting the URLs.

gábor hojtsy’s picture

I have fixed a similar bug in forum.module lately (this instructed the addition of taxonomy_get_parents_all(), which can be perfectly used to traverse the taxonomy path back to the vocabulary root). That approach is fine for breadcrumbs, if you only have one possible route back to the vocabulary root.

cornernote’s picture

Hello Goba,

Can you please give an example of how this could be done in the image.module?

Best regards,
Brett

blr’s picture

Just checking to see if any work has been done on this? This is still an issue with 4.5 and it would be great to see this addressed.

blr’s picture

Just checking to see if any work has been done on this? This is still an issue with 4.5 and it would be great to see this addressed.

drewish’s picture

Version: » 4.6.x-1.x-dev
Component: User interface » image.module
Status: Active » Closed (fixed)

i'm trying to clean up the image module's issue queue. this issue looks like it's been resolved by more recent versions of the module. feel free to re-open this if you disagree.