UNiTE, Remote CLI, eXtract Wizard

Wednesday, 23 April 2014 11:08 CDT

swingshoes

I read:
#19119 – Update to 3.2.2 CMS update not working

My update hangs at the "finalise" moment, and I ultimately get:
1091 Can't DROP 'usertype'; check that column/key exists SQL=ALTER TABLE `vts_users` DROP KEY `user type`;

As you recommended, I did a database fix on:
Database schema version (2.5.19) does not match CMS version (3.2.3).
Table 'vts_modules' does not have column 'asset_id'. (From file 3.2.0.sql.)
Table 'vts_users' does not have column 'otpKey'. (From file 3.2.0.sql.)
Table 'vts_users' does not have column 'otep'. (From file 3.2.0.sql.)
Table 'vts_update_sites' does not have column 'extra_query'. (From file 3.2.2-2013-12-22.sql.)
Table 'vts_updates' does not have column 'extra_query'. (From file 3.2.2-2013-12-22.sql.)
Table 'vts_updates' does not have column 'version' with type 'varchar(32)'. (From file 3.2.2-2014-01-18.sql.)

The database fixes everything except for:
Database schema version (3.2.3-2014-02-20) does not match CMS version (3.2.3).

If I select, Content -> Article Manager:
Warning
Error loading component: com_tags, Component not found

Let me know if you have any suggestions for this.
Let me know if you want "keys" to this basically empty site.

Thanks,
Erik

Thursday, 24 April 2014 01:42 CDT

nicholas

This error comes from the SQL file included in the update file by the Joomla! project themselves and is the result of the lack of permissions on your database user.

Please assign all necessary privileges to your database user (you may have to ask your host to do that for you): alter, create, drop, index, insert, select, update, create view and show view. Then go to Extensions, Extension Manager, Database and click on the Fix button.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Friday, 25 April 2014 10:26 CDT

swingshoes

Thank you for your information.
I have made sure that the database-user has "All Privileges"
I have clicked on Extension Manager > Fix Database,
but it still says:
"Database schema version (3.2.3-2014-02-20) does not match CMS version (3.2.3)"

There is also present on Content > Article Manager
Warning
Error loading component: com_tags, Component not found

Thanks,
Erik

Friday, 25 April 2014 11:10 CDT

nicholas

but it still says:

"Database schema version (3.2.3-2014-02-20) does not match CMS version (3.2.3)"

That's a known cosmetic bug in Joomla!. When they updated their code for 3.2.3 they forgot to remove the part after the dash when comparing the version of the installed database and the latest available database revision. They are already aware of it but they have not released a fix yet.

Warning

Error loading component: com_tags, Component not found

Also a bug in Joomla!. Most likely you can go to Extensions, Extension Manager, Discover and it will find the missing extensions. Then select them and click on Install.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Monday, 28 April 2014 23:28 CDT

swingshoes

Thanks! Your suggestions solved the issues for one of my sites.

Here's the next site's issue:
Update hangs at "Finalise"
Can not get back into Extension Manager:
Message:
An error has occurred.
1064 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 '= 'plugin' AND = 'editors' AND = 1' at line 3 SQL=SELECT element, name FROM dancinginct_extensions WHERE = 'plugin' AND = 'editors' AND = 1

Any thoughts on this?
Erik

Tuesday, 29 April 2014 01:52 CDT

nicholas

It's the same thing, all over again. The database update fails (probably just times out?) leading to an incomplete upgrade. At this point the only thing you can do is restore a backup of the site.

I would recommend the following method for performing updates to a new major release of Joomla! (e.g. from 2.x to 3.x):

Take a backup of your live site
Restore it on a local server (MAMP, XAMPP, WAMPserver or Zend Server)
Set max_execution_time=180 and memory_limit=256M in your local server's php.ini and restart it.
Make sure you've shut down as many programmes as possible, especially those which produce a lot of disk activity.
Upgrade your site on the local server.
Take a backup of the upgraded site.
Delete the files of your live site (leave the database intact)
Restore the backup of the upgraded site to the live site.

That's how we do it on all of our sites.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Wednesday, 07 May 2014 21:52 CDT

swingshoes

I followed your directions to the letter, however I still received the same message:
1064 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 '= 'plugin' AND = 'editors' AND = 1' at line 3 SQL=SELECT element, name FROM joom25_extensions WHERE = 'plugin' AND = 'editors' AND = 1

Please let me know any suggestions you have. I can send a jpa file to you if you want.

Thanks,
Erik

Thursday, 08 May 2014 00:58 CDT

nicholas

Sorry, that seems to not be related to our software or Joomla! after all. I guess that you have some very old extension which is not compatible with Joomla! 3. Most likely it's a WYSIWYG editor or something that uses one as far as I can tell from the SQL error.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Thursday, 08 May 2014 10:47 CDT

swingshoes

Is there a way to send the jpa file to you so you can tell me the silly problem plug-in that is causing me grief?

thanks,
Erik

Thursday, 08 May 2014 11:02 CDT

nicholas

No, sorry, I can't debug Joomla! sites on behalf of my clients. I can, however, tell you what I'd do: edit the #__extensions table and unpublish (set enabled=0) to all plugins except the core Joomla! ones. If necessary, I'd do the same with #__modules. One I'd get access to the admin I'd start enabling one plugin/module at a time to find out what the culprit is.

Alternatively, follow this video tutorial to upgrade your site: http://www.siteground.com/tutorials/joomla-video/jooml25-to-joomla3/

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Thursday, 08 May 2014 16:11 CDT

swingshoes

Thanks!!
I disabled all plug-ins.
I was able to view the Administrator side.
Turned on Plug-ins, one by one.
Found problem (System - Show/Hide content)
Deleted Problem plug-in.

It's a slow process to fix.

Is there a way that your component would be able to detect what the conflicting plug-in or module would be? Perhaps a Debug toggle?
For guys like you, this stuff is simple; for guys like me, it makes me go crazy (and feel dumb).

Thanks,
Erik

Thursday, 08 May 2014 17:32 CDT

nicholas

Is there a way that your component would be able to detect what the conflicting plug-in or module would be?

No.

Perhaps a Debug toggle?

No.

For guys like you, this stuff is simple; for guys like me, it makes me go crazy (and feel dumb).

I wouldn't call it "simple" by any definition of the term. Maybe you meant "slow, frustrating and with a chance of making you feel like you were born yesterday"? If that's what you meant with "simple" then, yeah, that's exactly what it is.

FWIW, if I could automate this kind of debugging I could shut down the site restoration section of the support ticket system and probably the entire support. Unfortunately, the level of troubleshooting required for this kind of issues requires a human brain or artificial intelligence. We're not there yet :)

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Saturday, 07 June 2014 18:00 CDT

System Task

system

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

Edited by on 2014-06-07 18:00 CDT

Support