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 hierarchy is lost in case of EE validation error

Status Resolved
Add-on / Version Bloqs 4.0.1
Severity
EE Version 4.1.3

Josh Noble

Apr 11, 2018

Description:

After successfully saving an entry with nested Bloqs structure, upon subsequent save, if there is a validation error triggered by one of the Bloqs’ atoms, the whole existing hierarchy vanishes irrevirsibly. There is nothing extraordinary in the Bloqs themselves - they only have one text field for title.

Screencast: https://drive.google.com/file/d/12CQ-hIzNv-J7rF9k8sNkXTrPckbTe1kJ/view

#1

BoldMinded (Brian)

I see this locally too. The main issue is that there are 2 different methods that display the blocks. One for valid, already saved blocks, and the other for when its trying to display revision data or invalid data, such as this case, and it doesn’t have any of the nesting logic in it. To be honest this could take some time to figure out… maybe a couple weeks.

#2

Josh Noble

That’s very unfortunate since the risk of losing a lot of work is considerable. Is there some workaround that can be used until a fix is provided?

#3

BoldMinded (Brian)

Sorry but if there was a simple workaround I would have already fixed it and sent you a build. I started looking at it last night but it’s not an easy 1 liner fix. A couple methods need to be refactored.

#4

BoldMinded (Brian)

Josh, here is an update. I have it working for the most part, there is just 1 scenario that isn’t working correctly, but I hope to have it figured out this week.

#5

Josh Noble

Great news! Thanks, Brian!

#6

BoldMinded (Brian)

Are you using Publisher? If not then I can send a build for you to test. I’m seeing an edge case where existing blocks are deleted if the Bloqs field is inside of a channel ignored by Publisher, which may be an entirely separate issue.

#7

Josh Noble

No, at the moment we aren’t using Publisher and I don’t believe we will.

#8

BoldMinded (Brian)

Comment has been marked private.

#9

Josh Noble

Hi Brian, At first glance things seem to be working. We’ll test a bit and get back to you, but so far we the original issue doesn’t seem to persist any longer. Thanks!

#10

BoldMinded (Brian)

Comment has been marked private.

#11

Josh Noble

So far everything looks good, Brian. I think we are in a good place with this build. Thank you!

Login to reply