Missing all meta since upgrade

Exact same problem here. Please advise.

Did you enable all the required modules?

ah, geez, i'm sorry. that was it. apologize for the bother.

There is no need to apologize. There have not been any warning messages, and you could not know there were new modules to enable.
The code of the newest versions has been changed, and there is a warning in the case nodewords.module doesn't find any modules that implement meta tags.

alright. sorry. i'm not getting it. feeling quite clueless. this setup is much more confusing that it used to be - and i need to re-enable it on about 30 sites. ugh.

so i enabled ALL the nodewords modules (i think i only need basic, but just in case...). i enabled all the nodewords-related permissions for admin. i am an admin user (the only one).

i can now see the meta on the nodewords config page for node edit form and head printing. have enabled 3 fields: description, keywords, and robots. i can see these (more or less) in the node edit form and the values are filled in for description and keywords as they were before upgrade; robots not so much.

there are two problems:

1. none of the items is printing in head, even after these steps.

2. robots options on edit form contains only 'no' versions. nofollow, noindex... but not regular 'follow' 'index', etc. i can check the 'default' box but it says there is no default set up. on global settings page, it says to refer to 'settings' page for default robots settings, but there are none. just checkboxes for meta options edit mode and head where you can select 'robots'; then some advanced options. but no choices for robots.there are options for robots, but as in node edit they are all in the negative. there are no affirmative choices, e.g., follow, index.

i have cleared and re-cleared cache. tried on different pages.

i guess i'm still missing something. any suggestions?

thank you.

Sound like a duplicate of #587142: update_6113: No rows written to nodewords_tmp and therefore all data lost

thanks for that suggestion. not sure it applies.

i do not know what nodewords_tmp is, but looking at the DB in phpMyAdmin shows that the table titled nodewords exists and appears to have all data in - the original data from before update. i didn't go line by line, but it appears complete. or, more specifically, it has 'keywords' and 'description' tags for most/all nodes.

there is not a 'robots' tag for each node - i assume that is because they are essentially all set to default? actually looking closer, there are a handful of pages with robots field, too - either containing nothing or containing values that are greek to me. for example:

a:2:{s:5:"value";a:6:{s:7:"noindex";i:0;s:8:"nofollow";i:0;s:9:"noarchive";i:0;s:5:"noopd";i:0;s:9:"nosnippet";i:0;s:6:"noydir";i:0;}s:11:"use_default";i:1;}

actually, these look like the options i'm seeing on the node edit form. perhaps these are the pages i 'touched' while trying to debug this problem.

my nodewords module definitely was active during the update.

update: i did all above steps on another one of my sites. same result. showing up on the edit form, but not printing to head. and robots not working properly.

Do not install 1.2 on more sites, please. Stay at 1.0 for now... This are all known bugs of 1.2 and you should better wait for 1.3 final or higher. Otherwise you loose your robots.txt data and other data plus many older config options. Also do not try 1.3 alpha! You will loose all your data if you upgrade from 1.0

Best suggestion is to go back to your backup with 1.0...

As per meta tag ROBOTS options, when you don't select NOFOLLOW, it is implicit that it is FOLLOW.

As already reported by hass, stay on 6.x-1.0 if you don't want to loose your meta tags; version 6.x-1.3-alpha1 doesn't fix that problem, and it is equivalent to 6.x-1.2 for that issue (it does fix other problems, but not that).

ugh. ok.

so to clarify, i have already (partially) installed 6.x-1.2 on all my sites - it's 'partial' because, as discussed above, i enabled only the main 'nodewords' module, but not 'basic meta tags' and the other 2 modules. i have since enabled those additional modules on 2 sites, but not the others.

given this, you are both recommending that i rollback all sites to the 1.0 version.

can i do this while retaining the existing DBs? or do i need to go back to prior DBs (which were backed up just prior to the update)? either way, this is some work, but if i have to go back to prior DBs, then that creates several days worth of re-work. obviously, i'd like to avoid that, if possble.

if you strongly recommend going back, is there a workaround whereby i import just the nodewords table to the current DBs? i'm not DB whiz, but i believe you can do that (not sure how hard it is). that would retain all the other changes since the update while possibly also keeping the original nodewords info.

thanks to you both for your help.

You have already lost data by the upgrade (at least robots tags and many settings). It's up to you... you are able to restore only the nodewords table(s) and delete and restore all "nodewords_*" variables in the variable table... this should be enough. Nevertheless I haven't tested it myself yet. I have disabled the module for now, but I will do the restore within the next days.

