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: Bloqs with 2 relationships not saving in non default language. Using Publisher 2.7.5

Status Resolved
Add-on / Version Bloqs 3.3.4
Severity
EE Version 3.5.12

Kevin Chatel

Feb 15, 2018

Issue:
Entry in non default language saves with no error, but bloq elements with 2 relationships are not saving the values selected. After saving and reload, openning the bloq element shows no entries selected.

In the Database we clearly see the right values/entries selected, however nothing shows in the entry in the bloq element nor on the page in that language.

This issue only seems to be an issue when there are relationship fields in the bloq.

#1

Kevin Chatel

Seems to only happens on a bloq that has more than 1 relationship field. if that helps you out at all.

#2

BoldMinded (Brian)

Bloqs with multiple single relationship fields in the same block in non-default language do not display relationships. Persistent Relationships is turned on.

#3

Kevin Chatel

  • Persistent Relationships on or off
  • On can’t select anything but doesn’t show in template.
  • Off can select but doesn’t save on a bloqs with more than 1 relationship field.
  • In my case the relationships are pulling both from the same channel.
#4

BoldMinded (Brian)

Kevin, just an update on this. I haven’t forgotten about it. I’ll hope to get to it in the next few days.

#5

Kevin Chatel

Comment has been marked private.

#6

BoldMinded (Brian)

Comment has been marked private.

#7

Kevin Chatel

Thx Brian I’m traveling and wont be able to test this build out until next week. Please don’t close the ticket just yet.

#8

BoldMinded (Brian)

Sounds fine. I’m going to release this version today anyway b/c its long overdue.

#9

BoldMinded (Brian)

Closing this ticket b/c I’m pretty sure the 2.7.6 build fixes the issue.

Login to reply