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: Relationshipfield not storing option

Status Resolved
Add-on / Version Publisher 2.10.7
Severity
EE Version EE 5.2.1

Verve -Webdesign und Grafik

Mar 19, 2019

Hi
Updated EE to newest version 5.2.1 with Publisher 2.10.7
Now I cannot store again an option in a relationshipfield and wondering if it has something to do with publisher.
I already made another relationshipfield for testing with same result.
Thanks
Res

#1

BoldMinded (Brian)

Hi there. Can you provide more detailed information about the issue you’re having? What you described is very vague. Is the Rel field inside of a Grid, Bloqs, or standalone? Are you saving it as a non-default language? Are you saving it in a published or draft state? I need you to describe this to me in as much detail as you can. Provide screenshots or a video if you need to. Thanks.

#2

Verve -Webdesign und Grafik

Comment has been marked private.

#3

BoldMinded (Brian)

Comment has been marked private.

#4

Verve -Webdesign und Grafik

Hi Brian Thanks for the build. But the problem still exists. Made also other settings in the relationshipfield (multi, changed channels etc.) - still the same. Looked also in bugtracker of EE … Any idea? Res

#5

BoldMinded (Brian)

Can you share the link to to the issue in the bug tracker so I know what you’re referring to?

#6

BoldMinded (Brian)

If there is a reported issue with EE, did you try uninstalling Publisher to see if it only happens when Publisher is installed?

#7

Verve -Webdesign und Grafik

Sorry Brain, seems to be a misunderstanding…I mean: I looked to the bugtracker but didn’t found a reported issue

#8

Jef Roode

I have exactly the seem problem. I cannot store the relationship field after updating to EE 5.2.1. and Publisher 2.10.7. After de-installing Publisher everything worked fine, so it is a Publisher issue.

#9

BoldMinded (Brian)

Which did you upgrade first? Or did you do it at the same time? 2.10.7 has been out for awhile, so I’m guessing something in EE changed :/

#10

BoldMinded (Brian)

I’m guessing it had something to do with this commit in EE: https://github.com/ExpressionEngine/ExpressionEngine/commit/bb9b5fdbfcbba8b5f90bdf1c30ace9a4f3cb6a43

Can you two revert those changes in your local install to see if the issue resolves itself? I think it’s probably saving the relationship fine, it’s just not fetching it again when reloading the page to display the Relationship field due to that query change.

#11

Verve -Webdesign und Grafik

I upgraded EE latest (few days ago to 5.2.1).

#12

Jef Roode

I cannot remember exactly which one first, but my guess is that it was Publisher.

#13

BoldMinded (Brian)

If you can manually revert the change shown in that commit and try it with the old code to confirm my suspicion it would help me greatly.

#14

Verve -Webdesign und Grafik

I changed ft.relationship.php like descirbed and this helps. Can store the relfield again.

#15

Jef Roode

Yes! That’s the problem. Can you update Publisher, so it will work with the latest version of EE?

#16

BoldMinded (Brian)

Thanks for testing and confirming that guys. I appreciate it.

I’ll try to update Publisher in the next few days to accommodate the new change and still work with the old change. So for now you can keep your local env to the code changes you made so you can keep working.

#17

BoldMinded (Brian)

I think this is an easy fix. On line 378 of Publisher_relationship_hooks.php, change it from:

if (!empty($relationships) && $grid_field_id === false)

to:

if (!empty($relationships) && !$grid_field_id)

After you do that you should be able to use the latest version of EE and undo the changes you made to the ft.relationship.php file.

#18

Verve -Webdesign und Grafik

Great thx - in what folder can I find the file?

#19

BoldMinded (Brian)

legacy/libraries/hooks, or just search for that file name.

#20

BoldMinded (Brian)

Going to mark this resolved as the fix for this is included in 2.10.8.

Login to reply