Reed Sutton

Can anyone confirm this is resolved?

Bump

Same issue here. Cloudflare says its a plugin issue.

Also being blocked from logging into wordpress even though Turnstile says passed as valid.

Okay so I didn’t have that enabled. I just did and it didn’t resolve the issue.

What did resolve the issue is using the full shortcode.

So [pods name=”bank_account” id=”35941″ field=”standard_interest_rate”] instead of [pods field=”standard_interest_rate”].

However I would think that wouldn’t be required since the ID is specified already in the parent shortcode. Not sure if this is intended behavior or not of Pods but at least I was able to get it to work with the longer shortcode.

So I already manage my Pods data by importing a published google sheet (csv) into wordpress using WP All Import.

So I guess my question is more around, with the native behavior of Pods, will a cell with multiple values comma separated, properly import into a simple relationship field that has options corresponding to those values?

This plugin was determined to be causing my site to make 15 second requests and become rampant with downtimes and http errors. We hired a new relic expert who narrowed the issue down to Content Control. You guys have BAD BAD code.

This is possible using the conditional logic.

Only handling a page at a time would actually be perfectly useful functionality for our purposes.

FYI – this is the reply I received from my theme support and it resolved the issue:

for the solution, try adding this CSS: picture { display: block; }

For the problem.

When you set the size of a core Image Block, it adds CSS Class and Styles Attributes to the <img> HTML.

https://app.screencast.com/JLa14iFev9Wlc

And WP adds CSS specifically for an img eg. .wp-block-image img { box-sizing: border-box; height: auto; max-width: 100%; vertical-align: bottom; }

The Theme itself does not control the inline style or that CSS.

When that plugin converts the image, it wraps the img inside a <picture> tag and it MOVES the CSS Class and Style Attributes from the img tag to the <picture> tag. See here:

https://app.screencast.com/tKNZGDHJwDFOA

And that is where the problem lies.

A <picture> elements main purpose is a wrapper to provide source information, it itself is an inline element that does not have any width and height attributes and therefore it does not occupy any real space on the page.

And therefore that inline style which sets the width will not work there.

The CSS i provided up top changes the picture display property to a block so it can accept the width style.

The ideal solution would be that the Plugin does NOT move the inline style from the img tag and that way the core Image Block would work as expected.

Awesome thank you.

Thanks for this, I am not sure it would help my specific case as I need the four digits to be reflected on the backend in the field value.

Thank you figured out the issue.

Some data to back up my statement:

• GeneratePress has 600,000 installations, but GenerateBlocks has only 100,000 installations even though GeneratePress pushes their own Blocks plugin.
• Kadence WP has only 200,000 installations, yet Kadence Blocks has 300,000 installations.

People not tied to either ecosystem are vastly choosing Kadence Blocks over GenerateBlocks.

• This reply was modified 1 year, 3 months ago by Reed Sutton.

I don’t really see what is illogical about it. I would like to stay within the Generate ecosystem, as I like the GeneratePress theme and use it with several sites. So ideally would just use GenerateBlocks to ensure compatibility. But having trouble justifying it given the other Gutenberg block plugins are offering more for less.

If I wasn’t using the GeneratePress theme, GenerateBlocks wouldn’t get a second look, as its not even top 5 in the category. But it seems GenerateBlocks is taking advantage of its existing GeneratePress user base who will pay above market to stay within the ecosystem.

So was just wondering if there was any acknowledgement of this or no plan to discontinue offering an inferior product at an overpriced price point.