Opened 9 years ago

Closed 9 years ago

#5098 closed bug (fixed)

HTML meta tags have vanished

Reported by: koki Owned by: haiku-web
Priority: high Milestone: Unscheduled
Component: Website/CMS Version:
Keywords: meta tags Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

All HTML meta tags have vanished from the header of all pages of the website.

Change History (5)

comment:1 Changed 9 years ago by umccullough

Milestone: R1Unscheduled
Priority: normalhigh
Version: R1/alpha1

As mentioned in #5100, a recent update of Nodewords seems to have broken the meta tags functionality, and it is being investigated.

comment:2 Changed 9 years ago by koki

I just noticed that the tags for all pages have been overwritten with the same tag data from the front page. This is not how HTML tagging worked before, nor the way it is intended to work. The original configuration was such that:

1) The front page had its own set of data for the keywords, description, and copyright tags, customizable from the admin area.

2) Each individual node would automatically inherit the node teaser as the description tag and prefix the taxonomy entries to the default keywords tag. In each node, every tag could be overridden manually (customized) as needed from the node edit window, to maximize the SEO effect for very specific pages (for example, among others, the Get Haiku page had a more explicit custom description the would appear below the link in a Google search).

Now that all pages seem to have the same tag data, you will not get the desired SEO effect.

Given that the previous version of the updated module was working nicely and without any glitches, can we just revert to the previous version and recover the original tag data? I don't see the point of updating a module to a version that breaks functionality so badly.

comment:3 in reply to:  2 Changed 9 years ago by nielx

Replying to koki:

Given that the previous version of the updated module was working nicely and without any glitches, can we just revert to the previous version and recover the original tag data? I don't see the point of updating a module to a version that breaks functionality so badly.

As the module updates weren't security related, I guess that's a possible thing to do right now. After a new version is released we can first try it on a sandbox and to check whether the upgrade process works properly now.

This would require extracting the database from one of our backups prior to December 4 2009. Matt, are you able to do this or should I?

An intermediate step could be to check out the data (and the settings) and try to recreate that for the 1.7 version of the module. If that does not work (satisfactory) we can always revert to 1.5.

But I'll leave that for the one doing the work (perhaps this is going to be me ;-)).

comment:4 Changed 9 years ago by mmadia

Instead of 1.5, 1.2 was reinstalled. The 'nodewords' and 'nodewords_custom' tables were extracted from the 12-03 database and applied. From limited peeking, the meta tags appear to be restored. However, the permissions are currently limited to admin. In addition the settings on admin/content/nodewords may need further tweaking as well.

comment:5 Changed 9 years ago by mmadia

Resolution: fixed
Status: newclosed

nodeword's settings from the legacy.web.* site was used as a guide. Feel free to tweak any settings as needed.

Note: See TracTickets for help on using tickets.