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: Errors trying to upgrade Publisher Lite from 2.11.2 to 3.2.2
| Status | Resolved |
| Add-on / Version | Publisher Lite 2.11.2 |
| Severity | |
| EE Version | 5.4.1 |
Fabcom
Feb 18, 2021Hello, we’re trying to upgrade Publisher Lite 2.11.2 to the latest 3.2.2 and running into errors. After copying over the system and themes folders, we’re first asked for the new license, which I entered, then went to step 2:
Publisher detected 1847 rows to import.
2615 of 1847 entries imported so far. The rest of the installation process may take a few seconds or minutes depending on the number of entries you have. You will be updated on the progress as the entries are imported.
After clicking continue, there’s an exception error right away and then clicking anything mostly anything else in EE brings us back to step 2:
Exception Caught
SQLSTATE[42S02]: Base table or view not found: 1146 Table ‘****dbnameredacted*****.exp_publisher_data_field_38’ doesn’t exist:
ee/legacy/database/drivers/mysqli/mysqli_connection.php:117
Stack Trace: Please include when reporting this error
#0 ee/legacy/database/drivers/mysqli/mysqli_driver.php(112): CI_DB_mysqli_connection->query()
#1 ee/legacy/database/DB_driver.php(270): CI_DB_mysqli_driver->_execute()
#2 ee/legacy/database/DB_driver.php(180): CI_DB_driver->simple_query()
#3 user/addons/publisher/Service/Migration.php(247): CI_DB_driver->query()
#4 user/addons/publisher/mod.publisher.php(1418): BoldMinded\Publisher\Service\Migration->installEntryData()
#5 ee/legacy/libraries/Actions.php(209): Publisher->install_migrate_entries()
#6 ee/legacy/libraries/Core.php(549): EE_Actions->__construct()
#7 ee/legacy/controllers/ee.php(59): EE_Core->generate_action()
#8 [internal function]: EE->index()
#9 ee/EllisLab/ExpressionEngine/Core/Core.php(268): call_user_func_array()
#10 ee/EllisLab/ExpressionEngine/Core/Core.php(118): EllisLab\ExpressionEngine\Core\Core->runController()
#11 ee/EllisLab/ExpressionEngine/Boot/boot.php(156): EllisLab\ExpressionEngine\Core\Core->run()
#12 index.php(172): require_once(’...’)
#12 index.php(172): require_once(’...’)
BoldMinded (Brian)
You might have to revert to the database version before you tried upgrading, then use the build in the next comment. Hopefully it works. Someone else had a similar issue, and I think this build might fix it.
BoldMinded (Brian)
Comment has been marked private.
Fabcom
Started clean at 2.11.2 and tried upgrading with 3.2.4.. Initially I got the same exception error, then I re-tried and it said good to go, though still said 2.11.2 on the EE addon list page. I then clicked “update to 3.2.4” and received a “Good to go! Publisher upgrade is complete!”, but I’m stuck on that and can’t logout or click anywhere without being redirected back to saying upgrade complete…
BoldMinded (Brian)
Run these two queries separately, what are the results?
BoldMinded (Brian)
Is this a site you can package up and send to me so I can try to replicate this locally? Would need files and sql dump of the working site with 2.11.2 installed. If so, zip it up somewhere (Dropbox or whatever) and post a link in a private message. Make a fresh super admin account for me and share that login too.
Fabcom
install_complete = yes migration_complete = no
I’m seeing if sharing a zip of the site is an option.
Fabcom
Comment has been marked private.
BoldMinded (Brian)
Try the build in the next comment. I think I found the issue. The upgrade from 2.x directly to 3.0.0 worked fine, but people upgrading from 2.x to 3.1 or greater didn’t get through the migration process correctly.
BoldMinded (Brian)
Comment has been marked private.
Fabcom
Thank you, that worked!
I went ahead and upgraded EE to 6.0.3, but now I’m getting “Unlicensed Add-on: Publisher does not have a valid license.”, maybe due to that dev 3.2.4 version? I tried re-entering our license but still the same…
BoldMinded (Brian)
What license key are you using? Be sure to mark the message as private when you share the key.
Fabcom
Comment has been marked private.
BoldMinded (Brian)
Yeah that key is definitely valid. I changed how the license validation works in the newer builds, so it’s possibly a bug with the new code. Try deleting the publisher_last_ping file in your cache directory and see if it resolves it.
Fabcom
no luck, if I delete it, it gets recreated as soon as you navigate anywhere in the EE admin.
BoldMinded (Brian)
Comment has been marked private.
Fabcom
I did need to re-save the license, but that seemed to have worked, thanks again.