New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tagging /utility/structure error when upgrading from 2.0.18 to 2.1.6 #2291

Closed
peregrine-web opened this Issue Nov 26, 2014 · 2 comments

Comments

Projects
None yet
2 participants
@peregrine-web

peregrine-web commented Nov 26, 2014

You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'alter table GDN_Tag add unique index UX_Tag (Name, CategoryID)' at line 4|Gdn_Database|Query|/* 'unique index UX_Tag (Name)' => 'unique index UX_Tag (Name, CategoryID)' */ alter table GDN_Tag drop index UX_Tag; alter table GDN_Tag add unique index UX_Tag (Name, CategoryID);

where I saw this happen.

had tagging enabled in 2,0.18 so there was a tag table.
all plugins disabled.

user attempted upgrade
run utlility/structure

above error occurred.

had user go to phpmyadmin and go to your database and

run this
alter table GDN_Tag drop index UX_Tag

and run /utility/structure again and it fixed issue

details here:
http://vanillaforums.org/discussion/comment/220308/#Comment_220308

http://vanillaforums.org/discussion/comment/220308/#Comment_220308

not sure if this is edge effect or why more people haven't reported issue, but 3 different sites reported issue in one day.

@linc linc added the Bug label Nov 26, 2014

@linc linc added this to the 2.1.x milestone Nov 26, 2014

@linc linc changed the title from /utility/structure error when upgrading from 2.0.18 to 2.1.6 to Tagging /utility/structure error when upgrading from 2.0.18 to 2.1.6 Nov 26, 2014

@peregrine-web

This comment has been minimized.

peregrine-web commented Nov 27, 2014

another piece of info surfaced. the person who I helped was using tagging enhanced prior to upgrade,

@linc

This comment has been minimized.

Member

linc commented Jan 20, 2015

I believe we fixed this with 2.1.8p2.

@linc linc closed this Jan 20, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment