Upgrade from 8.2.1 to 8.3.1 leaves a table unturned and a big error message. Can it be fixed?
Permalink 2 users found helpful
8.3.1 is supposed to be able to upgrade directly from any version after 5.7.5.13. However, I discovered what apparently is a missing table when I upgraded some sites from 8.2.1. Going into the Extend menu after the upgrade, when I attempted to remove an add-on, I got a message similar to the one below:
An unexpected error occurred.
I could not remove the add-on from within the application.
I also noticed the same (or similar) message with each installed add-on. I can add more but I cannot remove them.
Also, a new menu item, Geolocation, renders a similar error.
I know 1146 is a missing table code.
I tried upgrading to 8.3.0 and then to 8.3.1 on another site, and there was no error.
I tried downgrading to 8.3.0 and then returning to 8.3.1 -- the error persists.
Foolish me: I'd upgraded at least 5 sites before noticing the error, and did not backup the last two.
Soo... recommendations? Geolocation isn't high on my organization's list -- in fact, i might have to disable it. However, it's still a potential turnoff for my users to get that big, fat red error message. Any help appreciated.
An unexpected error occurred.
An exception occurred while executing 'SELECT t0.glID AS glID_1, t0.glHandle AS glHandle_2, t0.glName AS glName_3, t0.glDescription AS glDescription_4, t0.glConfiguration AS glConfiguration_5, t0.glActive AS glActive_6, t0.glPackage AS glPackage_7 FROM Geolocators t0 WHERE t0.glPackage = ?' with params [21]: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'yfsneals_imcomhq.Geolocators' doesn't exist
I could not remove the add-on from within the application.
I also noticed the same (or similar) message with each installed add-on. I can add more but I cannot remove them.
Also, a new menu item, Geolocation, renders a similar error.
I know 1146 is a missing table code.
I tried upgrading to 8.3.0 and then to 8.3.1 on another site, and there was no error.
I tried downgrading to 8.3.0 and then returning to 8.3.1 -- the error persists.
Foolish me: I'd upgraded at least 5 sites before noticing the error, and did not backup the last two.
Soo... recommendations? Geolocation isn't high on my organization's list -- in fact, i might have to disable it. However, it's still a potential turnoff for my users to get that big, fat red error message. Any help appreciated.
I just upgraded a site from 8.2.1 to 8.3.1 directly without seeing this issue. I have also checked my clean 8.3.1 database and there is no table Geolocators, so this table must be part of a package. Have you tried clearing your cache then removing packages again?
Yes, cache was cleared. "Geolocation" showed up in Systems and Settings for the first time when I upgraded. Also, I am not very successful in removing packages outside the program. Part of the breakdown is I get the error message instead of the add-on page (with the delete button) under the Extend Concrete5 page.
I understand what you are saying now, I thought you were saying that the Extend Concrete5 page was throwing errors but it's after you click the Details button.
I can confirm that upgrading from 8.2.1 to 8.3.1 results in the same errors as what you are saying. However a clean install of 8.3.1 does not.
The only way that I was able to correct this was to manually re-create the table in the database based on my clean 8.3.1 install. Attached is the SQL I used to create the database, you can use phpMyAdmin to run this and create the table. I have also posted about this in the bug_team channel on slack so hopefully it will be corrected in 8.3.2.
I can confirm that upgrading from 8.2.1 to 8.3.1 results in the same errors as what you are saying. However a clean install of 8.3.1 does not.
The only way that I was able to correct this was to manually re-create the table in the database based on my clean 8.3.1 install. Attached is the SQL I used to create the database, you can use phpMyAdmin to run this and create the table. I have also posted about this in the bug_team channel on slack so hopefully it will be corrected in 8.3.2.
It works. Thanks.
If you could please comment on this GitHub issue about this topic to let the core team know that you had/have the same issue, that would be great
https://github.com/concrete5/concrete5/issues/6284...
https://github.com/concrete5/concrete5/issues/6284...
