Publisher is EE6 compatible, but it does not support the Fluid field. 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: Some bloqs don’t expand to show content. Throws .js error

Status Resolved
Add-on / Version Bloqs 4.9.1
Severity
EE Version 5.4.2

Paul Larson

Oct 15, 2021

The .JS error is this:

TypeError: settings.child_of.map is not a function. (In ‘settings.child_of.map(Number)’, ‘settings.child_of.map’ is undefined)

GIF below shows bloqs that work, followed by several that don’t.

https://www.dropbox.com/s/5kk8w0hxkuqejtd/2021-10-15_14-19-40%20%281%29.gif?dl=0

#1

BoldMinded (Brian)

Oct 20, 2021

Paul, can you include screenshots of all the settings pages of every block that is appearing in an entry when the issue occurs? This sounds like an issue with the settings, so I need to see what is going.

#2

Paul Larson

Oct 20, 2021

Comment has been marked private.

#3

BoldMinded (Brian)

Oct 20, 2021

Wait, you get that error on the field settings page?

Also, any chance you plan on updating this site to EE 6 soon? As I mentioned in the other ticket I technically don’t support 5 anymore.

#4

Paul Larson

Oct 20, 2021

I have two tickets open with you. =) I think on the other ticket I get the error on the Field settings page.

This one I think is just the .js error when viewing an entry.

#5

BoldMinded (Brian)

Oct 20, 2021

Not sure those are the screenshots I need.These are screenshots of the fields, I need screenshots of the bloq setting/definition page for each bloq that appears on an entry when the error occurs. The error is coming from the nesting settings, so I need to know what the nesting settings are. The first gif in the original report doesn’t tell me anything about the issue. Can you also include the line number that the JS error happened on?

#6

Paul Larson

Oct 21, 2021

Comment has been marked private.

#7

BoldMinded (Brian)

Oct 22, 2021

Paul, I closed the other ticket, thus it deleted the CP login info :( Can you edit and add the CP logins back to this ticket? Sorry about that.

#8

Paul Larson

Oct 22, 2021

Done! Need ssh again too?

#9

BoldMinded (Brian)

Oct 22, 2021

Appears to be fixed now. For some reason the child_of setting, the one where you pick the parents, saved it as an object, not an array. I disabled all the nesting rules for block definition #25, saved it, then re-selected the rules and re-saved it, and it appears to have saved correctly this time without errors.

#10

Paul Larson

Oct 22, 2021

Thanks! What steps do I take to apply the fix on production?

#11

BoldMinded (Brian)

Oct 22, 2021

Do what I did in comment #9.

#12

Paul Larson

Nov 04, 2021

Comment has been marked private.

#13

BoldMinded (Brian)

Nov 04, 2021

Shouldn’t need an update because I was able to fix it in your dev environment without any new add-on files. Maybe another block on that page is also exhibiting similar behavior and needs the same “reset” done to its settings?

Somehow one of the settings saved as a JSON object,”{key: value}” as opposed to an array “[key => value]”, and I have no idea how that happened b/c it should certainly be an array. Resaving the settings properly set the child_of setting back to an array instead of a JSON object.

#14

Paul Larson

Nov 04, 2021

I think we are all good, thanks! Did another pass on production and found the gremlin you mentioned.

Login to reply