dugost

Thanks for info and that hook. I’ve adjusted the popover event description length but will look to CSS for adjusting the length of the event list block description.

Looking forward to seeing events using excepts that can hopefully preserve HTML. Cheers!

That updated code did the trick, thanks! The image optimization plugin I’m using wasn’t preventing higher quality images from being displayed. It applies srcset wherever it can and outputs webp when possible. It just can’t tackle responsive backgrounds so I appreciate you passing along the recommendation. Cheers!

@kona After running a plugin conflict test, I’ve determined that there’s a conflict with Super Page Cache. Bulk Optimization will run when it’s deactivated. So you were spot on with the Cloudflare angle.

I had hoped adding /wp-admin/options-general.php/?page=rio_general-wbcr_image_optimizer to SPC’s “Prevent the following URIs to be cached” list and purging the cache would help but no such luck.

Perhaps a different setting can be changed in SPC in order to keep it active and avoid the error RIO. For now, I’ll have deactivate SPC, run the optimization and then reactivate it.

Can the developer please look into this? Only with SPC active am I still getting the Uncaught TypeError: Class constructor xn cannot be invoked without 'new' error in Console.

Thank you for that! I’ll pass this along to my programmer to possibly customize.

Edit: With your info about the filter, I was able to search for it and find this post with a function that solves the problem. Passing it along it case it helps others. Thank you again!

• This reply was modified 3 years, 3 months ago by dugost. Reason: New info, helpful link

Ok, the page containing the 2 forms is using the original form and its duplicate (not an imported one). I placed the code above into a Code Snippet since I already had that plugin installed. After activating it, the Uncaught TypeError: FUI.select is not a function error is gone. As is the problem with the second, duplicated form’s multi-select not adding highlights onClick.

When I disable that snippet, the error and the multi-select highlighting issue return.

I hope that helps. I have no idea why it exists on a staging site on the same server as the production site with all of the same versions but, hey, web development, right? 🙄

I right-clicked the page area containing the 2 forms and within the forms themselves, the multi-selects, etc. but didn’t get any sort of visible error. In the Inspector’s Console, the only errors I see are:

Uncaught TypeError: FUI.select is not a function
    at HTMLSpanElement.<anonymous> (front.multi.min.js?ver=1.14.11:1)
    at Function.each (jquery.js?ver=1.12.4-wp:2)
    at n.fn.init.each (jquery.js?ver=1.12.4-wp:2)
    at e.init_fui (front.multi.min.js?ver=1.14.11:1)
    at e.init_custom_form (front.multi.min.js?ver=1.14.11:1)
    at HTMLFormElement.<anonymous> (front.multi.min.js?ver=1.14.11:1)
    at Function.each (jquery.js?ver=1.12.4-wp:2)
    at n.fn.init.each (jquery.js?ver=1.12.4-wp:2)
    at e.init (front.multi.min.js?ver=1.14.11:1)
    at new e (front.multi.min.js?ver=1.14.11:1)

And 3 verbose errors.

jQuery.js:
[Violation] 'DOMContentLoaded' handler took 3071ms

Other:

[Violation] Forced reflow while executing JavaScript took 120ms
[Violation] Forced reflow while executing JavaScript took 47ms

Please let me know if I’m not checking for errors correctly, though.

As for your other note, I’m glad that issue will be addressed in the next version but your instructions describe a process I’ve already tried.

With the original form, I did initially use Forminator > Form > Duplicate. The duplicate only had a title change and some edits to some field content. I placed it and its duplicate on the same page, that’s when I first noticed the multi-select issue. So I then imported the original “New Members” form’s code with the modified IDs to use as the alternate “Current Members” form. The problem persisted.

As I mentioned in my further testing, I created a different form with yes/no radios to display a conditional select like I have in my member form. I then duplicated it and placed it on the same page. The problem didn’t appear for those test forms so it appears to be isolated to the originals I created.

I didn’t get far enough along with my project since my last post but if I can follow up with a live link today I will. Cheers.

• This reply was modified 4 years, 11 months ago by dugost.

Sorry for being unclear. My duplicated form’s fields had the same IDs as the original. I mistakenly assumed these led to a conflict affecting the duplicate’s multi-select. That’s why I asked about editing the import code to assign unique IDs. But, as you say, “Duplicate” avoids conflicting IDs.

Unfortunately, I have no public link to share right now. If I can move it to a production site today I’ll share the link. For now, I’m testing options to help eliminate culprits.

With the original form (“New Members”) and its duplicate (“Current Members” with no edited import code), I’ve moved both out of the tabs into the regular page layout. I wanted to make sure the tabs I was using weren’t the issue.

In this screenshot, you can see the first form highlights my selections in blue but the second still won’t. There’s no visible interaction other than a grey hover state. Selections are registered because aria-invalid is toggled on click and other conditions are being triggered. It’s just that no blue highlight appears to highlight them.

That page is built with WPBakery, though, so I added both forms to a different page using Gutenberg blocks. I also switched the order of the forms.

In this screenshot, you can see the issue continues to affect the second form but this time it’s the original (“New Members”). So it’s not a problem isolated to the duplicated form. The page order of the forms is relevant to the problem. When swapping them back to New then Current, the problem affects the second form regardless.

In case it matters, the multi-selects appear conditionally based on the radio selections above them. Also, by leaving the first form untouched, the issue persists even if selections are made in the second form only.

Using version 1.14.11 with WordPress 5.5.2.

Does this shed light on anything? Can I try anything else?

Ok, I’ve posted the form export but this won’t have the comment in the CSS.

I believe the first version saved without any problems and included this:

.forminator-description-password {font-size: 21px;} /* some comment */

Later when I had to go back and edit the form’s settings and got the error, I removed that comment from the CSS and it saved just fine.

• This reply was modified 4 years, 11 months ago by dugost.