Token for the front page URL should return the base URL [#767764]

Comment	File	Size	Author
#17	nodewords-n767764-17.patch	1.99 KB	damienmckenna

Comment #1

Anonymous (not verified) commented 11 April 2010 at 10:37

Title:

Canonical tag for home page should be base url

» Token for the front page URL should return the base URL

The meta tag for the canonical URL accepts <front> as value.

I will change the description for the canonical URL to report that <front> is an accepted value, remove the tokens for the front page URL, and change the code for generating the tokens [metatags-normal-url], and [metatags-url-alias] to consider the case of the front page URL.

Log in or register to post comments

Comment #2

locomo commented 11 April 2010 at 18:57

great thanks

worked for me!

Log in or register to post comments

Comment #3

Anonymous (not verified) commented 11 April 2010 at 19:53

Status:

Active

» Fixed

I changed the code, and committed it in Drupal.org repository.
Thanks for your report.

Log in or register to post comments

Comment #4

locomo commented 22 April 2010 at 02:27

Priority:	Normal	» Critical
Status:	Fixed	» Active

I'm confused - in the most recent dev version the Front Page settings under "Specific Meta Tags" are no longer available .. so there is no way to set for the home page..

I think the home page is a "special page" and I would lobby for returning a dedicated area to set meta tags for this page

there is now no way to set tags for the home page and the custom page tags are not working

Log in or register to post comments

Comment #5

Anonymous (not verified) commented 22 April 2010 at 06:36

The token code has been already changed to return the correct URL for the front page; there is no need to set the canonical URL for the front page specifically.

Log in or register to post comments

Comment #6

locomo commented 22 April 2010 at 15:29

its not working though.. check out:
http://omaha.net/

also, how do we now set meta description and meta keywords fro the home page??

Log in or register to post comments

Comment #7

damienmckenna

TN, USA

commented 18 October 2010 at 01:41

Issue tags:

+v6.x-1.12 blocker

Tagging this. We want the next release to be rock solid, so if you have some time please help test the v6.x-1.x-dev release to see if all of the above issues are resolved.

Log in or register to post comments

Comment #8

damienmckenna

TN, USA

commented 30 October 2010 at 21:56

I think the question is: what should the default value for the Canonical URL meta tag actually be to provide the correct result?

Results of using various tokens provided by the token.module as the canonical URL with the site_frontpage value set to "homepage":

[current-page-path]: http://example.com/homepage
[current-page-path-raw]: http://example.com/homepage
[current-page-url]: http://example.com/homepage

Log in or register to post comments

Comment #9

damienmckenna

TN, USA

commented 30 October 2010 at 21:57

Could this be a problem in token.module itself?

Log in or register to post comments

Comment #10

dave reid

he/him

English

Nebraska USA

commented 31 October 2010 at 22:46

@locomo: To answer your question about setting frontpage meta tags, you have to make sure the "Meta tags for custom pages" module is enabled, then go to admin/content/nodewords/custom/add and use the path '' and set your meta tags as desired.

Log in or register to post comments

Comment #11

dave reid

he/him

English

Nebraska USA

commented 31 October 2010 at 22:49

@DamienMcKenna: If you're wanting to use a canonical URL for frontpage, you should probably be using the [site-url] token, not the [current-page] tokens.

Log in or register to post comments

Comment #12

dave reid

he/him

English

Nebraska USA

commented 31 October 2010 at 22:50

Category:	bug	» support
Status:	Active	» Fixed

The answer to the original problem is to use the [site-url] token as your canonical token's value. Hence, there's no bug here.

Log in or register to post comments

Comment #13

damienmckenna

TN, USA

commented 1 November 2010 at 00:42

Status:

Fixed

» Needs work

Maybe this just needs #901764: Re-add easy support for front page meta tags to resolve the stupidity of getting this to work?

I also also under the mistaken impression that GlobalRedirect kicked in to change the path provided by drupal_get_path_alias(), but it only works on the actual page load. Should that be changed?

Log in or register to post comments

Comment #14

damienmckenna

TN, USA

commented 1 November 2010 at 01:06

For v6.x-1.12 should we add a note to the README.txt to explain it? it just sucks how this currently works right now :-\

Log in or register to post comments

Comment #15

dave reid

he/him

English

Nebraska USA

commented 1 November 2010 at 03:36

No global redirect only works on the actual page request, not on all links generated. I think we need to re-add the easy front-page meta tag sub-tab for 6.x-1.12. It should be fairly easy to do.

Log in or register to post comments

Comment #16

dave reid

he/him

English

Nebraska USA

commented 1 November 2010 at 05:52

Priority:	Critical	» Normal
Status:	Needs work	» Fixed

Yeah let's fix #901764: Re-add easy support for front page meta tags.

Log in or register to post comments

Comment #17

damienmckenna

TN, USA

commented 1 November 2010 at 12:58

Status:

Fixed

» Needs work

Status	File	Size
new	nodewords-n767764-17.patch	1.99 KB

Lets change the canonical field's description to indicate what the recommended defaults are:

Canonical URLs are used from the search engines, and allow them to not report duplicate titles for HTML pages that are accessible from different URLs. Canonical URLs that point to a different domain are normally not accepted. This meta tag supports tokens. The recommended value for the front page is "[site-url]", the recommended default for other pages is "[current-page-path-raw]".