Pages with the noindex in the Custom Page can not be indexed; returning Nodewords 6.x-1.11, you can remove the noindex in Custom pages, but you can not put it in Tracker, imported into the new version in the Custom Page.

Comments

damienmckenna’s picture

@giovanninews: I'm a little confused by what the exact problem is. Are you trying to add set the robots option to "noindex" for the Tracker pages via the Custom Page feature?

giovanninews’s picture

Damien, sorry for my english;
to Nodewords 6.x-1.11, to Custom Page, I added the robots option to "noindex" in the pages tag/* and category/* ; after the ugrade to Nodewords 6.x-1.13, wanting to eliminate the robots option to "noindex" to pages category/*, is no longer possible. This is possible by making the downgrade to Nodewords 6.x-1-11 ( operation carried out in test ). The downgrade to Nodewords 6.x-1-11 however, no longer allows you to set the robots option to "noindex" in the pages Tracker ( user/*/track, tracker, tracker/*) and the Error 403 page and the Error 404 page. So, on the production site, I can not downgrade to previous version of Nodewords.

giovanninews’s picture

Hi,
in another web site, Nodewords 6.x-1.13 has added the robots option to "noindex" in 80% of the pages. In all of these pages has also lost the meta name "geo.position". For this website, from the backup, I restored the old version 6.11.

giovanninews’s picture

Hi Damien,
There is an 'else that I do not understand. I refer to the website with Nodewords 6.x-1.13, comment #2. With Nodewords 6.x-1.11 was not possible to set the robots option to "noindex" to the system paths ( Nodewords probably did, but not transferred to html ); for add the robots option to "noindex" to the system paths ( example archive/* or taxonomy/term/* ) I used the template_preprocess_page. Now, with Nodewords 6.x-1.13, I have for system pages, twice the robots option to "noindex"; evidently with Nodewords 6.x-1.13 has fixed the bug earlier and no longer need template_preprocess_page.

damienmckenna’s picture

I don't *want* you to downgrade, I want to work out the problem so it can be fixed. :-)

Did you try setting the meta tags on the vocabulary pages, e.g. admin/content/taxonomy/edit/vocabulary/1? What is set there will be used as the default on all term pages within those vocabularies.

If you send me a copy of your nodewords and nodewords_custom tables I can help identify the problem and explain how to make it work the way you want.

giovanninews’s picture

Hi Damien,
is true, as you say it is also possible setting the meta tags on the vocabulary pages. I still have this problem solved creating a new page Custom for category / * with meta name index and follow. My situation at the moment is the following:
website 1 - Nodewords 6.x-1.13 works well; I lose something else in relation to meta name = "copyright" and meta name = "geo.position". I have not yet figured out which setting to Nodewords upload these two meta name. I have eliminated template_preprocess_page so there are no duplicate meta name. In my case, however, Nodewords was no longer necessary having understood the 'use of template_preprocess_page. I still use Noderwords for not having error 404 with the search engines for "keywords".
website 2 - downgrade Nodewords 6.x-1.11 because Nodewords 6.x-1.13 had set the noindex meta name in '80% of the pages; Nodewords he seemed to have created problems with meta name = "copyright" and meta name = "geo.position". Some problems with 'wysiwyg editor ( FCKeditor ) ( problems with "Switch to plain text editor" and "Switch to rich text editor" ). In this case I suspect that the failure may depend on the theme (Marinelli) or the TAC module.

During the week I will again 'upgrade to Nodewords 6.x-1.13 for the website 2. I'll post here any problems to discuss with you.
Hello Giovanni

damienmckenna’s picture

Status: Active » Postponed (maintainer needs more info)

If you could upload a database dump of your nodewords tables I'll be able to debug the problem, otherwise I'm not sure what is going on, it should work just fine.

couloir007’s picture

I have a similar problem. I've created custom pages to add no index to category pages, etc, but it doesn't add the robots meta tag. I upgraded to the dev 3.14, but another problem surfaced, canonical url is not using the alias, but the node/[nid], which I'll add to the issue queue in a moment. So I'm force to choose which is more important.

damienmckenna’s picture

Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (won't fix)

Unfortunately this module is no longer supported, so I'm closing this issue.