Thank you for that info, unfortunately I only barely understand it and wouldn't be able to do it myself - the delete and restore parts. I can, however, rollback to prior DB and 1.0 version on my own, so it seems that is the only actionable choice I have.

Only one of the sites has had any appreciable work done on it since the upgrade, so I guess I'll need to recreate that. Others were all simply maintenance things, but still close to a day of work.

So final question(s), if I may: can you clarify what happened? am i correct in understanding that there is a bug with the 1.2 version and that the upgrade itself (as opposed to something that I did) caused this problem? and further that the last actual properly working version is 1.0 - the version i just upgraded from?

Thank you again for your help.

am i correct in understanding that there is a bug with the 1.2 version and that the upgrade itself (as opposed to something that I did) caused this problem?

Yes.

and further that the last actual properly working version is 1.0 - the version i just upgraded from?

Yes.

Future versions (may hopefully) take more care about the upgrade path and do not get released that way untested. ~40.000 installations prove that an upgrade path must be 1.000% save. This is not the case with 1.1 and 1.2 and 1.3-alpha1. Please understand all versions above 1.0 should be seen as 2.x versions what should tell you "many new feature" or "complete redesign" - what also should give all people an idea that they should better test a bit more in dev environments and not deploy in production without carefully testing.

point taken about testing on my part before deploying.

i think i understood that official full module releases (i.e., non-.dev, non-.alpha, non-.rc, etc.) were already well tested. some .dev versions i've put in place have a 1,000+ users, but i guess this is not a safe assumption.

i also thought going into the nodewords upgrade specifically that i was doing a required security upgrade. in fact, my 'update status' page continues to show red and indicates upgrade to be required for security purposes. so idea that built into that security upgrade was, in fact, a huge module overhaul - well, that was not at all obvious. i have no idea how i could even ascertain that even if i'd tried.

overall, i remain a bit perplexed by the situation: if there are known bugs in the new versions, why don't you pull them back and stop pitching 1.2 as a required security update? i know you've got a warning posted, but it is extremely vague and appears to apply to the .dev version. i actually read it before installing, but proceed cause i had no idea what it meant. many less technical folks such as myself are not going to understand that that is a warning not to install an otherwise normally required security update. many aren't even going to see it cause they just download via update status page.

anyway, i'll start rebuilding my sites - and thanks for helping sort this quickly.

Sooo #587142: update_6113: No rows written to nodewords_tmp and therefore all data lost seems to be fixed. This issue should therefore no longer exists. Reopen of still an issue with alpha2+.

sorry, but i'm back...

so i tried to do as you suggest and go back to previous DB and v 1.0, but it is not quite working. steps taken were:

- removed entire nodewords 1.2 folder.

- dumped all existing DB tables and then i imported the old DB saved last Wed prior to this problem. loads fine. looks fine.

- downloaded and reinstalled 1.0 version of nodewords. loaded modules page. nodewords not being seen - meaning it isn't showing up on the module list. i ran update.php, cleared cache. reinstalled module again. still not being seen.

- nonetheless, in node edit form, nodewords options are present. there is a functioning 'meta tags' config page which i've made changes to and seen reflected in edit form. and the specified meta are printing in HTML head. in other words, the module appears to be working despite the fact that it isn't showing up on the modules page.

any suggestions?

duh - never mind. the module had another name way back as of last week.

I upgraded nodewords on 3 sites before I realized that all meta tags were missing.

I activated all need modules and clicked on all meta tags I needed but none would show up.

I went back to the old version of metatag and everything works fine.

I don't know but the old version works great, I will wait to upgrade again.

You may missed to run update.php

No I ran it.

I didn’t spend much time with it I will play with it later on a development site. But seems like the old version was much easier to install and use.

I enabled all the modules

Basic meta tags
Extra meta tags
Nodewords
Site verification

but it didnt help...

the only thing i want is the field Discription to be shown in node edit as before....

what am i missing?

You have installed a VERY buggy version. Check out if the nodewords table is empty. This has been fixed in 1.3alpha2 -> Restore your site from backup.

i updated to 1.2
the nodewords table is ok...

i dont understand why everything is fine for some people here after enabling the modules and not for me...

There is *nothing* fine for other people. They may haven't seen that their nodewords table is wiped or ~80-90% of their settings are lost. You may have disabled all modules before the upgrade like core suggests. This is another known - and as I know - still unfixed bug.

Restore your backup, stay at 1.0 and wait for 1.3 final, please.

sorry
i dont know how, but now i can see the permissions unset... they werent here before (i almost can swear it)

#613376: How to downgrade broken nodewords 1.1+ to 1.0 for a smooth upgrade to 1.3

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