canonical issue [#1858040]

Not sure if this is me or if there is a bug...

have a few duplicate aliases kicking around and want the canonical tag to point to the alias you see when you edit the node...

none of the options seem to do this, I think I've tried them all, but all seem to use the aliases of the duplicate
entered when looking at the source and not the one from the real node itself... i.e. all the duplicates declare themselves to be the original and not the real node path alias (node/xx works but not the node alias)....

Have I missed an option or is it a bug?

I would have thought [node:url:path] would do the job but it isn't for me...

Comments

Comment #1

DamienMcKenna

NH, USA

CreditAttribution: DamienMcKenna commented 4 December 2012 at 14:37

Priority:	Normal	» Minor
Status:	Active	» Postponed (maintainer needs more info)

Are you using Pathauto? Are you using Redirect? Are you using the latest version of Token? Have you checked the database records in the url_alias (and redirect) table to see what records are stored? The reason I ask these is because Metatag doesn't create the URL for the Canonical URL field, it comes from the Token module.

Comment #2

MJD CreditAttribution: MJD commented 4 December 2012 at 16:20

Thanks for the quick response.... I understand your comment about token generating this..
I've been looking at pathauto & token issue queues

I think that the alias displayed in the node edit.., is the required option for most sites IMO...

I think the primary alias should always be the one on the node and if you want something different then have the option to change...

Anyway, if you set up a new alias via path auto "add alias" to force the problem, then pathauto? seems to make that the primary alias everywhere... if you then look up the available tokens under the devel tab then there is no reference to the alias on the node....

Think I need to get my test system upto the latest core release and if that doesn't work I'll pursue over on the token / pathauto projects (not sure which yet)...

The problem obviously isn't here so you can close this issue from my viewpoint. If you agree with my way of thinking on the canonical tag and can confirm the fault... We may get a fix quicker if you as a module maintainer pursue... Anyway it's up to you...

Comment #3

DamienMcKenna

NH, USA

CreditAttribution: DamienMcKenna commented 4 December 2012 at 16:22

Project:	Metatag	» Token
Version:	7.x-1.0-beta4	» 7.x-1.4

Moving it over to the Token issue queue, as that's where the token comes from. It definitely deserves a little poking into, to find out where the path comes from that you see - if it happens to be another module at the root of the problem then we can move the issue over to that module's queue.