Support for Cononical meta tags Support for Cononical meta tags
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

Support for Cononical meta tags

Started by profili, June 12, 2010, 12:31:06 AM

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

profili

Using the Canonical Meta Tag is a great way to avoid the problems with the multiple urls that Coppermine gallery produce.
I hope you CPG guys will take in account this suggestion and will add this feature to Coppermine.

Joe Carver

Could be done with a plugin. I might try to add this to an existing one that I have made.

You will find that many "duplicate url's" in cpg 1.5.x are already tagged with:
<meta name="robots" content="noindex, nofollow" />
in the page head.

Moderators might consider this to be a feature request and move it.

Joe Carver

It will be added to the next version of my plugin "Add Meta Description". It will add
<link rel="canonical"....displayimage.php?album=xxx&pid=yyy " />
to search and meta album picture pages.
For preview and for comment see: http://photos-by.joe-carver.com/index.php

It will be on the pages with noindex nofollow and it could be argued that is is "overkill"
The plugin was due for an update and this fit right in.

BTW it is actually - "canonical"

Joachim Müller

So Google sets up yet another standard. What does the W3C say about this new meta tag?

Joe Carver

Quote from: Joachim Müller on June 12, 2010, 09:43:43 AM
So Google sets up yet another standard.
Only to make their work easier.......nothing seems to change.


Quote from: Joachim Müller on June 12, 2010, 09:43:43 AM
What does the W3C say about this new meta tag?

No complaints from the validation page. It looks like they have proposed more types of these (canonical) too. Maybe it's too early for me to be thinking clearly but I have not found the W3C standard/definition for this yet