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: Exception Caught after reordering bloqs.

Status Resolved
Add-on / Version Bloqs 4.0.19
Severity
EE Version 5.2.1

Sarah Friedlander

Apr 01, 2019

Brian,

I added a few new blocks and atoms today and started seeing this error (see attached image). I don’t get any console issues of any kind, but the issue seems to happen after using drag and drop to reorder blocks, then saving. It’s not template-related (it happens even if the template is empty). The exception says “error ocurred on a nested Bloq field” but we have no nested bloqs anywhere on the site.

We need to fix this in order to deploy a big change to one of the biggest sections of our website (a thousand-entry channel). Right now I can’t test on staging and I don’t want to deploy anything. In case it’s helpful: We migrated from EE3 to EE5 a few months ago.

I’m giving you access to our test server.
Let me know if you have any questions. Thanks in advance.

Best,
Santiago Melluso

#1

BoldMinded (Brian)

Hi, Santiago. Can you please include a screenshot of the Bloqs field in the CP and/or be very specific as to what entry and channel I should look at if I login to your CP?

Thanks.

#2

BoldMinded (Brian)

I also tried logging into your CP and got this error: “Error: You are not authorized to access this page”

Please ensure that the login credentials supplied let me access all of the Bloqs module and channel entry where the issue can be observed.

Thanks.

#3

BoldMinded (Brian)

Also, it would help if you provided a video of the issue as it happens, so I can see exactly what you are doing and replicate it myself.

#4

Sarah Friedlander

Comment has been marked private.

#5

BoldMinded (Brian)

I can’t replicate this locally, so I logged into your CP and took a look at your blog/index template. I didn’t see any {close:*} tags, which are used to determine when a block should be closed, so I think the history is getting messed up, thus causing the error. Check out the docs and update your template and see if it works: https://eebloqs.com/documentation/nesting

If it still doesn’t work and I need to login to the CP again, please create a test template with nothing else in it, just the entries tag and variables necessary to replicate the issue. The blog/index template is incredibly long and too complex for me to debug.

#6

BoldMinded (Brian)

Just checking in to see if it was indeed the template issue?

#7

Sarah Friedlander

Thanks Brian! That worked for us. Closing this one. S

Login to reply