Placeholder Not Working

Can you tell me more about the view?

Have you set up a node-type breadcrumb for the nodes displayed in the view?

Should I assume [field_archive_commodity-link] and [field_archive_commodity-title] are custom content fields for the nodes that are displayed in the view?

It looks like you really want a node-type breadcrumb, not a views-type breadcrumb. With a node object, these tokens could actually be replaced.

If the view displays many nodes each with a possibly different value for these fields, then what value should be chosen for the breadcrumb (first node in the results or ????)

Does you view use any arguments? What are they?

With some additional information I might be able to help you out.

Thanks for your response, no I hadn't set-up a node-type breadcrumb as the content isn't actually displayed using the node view as I need full control over the URL which the node view will not allow me.

Yes the fields are custom content fields and the second part of the URL is an argument which is another content type, to give you a better overview, this content type is broken down into 10 different commodities, you access this content by going to members-area/[commodity], this is just the home page of this commodity there will also be another 6 different pages below this which you access via members-area/[commodity]/whatever.

Hope this makes better sense to you.

O.k. So all of the results of the view will have the same values of [field_archive_commodity-link] and [field_archive_commodity-title], so by loading the node for the first result of the view, the breadcrumb should work. I've made some changes to the custom_breadcrumbs_views and custom_breadcrumbs modules, and I think this should work now. Can you test out the latest 6.x-2.x-dev ?

As is best practice, be sure to disable the custom_breadcrumbs modules before upgrading (you don't have to uninstall).

As for your other comment:

Additionally I cannot get anything to be displayed for Nodes except Home

I am a little confused by this because you also said you didn't set up node-type breadcrumbs. For nodes you'll need to either set up a node-type breadcrumb or a path based breadcrumb (which also works for nodes).

Thanks for testing.

Great thanks that's working now and picking up the correct information, however there's at least one additional problem, but I think they might be related:

When adding more than 1 view based breadcrumbs they all adopt the settings from the last one alphabetically e.g. I have the following created:

members-area/%
members-area/%/committee-meetings
members-area/%/information-archive
members-area/%/key-links

All breadcrumbs across the site adopt the one for Key Links, if I add one for say News, then the entire site also takes these breadcrumbs including nodes.

The second problem which also affects this is when I created the first view breadcrumb above the correct argument within the view was being pulled into the breadcrumbs, but after creating the additional breadcrumbs it always shows the same argument regardless.

Something else which isn't a bug but would be nice to have is in my view I replaced the spaces with dashes (-) and turned the title lowercase to make the URLs look nicer, your implementation still works, but would be nice to be able to mirror that

When adding more than 1 view based breadcrumbs they all adopt the settings from the last one alphabetically

Sorry, but I have not been able to replicate this on my test sites. I've duplicated views with arguments and paths as shown above.

The second problem which also affects this is when I created the first view breadcrumb above the correct argument within the view was being pulled into the breadcrumbs, but after creating the additional breadcrumbs it always shows the same argument regardless.

I am not sure I understand this. What are you using to pull the arguments into the breadcrumbs? What are you using for the titles and paths for the custom breadcrumb for these views?

I am closing this because its gone a long time without followup and the 6.x-2.x-dev codebase has changed considerably since June. If this problem still persists in the current code, please reopen this issue.