Hi to all

I made an Upgrade from 6.10 to 6.19: the procedure was right but I discover somethigs wrong in the module behaviour.

I made the setting for Front Page (meta Key and description) leaving all other "special page" with blank field.

But strangely I found that "Trakers page" settings are filled with the same value of "Front page". If I remove these "auto copyed" value... form "Trakers page" even the "Front page" are deleted too.

This is dangerous for generating "duplicate description" in many area of my site.

Another little thing: in this new version I didn't found possiblity to set Robots "noindex, nofollow" for "Special pages" (like tracker, ecc.) but only MetaTag settings... I'm missing somethings?

Thanks Bye!

Files: 
CommentFileSizeAuthor
#2 nodewords_0961B014.patch2.89 KBkiamlaluno

Comments

Please ignore the last sentence about "Special Pages": i found the settings.
Sorry!

But I confirm the situation for the main problem.
Bye

Title:Setting for "Front Page" Meta data... become "copyed" inside Traker Page settings (and other)Meta tags content for specific pages are wrongly saved
Status:Active» Fixed
StatusFileSize
new2.89 KB

I changed the code, and committed in CVS. The attachment is the patch that applies to the development snapshot.

Thanks for reply....!!

Another little bug i 6.x-1.9: when I try to delete a "Special Page" setting after the operation the value remain in the list...

;)

May you open a different issue report? It is rather difficult to keep track of a report that is included in another one.

oK!

Thanks, Dret.
Having a separated issue allows also to mark it as fixed, once the code get fixed.

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Status:Closed (fixed)» Fixed

I have marked #691170: Unable to save meta data after upgrade as duplicate of this report.

We upgraded to latest -dev version that has the alleged fix you linked to.

Still, no luck with getting the data back.

I also got the following errors, which could be the underlying cause:

Can't DROP 'nodewords_type_id_name'; check that column/key exists query: update_sql /* admin : update_sql */ ALTER TABLE nodewords DROP KEY nodewords_type_id_name in includes/database.mysql-common.inc on line 417

Duplicate entry '5-65535-keywords' for key 2 query: update_sql /* admin : update_sql */ ALTER TABLE nodewords ADD UNIQUE KEY nodewords_type_id_name (type, id, name) in includes/database.mysql-common.inc on line 403.

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.