When creating the settings for a custom page, users should be able to decide, i.e., if the paths they add should be compared with the path alias, or the request URI (which includes also any request parameters passed through the URL).

Comments

ilo’s picture

ilo commented

KiamLaLuno, should they? I mean, can't the module handle it automatically?

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Version: 6.x-1.x-dev »

The module can handle it automatically.
The additional settings allow the user to make the code faster; if the users know that the path they are using doesn't match with a path alias, it is useless to get the path alias of the currently viewed page.
I think there could be cases where the user is interested in applying meta tags to pages whose Drupal path (the one passes in _GET['q']) matches a defined value, but not applying meta tags to pages whose path alias matches the same value.

This is a task for 6.x-3, anyway.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Title: Add more options for the settings for other pages (a.ka. custom pages) » Add more options for the settings for custom pages
Project: Nodewords: D6 Meta Tags » Extra meta tags modules

I am slightly changing the title.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Issue summary: View changes
Status: Active » Closed (outdated)

I am closing this issue, which is for a not supported Drupal version.