Update error EB 3.8.2 > 3.8.5

  • OTWD
  • Topic Author
  • Offline
  • Platinum Member
  • Platinum Member
More
7 years 1 month ago #122784 by OTWD
Update error EB 3.8.2 > 3.8.5 was created by OTWD
Hi I just updated my J!3.9.3 site with EB 3.8.5
I am getting the error
BIGINT UNSIGNED value is out of range in '(`eckildar_dummyki`.`#__menu`.`level` - 1)'
Package Update: There was an error installing an extension: com_eventbooking.zip


And its messed up my components menu and I cant access EB in the backend anymore
0 Class 'EventbookingController' not found
DB table structure looks good and no errors to fix
index.php?option=com_installer&view=database
Is there a sql fix you can suggest please?

Success consists of going from failure to failure without loss of enthusiasm.

Please Log in or Create an account to join the conversation.

More
7 years 1 month ago #122785 by Tuan Pham Ngoc
Replied by Tuan Pham Ngoc on topic Update error EB 3.8.2 > 3.8.5
I would say that there is a problem with data in #__menu table before you upgrade and it causes the error

For now, better, restore your site to how it was before you update Events Booking

This is something not easy to fix. We will need to check data on that table (a Joomla! core table) to see what's wrong with level field to fix this issue

Tuan

Please Log in or Create an account to join the conversation.

  • OTWD
  • Topic Author
  • Offline
  • Platinum Member
  • Platinum Member
More
7 years 1 month ago #122796 by OTWD
Replied by OTWD on topic Update error EB 3.8.2 > 3.8.5
Thanks Tuan
I have restored my site back to j390 and EB382 what do you suggest i do about the upgrade now? Would you like to view my db tables?

Success consists of going from failure to failure without loss of enthusiasm.

Please Log in or Create an account to join the conversation.

More
7 years 4 weeks ago #122832 by Tuan Pham Ngoc
Replied by Tuan Pham Ngoc on topic Update error EB 3.8.2 > 3.8.5
I would suggest you to look at #__menu table, change data type of level column. Right now, I think it's TinyInt, change it to Int then try to update again. It should address the issue (of course, to be safe, before upgrading, you should make a full backup of your site)

Tuan

Please Log in or Create an account to join the conversation.

  • OTWD
  • Topic Author
  • Offline
  • Platinum Member
  • Platinum Member
More
7 years 4 weeks ago #122870 by OTWD
Replied by OTWD on topic Update error EB 3.8.2 > 3.8.5
Hi Tuan,
I have tried the following
1. The level col is already int(10) in the #__menu table so nothing to change there.
2. I tried to uninstall EB and I couldnt - it would result in the same error
BIGINT UNSIGNED value is out of range in '(`eckildar_backup`.`#__menu`.`level` - 1)'
3. I deleted the administrator > com_eventbooking dir and components>com_eventbooking dir and replaced with a clean 382 version and tried the upgrade - same error
BIGINT UNSIGNED value is out of range in '(`eckildar_backup`.`#__menu`.`level` - 1)'

Success consists of going from failure to failure without loss of enthusiasm.

Please Log in or Create an account to join the conversation.

  • OTWD
  • Topic Author
  • Offline
  • Platinum Member
  • Platinum Member
More
7 years 4 weeks ago #122872 by OTWD
Replied by OTWD on topic Update error EB 3.8.2 > 3.8.5
Ok i tried upgrading joomla first to 3.9.3 then upgraded the EB files - this resulted in the same error BIGINT UNSIGNED value is out of range in '(`eckildar_backup`.`#__menu`.`level` - 1)' however i did not get the 0 Class 'EventbookingController' not found or 1690 error as previous.
I re uploaded a sql dump of my #__menus only and this seemed to fix the error.
It looks like the upgrade has worked except that ?option=com_installer&view=update is still showing v3.8.2 - i cant seem to clear this despite deleting caches etc

Success consists of going from failure to failure without loss of enthusiasm.

Please Log in or Create an account to join the conversation.

More
7 years 4 weeks ago #122892 by Tuan Pham Ngoc
Replied by Tuan Pham Ngoc on topic Update error EB 3.8.2 > 3.8.5
Maybe it's because you just updated the component, not the whole package? Update the whole package and it should be fine

Regards,

Tuan

Please Log in or Create an account to join the conversation.

Moderators: Tuan Pham Ngoc