Be sure to checkout our newest add-on Reading Time Pro!

EE4 compatibility updates:

  • Publisher is EE4 and EE5 compatible, but it does not currently support the Fluid field (it's in the works).
  • Reel is EE4 and EE5 compatible, but it does not currently support the Fluid field.

Ticket: Update issue

Status Resolved
Add-on / Version Publisher Lite 2.7.6
Severity
EE Version 3.5.12
Images

Harold Kuiper

Jan 23, 2020

Hi Brian,

We are working on updating from EE3.5.12 to the latest version 5 of a pretty big website.

When updating from 3 to 4 we bump into the same issue as in this ticket: https://boldminded.com/support/ticket/1702 We encounter a ‘Dependency Injection: Unregistered service “publisher:Cache”’ as well. The solution at the end of the page doesn’t work for us as we have no expeditie_channels_statuses in our database.

What shall we do? We run Publisher Lite 2.7.6. After updating (in ee3) of Publisher Lite it runs through all channels (rows) but when opening an entry we get a sql error.

Do you have some tips on how to overcome the issue?

Best regards,

Harold

 

#1

BoldMinded (Brian)

Jan 24, 2020

“but when opening an entry we get a sql error” - Can you share the error?

#2

BoldMinded (Brian)

Jan 24, 2020

Comment has been marked private.

#3

Harold Kuiper

Jan 25, 2020

Hi Brian,
First: thanks!
We had help from Robin Sowell (EllisLab) and he helped us get over the bug and we managed to update to ee5. Which is a great step.
Last thing is upgrading to Publisher 3.
We click the update and we get this error:

SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'expiration_date':
ALTER TABLE `exp_publisher_titles` ADD `expiration_date` int(10) DEFAULT 0 AFTER `edit_date`

This is when we’re upgrading from 2.11.2 and 3 as well.
Do we need to send you entry to our CP?
Best regards,
Harold

#4

Harold Kuiper

Jan 27, 2020

Hi Brian,
Robin is checking out the errors as well.
Do you have any clue on this?
Best regards,
Harold

#5

BoldMinded (Brian)

Jan 27, 2020

Comment has been marked private.

#6

Harold Kuiper

Jan 27, 2020

Comment has been marked private.

#7

BoldMinded (Brian)

Jan 27, 2020

Harold, logging into customer servers is the absolute last thing I’ll do to debug an issue, and I’m not there yet. When sending FTP info, please edit the ticket and provide the info in the fields provided. When the ticket is closed, the info is removed from my database. Using the secret means I have to save the info somewhere in order to re-access the system, which is insecure.

Are you saying the last build I sent did not fix the SQL error from comment #3? Are you still getting the “publisher:Cache” error from your original report?

#8

BoldMinded (Brian)

Jan 27, 2020

When you got the publisher:Cache error, you should have gotten a full stack trace of the error. Can you please share that?

#9

Harold Kuiper

Jan 27, 2020

Hi Brian,
Will do that asap. It is evening here and I’m commuting now. When I’m home I send you the last trace.
Harold

#10

Harold Kuiper

Jan 27, 2020

Comment has been marked private.

#11

Harold Kuiper

Jan 27, 2020

Comment has been marked private.

#12

BoldMinded (Brian)

Jan 27, 2020

Harold, I’m going to edit your last comment and remove the FTP info you provided. Leaving it in a comment means it is in my database forever, I don’t want that, and you probably don’t either. Please edit the ticket and use the fields provided in the ticket description. There are separate fields for each piece of login information.

#13

BoldMinded (Brian)

Jan 27, 2020

Harold, based on that last error, it sounds like you need to roll back your database and start the upgrade process from the beginning. You’re trying to finish a half completed upgrade.

#14

Harold Kuiper

Jan 27, 2020

Hi Brian,
I will try.
Best regards,
Harold

#15

Harold Kuiper

Jan 27, 2020

Comment has been marked private.

#16

Harold Kuiper

Jan 27, 2020

I roll it back again to before updating.

#17

Harold Kuiper

Jan 28, 2020

Hi Brian,
What do you suggest for me to do?
Best regards,
Harold

#18

BoldMinded (Brian)

Jan 28, 2020

I suggested rolling the database back and starting the upgrade from scratch. Did that not work? If not what is the current issue (including full error messages if present)?

#19

Harold Kuiper

Jan 28, 2020

Comment has been marked private.

#20

BoldMinded (Brian)

Jan 28, 2020

is there more to that error message? I feel like there should be an SQL query string that it says it is failing on.

#21

Harold Kuiper

Jan 28, 2020

Comment has been marked private.

#22

BoldMinded (Brian)

Jan 28, 2020

Run these two queries directly on your database. Sounds like there are artifact rows that need to be deleted manually before you run the upgrade.

SELECT *
    FROM
        `exp_publisher_titles` AS `a`,
        `exp_publisher_titles` AS `b`
    WHERE
        -- Ensures one version remains
        `a`.`id` < `b`.`id`
        -- Find duplicates
        AND `a`.`lang_id` <=> `b`.`lang_id`
        AND `a`.`status` <=> `b`.`status`
        AND `a`.`entry_id` <=> `b`.`entry_id`;

SELECT *
    FROM
        `exp_publisher_data` AS `a`,
        `exp_publisher_data` AS `b`
    WHERE
        -- Ensures one version remains
        `a`.`id` < `b`.`id`
        -- Find duplicates
        AND `a`.`lang_id` <=> `b`.`lang_id`
        AND `a`.`status` <=> `b`.`status`
        AND `a`.`entry_id` <=> `b`.`entry_id`;
#23

Harold Kuiper

Jan 28, 2020

Comment has been marked private.

#24

Harold Kuiper

Jan 28, 2020

Hi Brian,
You can login on the CP if you want to. Maybe it saves us time?
Best regards,
Harold

#25

Harold Kuiper

Jan 28, 2020

Comment has been marked private.

#26

BoldMinded (Brian)

Jan 28, 2020

The control panel url you provided doesn’t work, it keeps redirecting.

#27

BoldMinded (Brian)

Jan 28, 2020

I understand that you’re stuck, but I can’t drop my day job to debug this. I’ll take a look when I can, maybe later tonight.

#28

Harold Kuiper

Jan 28, 2020

Comment has been marked private.

#29

BoldMinded (Brian)

Jan 28, 2020

The FTP login you provided also doesn’t work. Please double check all the URLs and credentials to make sure they work (login yourself to verify), then I can take a look at the site.

#30

BoldMinded (Brian)

Jan 28, 2020

Comment has been marked private.

#31

Harold Kuiper

Jan 28, 2020

Comment has been marked private.

#32

BoldMinded (Brian)

Jan 28, 2020

It’s still redirecting and won’t load.

#33

Harold Kuiper

Jan 28, 2020

Comment has been marked private.

#34

BoldMinded (Brian)

Jan 28, 2020

Comment has been marked private.

#35

Harold Kuiper

Jan 28, 2020

Comment has been marked private.

#36

Harold Kuiper

Jan 28, 2020

Comment has been marked private.

#37

Harold Kuiper

Jan 28, 2020

Comment has been marked private.

#38

BoldMinded (Brian)

Jan 28, 2020

I don’t think you fully rolled back your database before trying the upgrade again. None of the exp_publisher_data_field_X tables should exist prior to EE3. This is why you’re getting the error. It’s trying to insert data that already exists. You need to roll back _everything_ to what it was before upgrading Publisher to 3.

#39

Harold Kuiper

Jan 28, 2020

I will go through the whole process again from ee3 > ee5.

#40

Harold Kuiper

Jan 28, 2020

Comment has been marked private.

#41

BoldMinded (Brian)

Jan 28, 2020

What is “the same issue”? The error in comment #21 above?

#42

Harold Kuiper

Jan 28, 2020

Comment has been marked private.

#43

Harold Kuiper

Jan 28, 2020

Comment has been marked private.

#44

BoldMinded (Brian)

Jan 28, 2020

Yeah, her conclusion is similar to mine. You can also try just deleting all of the exp_publisher_data_field_* tables and then trying the upgrade again. However, it sounds like things are in a half upgraded state, so it’s difficult me to support it because I don’t know what has or has not been completed.

#45

Harold Kuiper

Jan 29, 2020

Hi Brian,

We hardcoded deleted all ‘exp_publisher_data_field_’ fields and now for the first time in ee5 it rolled the update.

Thanks. We might get back to you if we encounter anything but for now we can continue.

Best regards,

Harold

#46

BoldMinded (Brian)

Jan 29, 2020

I’m glad it finally upgraded 😊

I’m just going to mention that if there are additional issues that are difficult to debug or sound suspicious and I don’t know the immediate fix for, I may require an clean upgrade from Publisher 2 before I investigate the issue. I don’t want you to have to do that and hopefully it doesn’t come to that, but I feel like I do need to mention it since the upgrade was not cleanly successful the first time.

Login to reply

Contact

For add-on support, please use the Support section. General inquries and pre-sale questions can be sent to support@boldminded.com.