Comment has been marked private.

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

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.

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)?

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

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`;

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

Comment has been marked private.

It’s still redirecting and won’t load.

Comment has been marked private.

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.

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.

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.