Not being familiar with that plugin, I’m going off what they have for their demos. It looks like rather than using the normal WordPress methods, they implement albums/galleries on top of a single page. Breadcrumb NavXT has no way to tell what’s going on here as it technically is the same page. I suppose an extension plugin could be written for compatibility (assuming their API is decent). In the end, if they used CPTs the normal way, this issue would not exist.
Thanks for your reply John. I am not a programmer myself, so technically I don’t really know what they are doing. But I notice something: when you click an album, the URL in the browser changes. For example from http://localhost/artcenter/galleries/ to http://localhost/artcenter/galleries/gallery/test1.
Doesn’t that mean that it actually goes to another page, unlike what you said? Would there be an easy way to tell Breadcrum NavXT to use the path that the browser indicates?
I’m sorry if my observation is something you already took into account. Just wanted to clarify.
Unfortunately, even if the URL changes, that doesn’t mean a new page (instance of the page post type) is being loaded. Foo Gallery is likely using a shortcode to display the gallery on a page, and then updates the contents of what it replaces the shortcode with depending on the URL used to access that page (using custom permalink rules). In my opinion, this is a legacy and somewhat hacky way of implementing galleries that originated from back before custom post types existed.
Support for Foo Gallery would require looking into what they are doing and then trying to support it. It is likely outside the scope of the core plugin, and would require an extension plugin for full support.
I see, thank you for the clarification! I wonder why they use this ‘shortcut’ instead of using the proper WordPress way. Oh well …
