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: Publisher not working, white page/undefined offset & not saving

Status	Resolved
Add-on / Version	Publisher Lite 2.6.0
Severity
EE Version	3.5.10

KeesTM

Jul 10, 2017

Description:
When I installed Publisher 2.5.2 it gave errors and did not save my entries. When 2.6.0 came out, I installed it so I could try if the problem was solved in the new Publisher, but it wasn’t. I got an error: Undefined Offset. And for some reason I just get a white page now. So I can’t see what is going wrong here! It happens when there is a grid with images in the entry!

Detailed steps to reproduce the issue:
1. Install EE3.5.10
2. Install Publisher Lite 2.6.0
3. Try to save an entry with a grid/grid with image in it.

BoldMinded (Brian)

If you’re getting an undefined offset error, please share the error message. I can’t help if I don’t know what is happening.

Are you getting a white screen when attempting to save the entry? If so I also need an error message, please refer to https://gist.github.com/litzinger/5598641

BoldMinded (Brian)

Are you performing this action after the failed upgrade reported in the other ticket? https://boldminded.com/support/ticket/1486

BoldMinded (Brian)

Also what does “grid/grid” mean? Can you take a screenshot or quick video of the action you’re taking to cause the error?

Est Digital

I tried to reinstall a few minutes ago, it took about 3 minutes then I got a 500 Internal server error. it says its installed.
I try to edit an entry:

SQLSTATE[42S02]: Base table or view not found: 1146 Table 'dev_opmeer.exp_publisher_relationships' doesn't exist:
SELECT `child_id`, `order` FROM (`exp_publisher_relationships`) WHERE publisher_status = "draft" AND publisher_lang_id = 1 AND `parent_id` = 11 AND `field_id` = 26

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

I meant to say that I have the error with a grid, and with a grid where I can put images in.

And now edit page is completely screwed up, it does not load any CSS.

Est Digital

Comment has been marked private.

BoldMinded (Brian)

What do you mean updating? Updating to a newer version of Publisher, or updating EE 2 to EE 3 and also updating add-ons? When updating from EE2 to EE3 you should disable all extensions via the allow_extensions config item. Once EE is updated, re-enable extensions, then run Publisher’s upgrade.

The fact that the exp_publisher_relationships table doesn’t exist is a little concerning, and certainly a new issue that I haven’t seen before. Is there a stack trace with that error message?

Est Digital

This was not an update from EE2 to EE3. We have just built a site that is on EE3.5.10 and the client wanted to have publisher in it. So I installed 2.5.2, but that gave error’s and did not work well, so I upgraded tot Publisher 2.6.0 but now we have this problem. I will check for it!

BoldMinded (Brian)

What version of PHP and MySQL are you using?

Est Digital

PHP 7.0.15 & MySQL 5.5.49

#10

Est Digital

Comment has been marked private.

#11

BoldMinded (Brian)

I have never seen this issue before, where a table like this isn’t created during the install. I just un-installed and re-installed 4 times and it works fine. You’ll need to do some debugging. In the FieldHandler.php file step debug or add var_dump($files) the line after the getFiles() call to see if the Relationship file is correctly found.

https://www.dropbox.com/s/9jwerq9k6yfdzlm/Screenshot 2017-07-12 06.36.46.png?dl=0

If it is, then see if the install() method in RelationshipType.php is getting called during the install.

https://www.dropbox.com/s/cwog7xkf163n3ee/Screenshot 2017-07-12 06.38.54.png?dl=0

#12

BoldMinded (Brian)

Comment has been marked private.

#13

Est Digital

Comment has been marked private.

#14

BoldMinded (Brian)

If you’re getting a white screen you need to use the debugging script I posted in the 1st comment to reveal a useful error message, otherwise we don’t know where to look.

Regarding the latest error messages you’re getting, those aren’t coming from Publisher, those are EE’s file field errors. You’re reporting multiple different issues, seemingly unrelated, and that no one else is reporting, which leads me to believe something else is the issue here, not necessarily Publisher.

Have you tried replicating Publisher install on a clean EE site, with no other add-ons? Does the exp_publisher_relationships table get created when you do a clean install?

Have you tried disabling add-ons 1 at a time until the errors go away?

The file field errors you just posted, if you un-install Publisher do those errors go away?

Can you provide CP access to this site with direction on exactly what channels and entries I can edit to see the issue?

#15

Est Digital

I just did a new EE3.5.10 install, completely clear, just installed it and nothing else. I tried to install Publisher, but it again gave an “500 Internal server error”.

So I created a channel with a fieldgroup with these fieldtypes: Grid(Text, Rich Text, File, Date),file, text.

And gues what?

Notice

Undefined offset: 1

ee/EllisLab/Addons/file/ft.file.php, line 102 show details

Severity: E_NOTICE
Notice

Undefined offset: 2

ee/EllisLab/Addons/file/ft.file.php, line 102 show details

Severity: E_NOTICE
Notice

Undefined offset: 3

ee/EllisLab/Addons/file/ft.file.php, line 102 show details

Severity: E_NOTICE
Warning

Cannot modify header information - headers already sent by (output started at ee/legacy/core/Exceptions.php:119)

ee/legacy/core/Input.php, line 249 show details

Severity: E_WARNING
Warning

Cannot modify header information - headers already sent by (output started at ee/legacy/core/Exceptions.php:119)

ee/legacy/core/Input.php, line 249 show details

Severity: E_WARNING
Warning

Cannot modify header information - headers already sent by (output started at ee/legacy/core/Exceptions.php:119)

ee/legacy/libraries/Functions.php, line 440 show details

Severity: E_WARNING

Publisher seems to be incompatible with EE3.5.10. As it was a clean install, with only Publisher in it, no content, just 1 entry, 1 image and it still does not work.

What could be the problem here?

#16

BoldMinded (Brian)

Thank you for trying the clean install. As for the 500 error you _have_to use the script I mentioned in the first comment to reveal the error when you are installing. We have no idea what the error is so I can’t fix it, the script should reveal the error.

#17

BoldMinded (Brian)

I feel you get the 500 error when installing add the debug code to your admin.php and index.php files.

#18

Est Digital

Comment has been marked private.

#19

BoldMinded (Brian)

Ok, try this fix.

In legacy/libraries/hooks/Publisher_grid_hooks.php just remove this code. Let me know if you notice any other issues saving with Grid. I did some tests and it appears to be working fine for me.

https://www.dropbox.com/s/74qe6gquzm5ukkm/Screenshot 2017-07-13 20.02.31.png?dl=0

#20

Est Digital

I got it working after a lot of trouble. There seemed to be a few problems!

Problem 1: White page -> seems my frontend showed the right template while my structure template was pointing to an empty template (How is this even possible?!) Problem 2: Internal Server Error 500 -> MAMP Pro seems to have problems with the long install duration of Publisher, this was caused by FastCGI Problem 3: Database error V1 -> Because of the internal server error, during the install, the database was not fully created. Problem 4: Database error V2 -> It seems that during the internal server errors, when you uninstall Publisher, the database tables of Publisher were not removed. That caused some errors Problem 5: Grid -> This was solved by your fix.

So I got it working, at last. I want to thank you for your support!

I still find it a little bit slow(10-15 seconds load time for a preview on a simple entry with a small grid, in a website with only 30 entries) but that is not important and no real problem.

#21

BoldMinded (Brian)

Glad you got the server stuff figured out.

I agree the load times are not ideal. Its on my radar to take another look at soon to see what I can do about it.