BoldMinded

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: Problem with database tables

Status Resolved
Add-on / Version Publisher 2.4.0
Severity
EE Version 3.5.4

Marco Malavasi

Apr 06, 2017

Description: I upgraded EE from 2.11.1 to 3.5.4 version. Before that I disabled and uninstalled all add-ons and plugins, Publisher included. After the update I re-installed all add-ons and all worked. Then I installed Publisher 2 and I got this db error. I can’t log in the admin panel anymore.
I tried to restore a db backup after the installation of Publisher but the issue still remain.

 

 

#1

BoldMinded (Brian)

Did you clear your cookies and all caches?

If its a clean install there isn’t any reason for that column not to be added. Did you check the exp_publisher_languages table? If so what columns does it have?

Also, you do realize that uninstalling Publisher deletes the translations?

#2

Marco Malavasi

I tried to clear cookies and caches, but it doesn’t work. In the database I have all tables and translations from the old Publisher installation. In the exp_publisher_language table there’s not the column that he is searching for. The table has these columns: - id - short_name - long_name - language_pack - cat_url_indicator - country - is_default - is_enabled - direction - latitude - longitude
- sites

#3

BoldMinded (Brian)

Look like that column was left out of the update script. Odd that this is just only being noticed by a customer now. Try running this query:

ALTER TABLE `exp_publisher_languages` ADD `short_name_segment` varchar(6) DEFAULT null AFTER `short_name`
#4

Marco Malavasi

Tried to run the query, and it worked! But I had also to add a column named “locale”. Refreshing the page I had another error on two columns from another table: exp_publisher_site_pages. Modified these, refreshed and I got a new error on the table “member”. I think this will happen as long as I’ll update all columns and tables by hand. Seems that it didn’t update the tables in the db during the plugin installation. Now I’ll try to get back to EE2 and re-run all updates, hoping this will work this time.

#5

Marco Malavasi

I read just now this warning in the docs: “You must upgrade to Publisher 1.7.4 by clicking the Run Module Updates button in ExpressionEngine 2 before upgrading to ExpressionEngine 3”. I have 1.6.8 version, but I can’t find the update button in the control panel. How can I get the last version for EE2 in order to update to Publisher2 for EE3?

#6

BoldMinded (Brian)

Comment has been marked private.

#7

Marco Malavasi

Thank you, I have updated the plugin and upgraded EE to 3.5.4 version. It works, but the translations in my database are no longer available. It seems that, with the upgrade, all Publisher’s tables were emptied. Fortunately, before the EE upgrade I exported (with Publisher exporter) a csv file with all translations. Is there a way to import these translations in Publisher2?

#8

BoldMinded (Brian)

The upgrade didn’t remove the translations. You stated in the ticket description that you uninstalled all add-ons, which would have told Publisher to delete the translations. Sorry, but there isn’t an import option. If you have a copy of the database with the translations before the upgrade, then you should probably back up and re-do the whole process without uninstalling Publisher.

#9

Marco Malavasi

If I do not uninstall Publisher before upgrade, it gives me the db error on several table’s column (as I stated in the ticket description and shown in the screenshot). So it seems that there’s no way to upgrade EE and Publisher without losing all translations. Do you have any other suggestion? Thank you

#10

BoldMinded (Brian)

I’m doing an upgrade at this very moment. It appears the best course of action is to try disabling Publisher via its disable setting, or change your $config[‘allow_extensions’] = ‘y’; to ‘n’, run the EE upgrade, then turn extensions back on, then go into the modules page and click Update next to Publisher.

#11

BoldMinded (Brian)

Note you’ll still get that database error, but if you run the query above before starting the upgrade you should be fine.

#12

BoldMinded (Brian)

Comment has been marked private.

#13

BoldMinded (Brian)

You’ll need to start the upgrade process over again and either install Publisher 1.7.5, which is in that zip, or run that query above again before you start the upgrade. I just did a test of upgrading from 2.11.7 to 3.5.4 and everything went smoothly.

