Hello,

yesterday i noticed that my metatags arent showing on 6.x-1.5 so i upgraded to version 6.x-1.6 because the updater is bugged in the 6.x-1.7 version, but when i try to go to /admin/content/nodewords/meta-tags i get the following error:

Fatal error: Cannot unset string offsets in /usr/home/<username>/domains/ashladan.be/public_html/sites/all/modules/nodewords/nodewords_basic/nodewords_basic.module on line 571

i already downloaded a new copy of the 6.x-1.6 version and uploaded it.. and it still gives the error, but it seems that i can't acces the advanced settings of the module, and now my frontpage has no metatags, but the node tags still work..

php version 5.2.8

Comments

avpaderno’s picture

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

I tested the latest development snapshot (it will be available at 12:00 AM UTC), and I don't notice the problem you have, which is probably caused by the problem with the latest update function.

demon326’s picture

demon326 commented
Status: Fixed » Active

kiamlaluno, i'v just update to the lates dev release, and the error is still there, and only on my live website, my other sites, on the same host running drupal don't have the problem... it seems that there is something els in conflict....

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

The code present at line 571 is the following:

    unset($content['value']['noopd']);

The error you see is caused by an update which was not completed.
I will add an update function that resolves the problem you are seeing.

demon326’s picture

demon326 commented

kiam, i updated to 6.x-1.8 and the problems are solved, you can close this report and thanks for the support.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Fixed

I am glad to know the problem has been fixed.
Thank you for your report.

Status: Fixed » Closed (fixed)

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