EE compatibility updates:

  • Publisher is EE5 compatible, but it does not currently support the Fluid field.

ExpressionEngine.com licenses:

  • 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 ‘ee_ace.exp_publisher_data_field_47’ doesn’t exist:

Status Resolved
Add-on / Version Publisher 3.2.2
Severity
EE Version 5.2.2

Eric Harth

Feb 08, 2021

hi mate,

I am trying to install the new version of the publisher and have been getting few errors. PFA stacktrace.


e/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(‘SELECT `ct`.*, ...’)
#1 ee/legacy/database/DB_driver.php(270): CI_DB_mysqli_driver->_execute(‘SELECT `ct`.*, ...’)
#2 ee/legacy/database/DB_driver.php(180): CI_DB_driver->simple_query(‘SELECT `ct`.*, ...’)
#3 user/addons/publisher/Service/Entry/EntryQuery.php(231): CI_DB_driver->query(‘SELECT `ct`.*, ...’)
#4 user/addons/publisher/Service/Entry/EntryResult.php(502): BoldMinded\Publisher\Service\Entry\EntryQuery->getResultArray()
#5 user/addons/publisher/Service/Entry/EntryResult.php(220): BoldMinded\Publisher\Service\Entry\EntryResult->getAllQuery(Array, Array)
#6 user/addons/publisher/ext.publisher.php(869): BoldMinded\Publisher\Service\Entry\EntryResult->getAll(Array, Array)
#7 ee/legacy/libraries/Extensions.php(247): Publisher_ext->channel_entries_query_result(Object(Channel), Array)
#8 ee/legacy/libraries/Extensions.php(142): EE_Extensions->call_class(‘Publisher_ext’, ‘channel_entries…’, Array, Array)
#9 ee/EllisLab/Addons/channel/mod.channel.php(2756): EE_Extensions->call(‘channel_entries…’, Object(Channel), Array)
#10 ee/EllisLab/Addons/channel/mod.channel.php(281): Channel->parse_channel_entries()
#11 ee/legacy/libraries/Template.php(1847): Channel->entries()
#12 user/addons/stash/mod.stash.php(4327): EE_Template->process_tags()
#13 user/addons/stash/mod.stash.php(4523): Stash->_parse_sub_template(true, true, true, ‘2’)
#14 user/addons/stash/mod.stash.php(1583): Stash->_parse_output(’\n {exp:c…’)
#15 ee/legacy/libraries/Template.php(1847): Stash->set_list()
#16 user/addons/stash/mod.stash.php(4327): EE_Template->process_tags()
#17 user/addons/stash/mod.stash.php(3087): Stash->_parse_sub_template(true, true, true, ‘4’)
#18 user/addons/stash/ext.stash.php(453): Stash->parse()
#19 ee/legacy/libraries/Extensions.php(247): Stash_ext->template_post_parse(’{!—ra:0000000…’, false, ‘1’)
#20 ee/legacy/libraries/Extensions.php(142): EE_Extensions->call_class(‘Stash_ext’, ‘template_post_p…’, Array, Array)
#21 ee/legacy/libraries/Template.php(246): EE_Extensions->call(‘template_post_p…’, ‘{!—ra:0000000…’, false, ‘1’)
#22 ee/legacy/libraries/Template.php(165): EE_Template->fetch_and_parse(‘acer’, Array, false)
#23 ee/legacy/libraries/Core.php(661): EE_Template->run_template_engine(‘acer’, ‘index’)
#24 ee/legacy/controllers/ee.php(63): EE_Core->generate_page()
#25 [internal function]: EE->index()
#26 ee/EllisLab/ExpressionEngine/Core/Core.php(241): call_user_func_array(Array, Array)
#27 ee/EllisLab/ExpressionEngine/Core/Core.php(110): EllisLab\ExpressionEngine\Core\Core->runController(Array)
#28 ee/EllisLab/ExpressionEngine/Boot/boot.php(151): EllisLab\ExpressionEngine\Core\Core->run(Object(EllisLab\ExpressionEngine\Core\Request))
#29 index.php(173): require_once(’...’)
#29 index.php(173): require_once(’...’)

