Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Comment | File | Size | Author |
---|---|---|---|
#7 | PurlDisabledSiteUrlToken.zip | 1.31 KB | gmclelland |
#6 | PurlDisabledIdentifier.zip | 1.41 KB | gmclelland |
#5 | PurlDisabledIdentifier.zip | 1.41 KB | gmclelland |
#4 | PurlDisabledSiteUrlToken.zip | 1.29 KB | gmclelland |
Comments
Comment #1
gmclelland CreditAttribution: gmclelland commentedFrom further testing it looks like the spaces_og.module included with the spaces module causes CB not to work. I'm still trying to find a fix.
Comment #2
gmclelland CreditAttribution: gmclelland commentedAfter more investigation, it looks like it was caused by the spaces_og.module 6.x-3.2
When I comment out this function everything seems to work. Now I just need to figure how to get the "Home" breadcrumb using Custom Breadcrumbs module to be PURL disabled so that it goes to the site homepage instead of the group homepage.
Anybody have any thoughts?
Hope that helps someone.
Comment #3
gmclelland CreditAttribution: gmclelland commentedI guess I should create a token or Custom Identifier for the "site frontpage" that sets purl to disabled for that link?
Comment #4
gmclelland CreditAttribution: gmclelland commentedI created a PurlDisabledSiteUrl Token (see attached), but for some reason if it is used in the "path" field it gets wrongly encoded and it STILL gets prefixed with the purl modifier, yet it looks correct if used in a "title" field. If you look at the token you will notice when I build the link I set the l() function to disable purl. Does Custom Breadcrumbs run all breadcrumbs through an additional l() or url() that could be causing this?
Can you please tell me if the better approach would be to create an additional Custom Breadcrumbs Identifier, something like
<purl-disabled>
so that any breadcrumb link could be disabled by purl?Would love to hear some feedback.
Comment #5
gmclelland CreditAttribution: gmclelland commentedHere is a start to building the Purl Disabled Identifier. (see attached) It doesn't work yet. I was hoping someone could give me a few pointers of what I'm doing wrong.
Comment #6
gmclelland CreditAttribution: gmclelland commentedOk, I believe this is working now. Hope it helps someone.
Comment #7
gmclelland CreditAttribution: gmclelland commentedHere is the PurlDisabledSiteURL Token.
You have to use it together with the Purl-Disabled identifier like this:
Titles:
Home
Paths:
<purl-disabled>|[purl-disabled-site-url]
Note: The Purl-Disabled Identifer doesn't work for tokens that have a pregenerated url like [site-url] or [node-url], because PURL adds the modifer to the token.
It does seem to work with something like this:
Titles:
This node id is [nid]
Paths:
<purl-disabled>|node/[nid]
Hopefully someone else more knowledgeable than me will come along and improve this.
-Glenn
Comment #8
lamp5