#14

Marco Malavasi

I followed your instructions step by step but when I click on the update button near Publisher, in the cp, I get this error:

” Exception Caught

SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name ‘short_name_segment’: ALTER TABLE exp_publisher_languages ADD short_name_segment varchar(6) DEFAULT null AFTER short_name

ee/legacy/database/drivers/mysqli/mysqli_connection.php:122

Stack Trace: hide details

0 ee/legacy/database/drivers/mysqli/mysqli_driver.php(137): CI_DB_mysqli_connection->query(‘ALTER TABLE `ex…’)

1 ee/legacy/database/DB_driver.php(297): CI_DB_mysqli_driver->_execute(‘ALTER TABLE `ex…’)

2 ee/legacy/database/DB_driver.php(203): CI_DB_driver->simple_query(‘ALTER TABLE `ex…’)

3 user/addons/publisher/updates/up_2_00_00.php(33): CI_DB_driver->query(‘ALTER TABLE `ex…’)

4 user/addons/publisher/vendor/litzinger/basee/src/Updater.php(88): Update_2_00_00->doUpdate()

5 user/addons/publisher/upd.publisher.php(578): Basee\Updater->runUpdates()

6 ee/EllisLab/ExpressionEngine/Controller/Addons/Addons.php(560): Publisher_upd->update(‘1.7.5’)

7 [internal function]: EllisLab\ExpressionEngine\Controller\Addons\Addons->update(‘publisher’)

8 ee/EllisLab/ExpressionEngine/Core/Core.php(189): call_user_func_array(Array, Array)

9 ee/EllisLab/ExpressionEngine/Core/Core.php(94): EllisLab\ExpressionEngine\Core\Core->runController(Array)

10 ee/EllisLab/ExpressionEngine/Boot/boot.php(151): EllisLab\ExpressionEngine\Core\Core->run(Object(EllisLab\ExpressionEngine\Core\Request))

11 admin.php(143): require_once(‘…’)

11 admin.php(143): require_once(‘…’)

“

#15

Marco Malavasi

Tried to fix manually the table and got this new error:

” SQLSTATE[42S22]: Column not found: 1054 Unknown column ‘publisher_lang_id’ in ‘exp_publisher_titles’: ALTER TABLE exp_publisher_titles CHANGE COLUMN publisher_lang_id lang_id int(4) DEFAULT null

ee/legacy/database/drivers/mysqli/mysqli_connection.php:122

Stack Trace: hide details

0 ee/legacy/database/drivers/mysqli/mysqli_driver.php(137): CI_DB_mysqli_connection->query(‘ALTER TABLE `ex…’)

1 ee/legacy/database/DB_driver.php(297): CI_DB_mysqli_driver->_execute(‘ALTER TABLE `ex…’)

2 ee/legacy/database/DB_driver.php(203): CI_DB_driver->simple_query(‘ALTER TABLE `ex…’)

3 user/addons/publisher/updates/up_2_00_00.php(13): CI_DB_driver->query(‘ALTER TABLE `ex…’)

4 user/addons/publisher/vendor/litzinger/basee/src/Updater.php(88): Update_2_00_00->doUpdate()

5 user/addons/publisher/upd.publisher.php(578): Basee\Updater->runUpdates()

6 ee/EllisLab/ExpressionEngine/Controller/Addons/Addons.php(560): Publisher_upd->update(‘1.7.5’)

7 [internal function]: EllisLab\ExpressionEngine\Controller\Addons\Addons->update(‘publisher’)

8 ee/EllisLab/ExpressionEngine/Core/Core.php(189): call_user_func_array(Array, Array)

9 ee/EllisLab/ExpressionEngine/Core/Core.php(94): EllisLab\ExpressionEngine\Core\Core->runController(Array)