#1

BoldMinded (Brian)

Feb 08, 2021

What version are you upgrading from?

#2

BoldMinded (Brian)

Feb 08, 2021

Try the build in the next comment, then go to the Publisher > Utilities page and there is a Sync and Cleanup option. See if either of those pages are telling you that something needs to be fixed. Backup your DB first before taking any action.

#3

BoldMinded (Brian)

Feb 08, 2021

Comment has been marked private.

#4

Eric Harth

Feb 08, 2021

I am trying to migrate from EE 5.2 to EE 6.

#5

Eric Harth

Feb 08, 2021

i can see no errors now and both sync and cleanup options show good. but i am seeing a screen saying

Publisher detected 8447 rows to import.

16864 of 8447 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.

nothing seems to be changing at all.

#6

Eric Harth

Feb 08, 2021

Hi Mate, i did work i am able to install publisher 3.2.4 but I find a weird issue in the control panel the publisher version still says 2.11.1 which my previous version and i can still see the update to 3.2.4 button.?.

#7

BoldMinded (Brian)

Feb 09, 2021

The entry import process should only happen on initial install, not an upgrade. That and the fact that it still says version 2.11 is installed sound a like you’re doing an upgrade from EE 2 to 6? I have no idea what state your site is in so it’s hard to provide directions.

#8

Eric Harth

Feb 09, 2021

I cant see the update to 3.2.4 button in the control panel with the existing 2.11 version. I can only see the update to 3.2.4 button when I replace the existing publisher addon 2.11 with the new one.

#9

Eric Harth

Feb 09, 2021

Hi mate,

What does cp_members_member_delete_end NOT INSTALLED. i am getting this in diagnostics section.

#10

Eric Harth

Feb 10, 2021

and more even this error


Exception Caught
SQLSTATE[42000]: Syntax error or access violation: 1061 Duplicate key name ‘pub_key’:
ALTER TABLE `exp_publisher_titles` ADD UNIQUE KEY `pub_key` (entry_id, lang_id, status)
ee/legacy/database/drivers/mysqli/mysqli_connection.php:114

Stack Trace: Please include when reporting this error
#0 ee/legacy/database/drivers/mysqli/mysqli_driver.php(112): CI_DB_mysqli_connection->query(‘ALTER TABLE `ex…’)
#1 ee/legacy/database/DB_driver.php(260): CI_DB_mysqli_driver->_execute(‘ALTER TABLE `ex…’)
#2 ee/legacy/database/DB_driver.php(175): CI_DB_driver->simple_query(‘ALTER TABLE `ex…’)
#3 user/addons/publisher/updates/up_3_00_00.php(64): CI_DB_driver->query(‘ALTER TABLE `ex…’)
#4 user/addons/publisher/Library/Basee/Updater.php(95): Update_3_00_00->doUpdate()
#5 user/addons/publisher/upd.publisher.php(587): BoldMinded\Publisher\Library\Basee\Updater->runUpdates()
#6 ee/ExpressionEngine/Controller/Addons/Addons.php(320): Publisher_upd->update(‘2.11.1’)
#7 [internal function]: ExpressionEngine\Controller\Addons\Addons->update(Array)
#8 ee/ExpressionEngine/Core/Core.php(251): call_user_func_array(Array, Array)
#9 ee/ExpressionEngine/Core/Core.php(111): ExpressionEngine\Core\Core->runController(Array)
#10 ee/ExpressionEngine/Boot/boot.php(161): ExpressionEngine\Core\Core->run(Object(ExpressionEngine\Core\Request))
#11 kayru.php(144): require_once(’...’)
#11 kayru.php(144): require_once(’...’)

#11

BoldMinded (Brian)

Feb 10, 2021

I can only see the update to 3.2.4 button when I replace the existing publisher addon 2.11 with the new one.

 

