Ive also given up on tickets or reporting issues. It’s a waste of time 9/ 10 times. They won’t reply or they paste in something that has nothing to do with what I’ve asked (spent time taking screenshots, writing out a clear and concise report, screen record but then have to compress to upload to submit, gather all the relevant system info. Or my favourite is when they send an unrelated pasted reply then close the ticket immediately. After I’ve waited 10 DAYS for their first reply to my ticket.) Literally only one time a couple years ago I got a support rep that was truly helpful and dedicated to helping me. The rest have been useless. I bet there’s one dedicated person that’s trying to do 10 ppls jobs and pick up everyone else’s slack who are just sitting around and half-a**ing their jobs. Fire the ppl who won’t do their part.

Look at the open issues on github. They wont fix foundational issues. It’s impossible to override a their styles , with specificity commonly at (0,6,2) and trying to parse through the amount of wrappers will drive you mad. I’ve been waiting TWO YEARS for a fix on foundational UI stuff but oh yay I’ve got a floating button??

This is absolutely pathetic , they should be ashamed of how they treat their paying customers. I’m certainly not alone. Every two weeks I see another post on reddit about how terrible elementor support is and how isolated their users are feeling. And even community contributions and pull requesra where professionals try to help and fix their mistakes are not accepted. They don’t want to fix it but they won’t allow anyone else to either.

and don’t get me started on the updates. A new update every 3-4 days that hasn’t been thoroughly tested and breaks thousands if sites? Great job guys. Newbies don’t know to turn off auto-update and that elementor is one of the only plugins that you MUST test in a staging website. Or you’re just inviting breaking changes. What a pile. What happened to integrity and doing right by your users, especially users who are paying a pretty penny for SUPPORT?? should be ashamed of yourselves.

I could go on and on but save yourself the grief and go with Bricks or literally any other builder that will actually help paying users navigate and not subject their spaghetti code onto you.

The site is using the latest version of WordPress and plugin (1.36.2)

php info

PHP SAPI cgi-fcgi

PHP max input variables 1000

PHP 180 time limit

PHP memory limit 1024M

Maximum entry time 60

Maximum file upload size 128M

PHP post max size 512M

Also added to the post that I have tried disconnecting and reconnecting the Hubspot integration several times

2nd Update:
Investigating a little more, I noticed that the information is not sended correctly to Hubspot because”Property values ??were not valid” However, I think I have the custom fields created correctly

3r Update and Close:

Closing Thread I was able to solve it, Necessary was: Create custom fields in hubspot with a single selectable button The fields, both in their private and public values, must be the same as they are in Forminator They must not have “-” or special characters.

Nice plugin and seems to work well!

Just a couple of things we’ve noticed …

1. It’s not clear that the targeting CSS class has to include the dot (so .example-class rather than just example-class). Can you make it so that if the dot is omitted that you automatically add it or vice versa? Because classes in Block Settings by default don’t have dots I would probably choose not to have them in your setting to conform to that precedent.
2. If there’s a Gallery Block below the popup button then the gallery images show above the popup. We have resolved this issue with the following CSS …

.wp-block-makeiteasy-popup {
z-index: 1;
}

Oliver

If I insert my block and change the font-size, the has-small-font-size class always get’s applied to the root element of my block. Allthough I’ve tried the following in the block.json:

"selectors": {
    "root": ".box",
    "spacing": {
      "blockGap": ".box__content"
    },
    "typography": ".box__title"
  }

"selectors": {
    "root": ".box",
    "spacing": {
      "blockGap": ".box__content"
    },
    "typography": {
      "root": ".box__content",
      "fontSize": ".box__title"
    }
  },

According to the docs page, it should work from core 6.3. on. I’m using 6.4 and the Gutenberg 17.5.

If I search the core/Gutenberg code, I can’t find places where those selectors are used in the block-supports apply functions. Could it be, that this is only used for global block styles (= changing the global style of a block via site editor global styles or via theme.json) and not on a block instance level?

If that is the case, it would be great if that is documented. Also a list of all the block supports that support selectors would be great. The block.json schema lists a lot of properties that the doc page does not.

Just started using Forminator and am loving all the options.

I’ve created a form with a green background and am trying to make all the text black/dark grey, but for some reason the Radio and Checkbox text remains white.

I’ve replicated the issue with multiple forms and pages, so assuming my theme is overriding the settings for the form. I searched around trying to find the right css selector to use, but couldn’t find it.

Could you help me out? How would I target the Radio and Checkbox label text with the custom css option?

Thanks for your help!

James

Hoping someone can help me with some @media CSS I’m trying to apply.

First question: If an element has several classes to it like so
<div style="color:#ddd" class="wp-block-genesis-blocks-gb-spacer gb-block-spacer homepage-hero-spacer"><hr style="height:30px"/></div>

When using a selector in CSS, can I just use the “homepage-hero-spacer” selector, or do I need to use all of the classes. So could I do something like:

.homepage-hero-spacer {
    height: 100px !important;
}

or should I be doing this?

.wp-block-genesis-blocks-gb-spacer.gb-block-spacer.homepage-hero-spacer {
    height: 100px !important;
}

I’ve tried both, and neither seems to be changing the height to 100px.

Second question: I’m trying to show the above element only when the screen reaches 420px and above, and hide it otherwise using @media. Is this the correct way to do it?

@media screen and (min-width: 0px) and (max-width: 420px) {
    .homepage-hero-spacer { 
	display: none !important; 
	}  /* do not show it on small screens */
}

@media screen and (min-width: 421px) and (max-width: 1200px) {
    .homepage-hero-spacer { 
	display: block !important; 
	}   /* show it elsewhere */
}

Without the previous selector portion working, I can’t really test this @ media CSS, so I’m at a bit of a standstill. Any help would be greatly appreciated.
TIA!