10 ee/EllisLab/ExpressionEngine/Boot/boot.php(151): EllisLab\ExpressionEngine\Core\Core->run(Object(EllisLab\ExpressionEngine\Core\Request))

11 admin.php(143): require_once(‘…’)

11 admin.php(143): require_once(‘…’)

“

#16

Marco Malavasi

Note that in my database, in the ‘exp_publisher_titles’ table there’s not any ‘publisher_lang_id’ column, but only ‘lang_id’. This is the table structure:

id int(10) unsigned Auto Increment
site_id int(4) unsigned NULL [1]
channel_id int(4) unsigned NULL
author_id int(10) NULL
entry_id int(10) unsigned NULL
lang_id int(4) NULL
status varchar(24) NULL
title varchar(256) NULL
url_title varchar(256) NULL
page_url varchar(256) NULL
hide_in_nav char(1) NULL [n]
template_id int(10) NULL [0]
parent_id int(10) NULL [0]
entry_date int(10) NULL
edit_date big int(14) NULL
edit_by int(4) NULL

#17

BoldMinded (Brian)

Did you run the publisher 1.7.5 updates included in the zip file first? That update adds the short_name_segment column. You can back up and start the upgrade again and run that query manually before running Publisher 2s update or robs clip and run the 1.7.5 updates from EE2 and proceed from there.

#18

Marco Malavasi

Comment has been marked private.

#19

BoldMinded (Brian)

Jumping into a refund bc of this is premature. I will run an upgrade locally again in a few hours and see if I encounter the same issue. We’ll get this correct.

Also, I don’t have a refund policy. See the license agreement link in the footer.

#20

BoldMinded (Brian)

I just upgraded from 2.11.7 with Publisher 1.7.5 (provided in the latest zip file) and upgraded to Publisher 2.4.1 without error. I checked the database tables and it ran the updates correctly. The best I can suggest is to rewind and try the process again. First upgrade to Publisher 1.7.5 in EE2, then continue to the EE3 upgrade process.

#21

Marco Malavasi

Comment has been marked private.

#22

BoldMinded (Brian)

I’m sorry you’re still having troubles, but I’m more confident in the 2.4.1 release that upgrades shouldn’t have issues. I tested several upgrades last week and tested again this morning with the latest build and its working without error for me.

When I go to that admin url I see this:

Error: Unable to load the requested class: publisher_cp_events

Go into the legacy/libraries folder and make sure the Publisher_cp_events.php is capitalized, and not publisher_cp_events.php.

The license policy only referenced EE 2 in the sense of using the add-ons in EE 2. It was written back when EE 1 was still relevant. I’ve updated it to also include EE 3, but even then that line does not reference the refund policy, which is valid for all add-ons and all versions. You’re still welcome to use the license on another project or try the upgrade at another time.

#23

Marco Malavasi

I made the change but it doesn’t work. Still get “Error: Unable to load the requested class: publisher_cp_events”

#24

Marco Malavasi

Brian, I need that the plugin works on THIS site, not on other projects. I purchased the plugin to upgrade my site, followed your instructions, tried various solutions and nothing seems to work. I appreciated your support and I’m sorry for the troubles but I cannot use your plugin at all. I don’t want to debug Publisher, I have no more time to spend on this upgrade. When I buy something that doesn’t work it’s normal that I’m refunded. If you don’t want to, I’m sorry but I have to make a very bad review. I’m sure that you can understand and we can reach an agreement about this. Thank you

#25

BoldMinded (Brian)

Marco, I’m sorry you want to provide a bad review but are unwilling to work through this with me. My responses have been timely and I’m willing to help, but its a two way street. If you would like you can zip up your site and send it to me with the .sql file and I will try to run the upgrade myself locally to see if I can replicate the issue.

Providing returns for software is not like returning a physical item purchased at a store. When you return a physical item you no longer have access to that item. “Returning” software is not the same. You still have the source files and can use it to start a new site, give it to someone else, or put it up online for someone to download for free. I’m not saying you’ll do those things, but that is why it is a common policy to not refund software.