That sounds correct. Why do you think that is wrong?

Can you provide some videos or screenshots of what you’re seeing? As mentioned before I have no idea what state your site is in or what you did to this point that might have caused this, so it’s hard to know what is going on. At this point I’d recommend starting over with the upgrade, because it sounds like it’s in a half upgraded state.

#12

BoldMinded (Brian)

Feb 10, 2021

You also didn’t answer my question if you’re upgrading from an EE 2 install to 6?

#13

Eric Harth

Feb 10, 2021

I am upgrading from EE 5.2.2 to EE 6

#14

Eric Harth

Feb 10, 2021

I mean even after the update why is it still showing that update to 3.2.4 button

#15

Eric Harth

Feb 10, 2021

I have attached few screen shots when i click on the update to 3.2.4 button it throws that error which is in the screenshot attached. And i have attached the diagnostics section screenshot as well which says its missing   cp_members_member_delete_end NOT INSTALLED. PFA..

#16

BoldMinded (Brian)

Feb 10, 2021

It would probably be preferable if you were able to update Publisher while in EE 5.x, before going to 6. I’m not even sure how to advise you on this right now b/c there are so many things awry that I don’t know what state the site is in, or what things might have manually be done that could be causing the issues. I’m now even sure how Publisher was working in 5.x if you were running version 2.11. Starting with version 3 you had to be running EE4 or later. The 3.0 upgrade of Publisher should have migrated all the data, but you were seeing that 16864 of 8447 rows were migrated message.

As of this moment you’re upgrading from 5.2 to 6, but did you start recently with an EE 3 or 4 build and are in the process of going to 6? Prior to version 5.2, what version of EE were you running and how long ago was that? I’m just trying to wrap my head around what is going on, because none of this adds up to me.

#17

Eric Harth

Feb 10, 2021

answer to your question NO we have migrated from ee2 to ee5 more than 2 years back. We are now in a process of migrating to EE6 from EE5. Prior to EE5.2 we were running EE 2.2 for 2-3 years. We never installed publisher 3.0.

#18

Eric Harth

Feb 10, 2021

The version 3.1.2 has got this cp_members_member_delete_end hook update for some reason i am unable to get this hook being populated in the exrtensions table. This even might be an issue. Do we have to install the previous versions of publisher before we install the latest 3.2.2 one?

#19

BoldMinded (Brian)

Feb 10, 2021

What happens if you update the exp_modules table and set Publisher back to version 3.0.0? Then click the run update again? Everything looks correct with the 3.1.1 update file, which is when that hook was added. I don’t see any reason for the hook to not to be installed.

#20

BoldMinded (Brian)

Feb 10, 2021

Ohhh, wait. I see the issue. At the end of the 3.0.0 update it does a redirect, so it never gets to the 3.1.1 update, which is next in line. I’ll look into this a bit and see if I can send you a fix.

#21

BoldMinded (Brian)

Feb 10, 2021

I _think_ the quickest course of action is to roll back to EE 5.x, and Publisher 2.11.1, before you started the upgrade to EE 6, then in the latest Publisher 3.x codebase open up the updates/up_3_00_00.php file and comment out these two lines (lines 89 and 90)

$migration = ee(Migration::NAME);
$migration->startMigration();

This should let the upgrade finish, then when it’s done go to the Publisher add-on page and there is a Utilities > Install Step 2 link, go there and it should resume migrating the data. The $migration->startMigration() call you’re disabling does a redirect to this page prematurely, so the rest of the updates don’t get executed. This should get you updated.

Sorry for what it took to get to this point in the process 😊

#22

BoldMinded (Brian)

Feb 10, 2021

Actually, don’t do that. That might end up skipping some data migration. I’ll have to spend a little more time with this to find a better solution, sorry.

#23

Eric Harth

Feb 11, 2021

Found the issue mate. I have successfully migrated to Publisher 3.2.4.  The issue was if the install fails we have to truncate all the tables and reimport a fresh db.

Login to reply