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: Nested Wygwam Issue

Status Resolved
Add-on / Version Bloqs 4.0.3
Severity
EE Version 3.5.15

Mighty Citizen

Jul 09, 2018

 

 

Description: Wygwam works fine in a non-nested block, but once I nest it, the field is no longer clickable. I have a dev site that I’ve attached Super Admin credentials to. I can add FTP credentials if needed.


Detailed steps to reproduce the issue:
1. Create entry in About Pages channel
2. In Modular Content field at the bottom, Create Accordion Section
3. Create Accordion Item
4. Nest Accordion Item under Accordion Section

 

 

 

 

 

 

 

#1

BoldMinded (Brian)

I think I know what the issue is here, but it could take a few days to sort out.

#2

Mighty Citizen

Sounds good - let me know if you need additional info from me

#3

BoldMinded (Brian)

Kristine, I’m not sure I was seeing exactly what you were describing. The field was clickable and I could add text, but the block itself was not responding to drag attempts. It looks like a new error introduced in the last update. Open up the cp.js file in Bloq’s theme folder and find the stripHtml method on line 526. Change it to the following:

function stripHtml(string) {
        if (!string) {
            return '';
        }

        return string.replace(/<\/?[^>]+(>|$)/g, '');
    }

Let me know if that fixes it.

#4

Mighty Citizen

Hmmm that didn’t quite fix it - I can add in the FTP credentials for you (I don’t think it lets me while the ticket status is set to Client Wait)

And let me know if you need any additional info

#5

Mighty Citizen

Added in credentials to the ticket

#6

BoldMinded (Brian)

Comment has been marked private.

#7

Mighty Citizen

Sorry about that - should be working now!

#8

BoldMinded (Brian)

FTP doesn’t appear to work either.

#9

Mighty Citizen

Ah dang typo - should be working now. Sorry about that!

#10

BoldMinded (Brian)

I can’t edit any files.

#11

Mighty Citizen

Sorry about that - we changed server environments and they have restrictions on FTP access and it seems to be a permissions nightmare. I’ll just go ahead and give you master credentials.

#12

Mighty Citizen

Updated!

#13

BoldMinded (Brian)

So, what is the likelihood you’ll upgrade to EE4? 😊 Apparently the sortable JS plugin they’re using is different in EE3 and 4. I built this feature in EE4, but tested in 3, but didn’t notice that the sort events are not firing in EE3, but are in EE4.

#14

BoldMinded (Brian)

If its any consolation I looked at your installed add-ons list and nothing sticks out as “not available for EE4”

#15

Mighty Citizen

We’ll likely upgrade this site to EE 4 in the future, but it wasn’t quite on our agenda yet for this client. I’ll try to brainstorm other ways to structure this content if there isn’t an alternative solution

#16

BoldMinded (Brian)

Yeah, unfortunately I’m not sure what I can do about this other than add a caveat to the EE3 support. I wish I would have caught this sooner b/c now you’re in this situation, so I apologize.

Its just using the jQuery plugins already available in EE, and I spent a lot of time working with 3rd party plugins b/c some of the features seemed better, but ended up just using the native one b/c it worked (I always seemed to get 95% of the way there with the 3rd party libraries then ran into a snag where I just had no choice but to not use it), however, that means that something apparently changed from 3 to 4 :(

#17

BoldMinded (Brian)

Is that a field you can get away with just using a textarea until you upgrade?

#18

Mighty Citizen

We’re spec’ed to have WYSIWYG fields unfortunately. I was able to remove the nesting and instead use the {blocks:next:shortname} and {blocks:prev:shortname} to compare with {blocks:shortname} and use that as a divider for when my items start and stop. It was also working for generating each image in my photo gallery but I have gallery bullets that were being generated in the code that I can’t think of a good way to output yet, so I may just do that on page load with JS. So I thiiiink I can get it to work without nesting

Login to reply