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: Re-ordered blocks don’t save if more than one Bloqs field in channel
| Status | Resolved |
| Add-on / Version | Bloqs 3.1.5 |
| Severity | |
| EE Version | 3.5.11 |
DSite
Aug 30, 2017When I reorder blocks in a Bloqs field in a channel that has more than one Bloqs field, the new order does not save properly.
I’ve done a bunch of testing over a few different installations, and here is the cleanest test:
1. I created a fresh installation of EE 3.5.11 and Bloqs 3.1.5 (with no other add-ons).
2. I created a simple block with just a text field atom.
3. I created a new field group with a single Bloqs field using that simple block.
4. I created a new channel and assigned it the new field group.
5. I created a new entry with three blocks in the Bloqs field. I saved the entry.
6. I reordered the blocks and saved the entry. The new order saved successfully.
7. I added a second Bloqs field to my field group using the same simple text field block.
8. I opened my entry, reordered the blocks and saved the entry. The new order did not save.
Just the presence of a second Bloqs field seems to trigger the bug. I don’t have to actually have data in that field.
Let me know if you need any additional information. Thanks for your help!
BoldMinded (Brian)
In the bloqs/javascript/cp.js file, line 132, change
to
I believe this will fix the issue.
DSite
Thanks for the quick response, Brian!
That fixed it on my simple test install.
Unfortunately, it’s still not saving the order properly on my more complicated client site. So there’s something else going on. Looks like I’ve got another round of troubleshooting to do. I’ll let you know if I find the culprit.
DSite
Or I could just clear my browser cache.
sigh
It’s working everywhere now. Thanks for your help!
BoldMinded (Brian)
I saw the email from your previous comment and was about to ask if you cleared your cache 😊
Glad its working now. Sorry you ran into the issue, but thanks for reporting it!