I use beta 1.12, dev and 1.11 and for me the best version is 1.11 with patch to work custom pages (1.11 do not save data on custom pages). I see that there is still a little problem.

It would be great that meta tags will work on custom pages such as *sort=* (wildcard path). Then it will be easy to noindex adv. forum links etc (duplicate content).

Comments

Dave Reid’s picture

Title: Problem with custom pages 1.11 » Support query strings in custom paths
Version: 6.x-1.11 » 6.x-1.x-dev
Component: Miscellaneous » Code
Category: bug » feature
Priority: Major » Normal

Currently the pages only work for the path and not for query strings. Moving to a feature request for the 6.x-1.x branch.

DamienMcKenna’s picture

Version: 6.x-1.x-dev » 6.x-2.x-dev

Bumping to v2.

DamienMcKenna’s picture

Status: Active » Postponed

Marking all v2 issues as postponed while v1 is finished off.

kamranzafar’s picture

Is there any patch available.

vasrush’s picture

That would be very helpful, also interesting.

vasrush’s picture

For anyone after this feature request.
I managed to make it work, but not with Nodewords.

There is a patch for the context module http://drupal.org/node/904416 that enables queries as a condition.
There are patches for both drupal 6 and 7. Then you can use context metatags in order to alter your metatags.

This is a very important feature from SEO point of view and I would really like to see it in Nodewords.

I hope that helps.

rafal.enden’s picture

Version: 6.x-2.x-dev » 6.x-1.4
FileSize
1.82 KB

Patch for version 1.4 matching $_SERVER['QUERY_STRING'] instead of $_GET['q']

rafal.enden’s picture

Some corrections.

DamienMcKenna’s picture

Version: 6.x-1.4 » 6.x-1.x-dev
Status: Postponed » Needs review

Status: Needs review » Needs work

The last submitted patch, nodewords_querystring-1095790-8.patch, failed testing.