Play nice with Nodewords (Metatags) module

OK, so this is the closest thing to an existing issue I could find :) Yes, I foresee problems. I actually needed to solve the problem of the missing facebook-specific tags (app id and administrator ids) and I was already experimenting with nodewords. I too, however, did not like the way it handled the image meta tag, which this module does very nicely.

I installed both, but Facebook told me (by entering my page URL into https://developers.facebook.com/tools/debug) it failed validation due to double tags; both nodewords and opengraph_meta were including the tags (it *was* a long shot).

Long story short, as nodewords is somewhat of a standard for handling meta tags in D6, I thought it was a good idea to write a patch that makes this module play nice with nodewords. It basically turns off this module's own tag rendering (only when nodewords is present!) and instead uses nodewords' hooks to alter the tags it offers. The merging mechanism is fairly simple, it favours opengraph_meta's versions of the tags (when !empty) and overwrites nodewords' og tags. It will nog override nodewords_og's tags with empty values, though.

Thanks, this patch worked well for me.

The new 7.x-2.x version builds on metatag which by now seems the standard for managing metatags in drupal.

Does that mean the 6.x version is not supported anymore? There is no Metatag module for Drupal 6, the Metatag for Drupal 6 is Nodewords.

Yes. opengraph_meta wasn't supported for the last 3 years. It's (only?) maintainer has left the Drupal sphere since then. I took over the maintainership of the D7 version. I can't maintain the D6 version since I don't use Drupal 6. That leaves you with the following choice:

1. Step up to become maintainer of opengraph_meta-6.x-1.x.
2. Get someone else to do it. (Usually involves payment of some kind.)
3. Accept that it has the same level of support as in the last 3 years: none.

I'm only the messenger, because I closed all the D6 issues (thereby making the current state of this module explicit).

Fair enough. Maybe you want to put the 6 version to unsupported, then. The fact that the D6 version is effectively unsuported is not very clear from the project page.

Good idea! I've marked it as unsupported.

No it's not a good idea. Now you are creating a situation where people are forced to upgrade or must deactivate the module, should they still have a site or two running on drupal 6 - which I do.

If there are no safety concerns - why not keep the version 6 module up. Pleeeease!

I'm not sure I understand what the problem is. If you keep your site in version control in its entirety, you have the module downloaded and there is no harm done. If you have a build process that re-downloads the module on every build (drush make?) you can still download what you need from the Git repository. This does clearly communicate that the D6 version is not supported to anyone that might consider starting to use this now (I know I have customers that keep asking for features on their D6 sites...)

thanks for the patch! long live d6