Publisher does not support the Fluid field type. Please do not contact asking when support will be available.
If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.
Ticket: SQLSTATE[42S02]: Base table or view not found: 1146 Table ‘kub_ee.exp_publisher_data_field_70’ doesn’t exist:
Status | Resolved |
Add-on / Version | Publisher 3.2.2 |
Severity | |
EE Version | 5.2.3 |
Elli Pratt
Jan 21, 2021We are updating addons in our EE installation.
When we update publisher to the latest version 3.2.2 from version 2.11.2, we are unable to get to the admin area or site.
It appears that the addon didn’t run it’s migration to the new database schema.
This error is received on the site:
SQLSTATE[42S02]: Base table or view not found: 1146 Table 'kub_ee.exp_publisher_data_field_70' doesn't exist:
SELECT `ct`.*, `t`.*, `channel_title`, `c`.`channel_name`, `c`.`channel_url`, `c`.`comment_url`, `c`.`comment_moderate`, `c`.`channel_html_formatting`, `c`.`channel_allow_img_urls`, `c`.`channel_auto_link_urls`, `c`.`comment_system_enabled`, `username`, `m`.`email`, `m`.`screen_name`, `m`.`signature`, `m`.`sig_img_filename`, `m`.`sig_img_width`, `m`.`sig_img_height`, `m`.`avatar_filename`, `m`.`avatar_width`, `m`.`avatar_height`, `m`.`photo_filename`, `m`.`photo_width`, `m`.`photo_height`, `m`.`group_id`, `m`.`member_id`, `ct`.`url_title` AS default_url_title, `ct`.`status` AS status, `t`.`title` AS title, `t`.`site_id` AS entry_site_id, `exp_publisher_data_field_70`.`field_id_70` AS field_id_70, `exp_publisher_data_field_71`.`field_id_71` AS field_id_71, `exp_publisher_data_field_72`.`field_id_72` AS field_id_72, `exp_publisher_data_field_73`.`field_id_73` AS field_id_73, `exp_publisher_data_field_74`.`field_id_74` AS field_id_74, `exp_publisher_data_field_75`.`field_id_75` AS field_id_75, `exp_publisher_data_field_76`.`field_id_76` AS field_id_76 FROM (`exp_publisher_titles` AS t) JOIN `exp_channel_titles` AS ct ON `ct`.`entry_id` = `t`.`entry_id` JOIN `exp_channels` AS c ON `c`.`channel_id` = `t`.`channel_id` LEFT JOIN `exp_publisher_data_field_70` ON `t`.`entry_id` = `exp_publisher_data_field_70`.`entry_id` AND t.lang_id = exp_publisher_data_field_70.lang_id AND t.status = exp_publisher_data_field_70.status AND exp_publisher_data_field_70.is_fluid = 0 LEFT JOIN `exp_publisher_data_field_71` ON `t`.`entry_id` = `exp_publisher_data_field_71`.`entry_id` AND t.lang_id = exp_publisher_data_field_71.lang_id AND t.status = exp_publisher_data_field_71.status AND exp_publisher_data_field_71.is_fluid = 0 LEFT JOIN `exp_publisher_data_field_72` ON `t`.`entry_id` = `exp_publisher_data_field_72`.`entry_id` AND t.lang_id = exp_publisher_data_field_72.lang_id AND t.status = exp_publisher_data_field_72.status AND exp_publisher_data_field_72.is_fluid = 0 LEFT JOIN `exp_publisher_data_field_73` ON `t`.`entry_id` = `exp_publisher_data_field_73`.`entry_id` AND t.lang_id = exp_publisher_data_field_73.lang_id AND t.status = exp_publisher_data_field_73.status AND exp_publisher_data_field_73.is_fluid = 0 LEFT JOIN `exp_publisher_data_field_74` ON `t`.`entry_id` = `exp_publisher_data_field_74`.`entry_id` AND t.lang_id = exp_publisher_data_field_74.lang_id AND t.status = exp_publisher_data_field_74.status AND exp_publisher_data_field_74.is_fluid = 0 LEFT JOIN `exp_publisher_data_field_75` ON `t`.`entry_id` = `exp_publisher_data_field_75`.`entry_id` AND t.lang_id = exp_publisher_data_field_75.lang_id AND t.status = exp_publisher_data_field_75.status AND exp_publisher_data_field_75.is_fluid = 0 LEFT JOIN `exp_publisher_data_field_76` ON `t`.`entry_id` = `exp_publisher_data_field_76`.`entry_id` AND t.lang_id = exp_publisher_data_field_76.lang_id AND t.status = exp_publisher_data_field_76.status AND exp_publisher_data_field_76.is_fluid = 0 JOIN `exp_members` AS m ON `m`.`member_id` = `t`.`author_id` WHERE `t`.`entry_id` IN (1818) AND `t`.`status` = 'open' AND `t`.`lang_id` = 1
The addon area has what seems to be just generic warnings:
Notice
Use of undefined constant BASE - assumed 'BASE'
ee/legacy/core/URI.php, line 333
Severity: E_NOTICE
Warning
Cannot modify header information - headers already sent by (output started at ee/legacy/core/Exceptions.php:120)
ee/legacy/libraries/Functions.php, line 393
Severity: E_WARNING
BoldMinded (Brian)
Jan 21, 2021
Elli, can you provide more information? What is the rest of the stack trace around that query? It should show what methods were called prior to that and lines of code etc, which will be helpful. Can you also describe what process you took… when did this happen? Did you run Publisher’s updates or did this happen immediately after logging into EE 5 for the first time? I don’t have much context to work with… the more you can provide the better. Thanks.
Elli Pratt
Jan 21, 2021
Before this, we updated our assets, structure, and low_search addons.
These addons updated successfully.
When upgrading publisher,
- We first copied all of the files from the publisher zip on top of the existing files (in appropriate locations). This is where the below text showed up.
- For sanity, I did then delete the entire addon folder and copied the files in just in case there was erroneous files.
There was no other action beyond copying the files for the installation.
(exception text posted in another reply)
Elli Pratt
Jan 21, 2021
Here is the stack trace:
BoldMinded (Brian)
Jan 21, 2021
So that error is happening on the front-end? You should login to the CP first, then run the module upgrades.
Elli Pratt
Jan 21, 2021
That’s what I was thinking, but when the addon files were copied over, the admin page becomes inaccessible.
This is all that is shown in the login page. Just a blank screen with warnings.
Elli Pratt
Jan 21, 2021
I would also like to add that we tried a quick upgrade to EE 5.4.0 to see if the issue was EE, but the issue still appeared.
BoldMinded (Brian)
Jan 21, 2021
The first 2 errors are just notices, they shouldn’t stop anything from processing. There was nothing displayed below “Severity: E_WARNING”?
BoldMinded (Brian)
Jan 21, 2021
Wait, never mind. I misread that. The headers already sent is the Severity: E_WARNING error.
BoldMinded (Brian)
Jan 21, 2021
What other add-ons do you have installed?
Elli Pratt
Jan 21, 2021
Here are the other addons -
Assets, Low Search, Structure, Wygwam, cache buster, JSON Encode, LDAP authentication, Mo Variables, SEO Lite, Snippets Sync, Streeng
BoldMinded (Brian)
Jan 21, 2021
You don’t need Snippet Sync in EE 3+, it’s basically native functionality now. FYI.
Make this update and see if it fixes anything. ext.publisher.php, line 2173 or so you should see this:
Change it to this:
Elli Pratt
Jan 21, 2021
Good to know. Thanks! We will remove it.
The fix does not resolve the issue. The same error appears.
BoldMinded (Brian)
Jan 21, 2021
I’ve seen this happen before… something is trying to perform a redirect but EE’s core URI library needs to use the BASE constant, but it isn’t defined yet.
Try adding this to the URI.php file, line 352 or so.
Elli Pratt
Jan 22, 2021
Here is what was printed out:
BoldMinded (Brian)
Jan 22, 2021
Thanks for that var dump. Based on what I see there, the changes I suggested earlier should work.
if ($ping->shouldPing() && defined(‘BASE’)) {
It’s trying to redirect you to the license entry page.
Try moving it down a little further to the 2nd conditional:
Elli Pratt
Jan 22, 2021
I still received the same message.
I did some messing around I observed that if I remove the “validateLicense” function I still had the same error.
I went to the next function “validateInstallComplete” and my observations our in comments below.
Would I be correct in thinking the issue is the redirect line?
BoldMinded (Brian)
Jan 22, 2021
Ahh, forgot about that function. Try changing it to this:
Elli Pratt
Jan 22, 2021
Success!! I was able to login to the CP and finish the upgrade.
Thank you much!
BoldMinded (Brian)
Jan 22, 2021
Awesome! Sorry for the ordeal :(
I’ll make sure this change makes it into the next release.