Relevant to the other long bug report that is now closed, a number of us are left with corrupted data. Please tell us how to fix it.

Comments

avpaderno’s picture

Status: Active » Closed (duplicate)

See #654206: Upgrade to 1.7 fails to complete on some installations, and corrupts data, which has been marked as fixed because the problem has been already fixed, and the referring version for that report says in which version it has been fixed.

I am marking this report as duplicate.

Starminder’s picture

Status: Closed (duplicate) » Active

I am unable to add a comment to the existing issue, it is somehow now closed. Myself and others still have problems and do not know how to fix it. If you want me to comment in the existing issue, then please open it back up. I am using the current Dev version, yet my data is still messed up.

avpaderno’s picture

@Starminder: Which version are you using?

avpaderno’s picture

Status: Active » Postponed (maintainer needs more info)
Starminder’s picture

I was on 1.8 - I updated to Dev (Dec 15). My corrupted data is now gone, however, I now have no nodewords at all (at least according to SEO friend). I edited some content hoping it would repopulate the meta tags for that node, but the report still shows as empty. Not sure what to do next. Thanks.

Starminder’s picture

Status: Postponed (maintainer needs more info) » Needs review
avpaderno’s picture

Status: Needs review » Active

I installed version 6.x-1.7 on my test site, I created some meta tags for some nodes, updated to version 6.x-1.8; there was no corrupted meta tags.
I then updated to the latest development snapshot (the one without an archive, yet), and still the meta tags content were not corrupted.

avpaderno’s picture

I also tried installing version 6.x-1.6, creating some meta tags for nodes, and then updating to version 6.x-1.7, 6.x-1.8, 6.x-1.9. The only problem I noticed is that the meta tag ROBOTS has been reset, but no meta tags have been corrupted.

avpaderno’s picture

Status: Active » Fixed

Basing on my tests, I can report this issue has been already resolved.

Status: Fixed » Closed (fixed)

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