#26

Marco Malavasi

You’re right Brian, excuse me if I was too rude. I understand the point for downloaded software, but if I buy a plugin I expect It works without so many problems. Anyway, I’m very happy if you want to test an upgrade with my site (I wasn’t hoping so much). If you provide me an email address I’ll send you the “hot potato” zip. Thank you

#27

BoldMinded (Brian)

No worries. You can send it to support at boldminded dot com.

#28

BoldMinded (Brian)

Marco, I was able to successfully upgrade your site locally. The issue is that you were still running Publisher 1.6.8 according to the database you sent. Once I upgraded to 1.7.5 it worked fine. I mentioned this as a requirement in comment #13 and #15, as well as the README file that comes in the zip, and mentioned in the docs http://docs.boldminded.com/publisher/installation.

You will get errors about your avatar_path, which the upgrade wizard instructs you how to fix. And I had to truncate the exp_low_search_words table due to duplicate key errors. Other than that, no errors in upgrading Publisher. I’ve sent you a zip file with the upgraded database and site files.

#29

BoldMinded (Brian)

The zip file I sent you includes Publisher 2.4.2, which is also available in your account section for download.

#30

BoldMinded (Brian)

p.s. I think I accidentally included the Publisher Lite files in the WeTransfer zip. Just replace them with the version you can download from your account and you should be good to go.

#31

Marco Malavasi

Hi, I installed your zip file, but Publisher still doesn’t work. The site display {phrase:xxxx} instead of the translations. Publisher is enabled and all settings seems to be ok. I tried to switch off and back on Publisher but nothing has changed. Also, I downloaded the latest version (2.4.2) of Publisher and copied all files in the add-ons folder and themes folder but in the cp it still show the 2.4.0 version. No link and no button to run the upgrade (the same as the 1.7.5 version I sent you). So I think at this time I’m not able to update Publisher. After I copied all files in the right folders, where do I have to click to run the update? Thank you.

#32

Marco Malavasi

Comment has been marked private.

#33

BoldMinded (Brian)

Are you able to provide FTP access to that site so I can debug it? If so edit this ticket and use the fields provided, don’t put the info in a comment.

#34

Marco Malavasi

I edited the ticket with the informations

#35

BoldMinded (Brian)

Weird, it looks like the 2.1 update didn’t run correctly.

Try running this query on your database:

INSERT INTO `exp_extensions` (`class`, `method`, `hook`, `settings`, `priority`, `version`, `enabled`)
VALUES ( 'Publisher_ext', 'core_boot', 'core_boot', '', 1, '2.4.2', 'y');
#36

Marco Malavasi

It works! Thank you. I noticed that in the control panel Publisher still shows an available update, despite the latest version installed. Just to know, for the future upgrades, is enough uploading Publisher’s folders or I have to do something more? Thank you again.

#37

BoldMinded (Brian)

Yeah I’m not sure why its showing that you have an upgrade available. For future updates just replace the old files with the new and click the Run Updates button on the modules page next to Publisher. That upgrade message will hopefully go away with the next upgrade.

#38

Marco Malavasi

Ok, thank you very much! Next time you come to Italy, I’ll offer you a pizza dinner!

#39

Marco Malavasi

Hi, I’ve found a new bug on Publisher. After the update when I try to edit an existing entry, in the title field, it shows the title of another entry. I’ve made a search in the database on the ‘exp_publisher_titles’ table and I saw that record id is correct and also its ‘title’ field. I did not try to save the entry, but I assume that, if I do, it will change the entry title as it is filled by another value. Is this a known bug, or I’m the first? Thank you

#40

Marco Malavasi

Clarification: the ‘title’ field is the only one affected by this bug. All other fields seem to be ok.

#41

BoldMinded (Brian)

Marco, please create a new ticket for this, it shouldn’t be part of an unrelated ticket. Thanks.

Login to reply