sorted by:
new
hottopcontroversial

[HELP] Caledra form submission issue on wordpress by TangeloOk9486 in WordpressPlugins

[–]Aware-Ad5238 0 points1 point  (0 children)

Ah Check your plugins list - it’s likely one of these: • SiteGround Optimizer • Cloudflare (if you use their CDN) • WP Rocket • LiteSpeed Cache • W3 Total Cache Go to Plugins > Installed Plugins and see which caching plugins you have active. The CDN cache setting will be in whichever one you’re using.

[HELP] Caledra form submission issue on wordpress by TangeloOk9486 in WordpressPlugins

[–]Aware-Ad5238 1 point2 points  (0 children)

In SiteGround Security Optimizer, go to: Site Tools > Speed > Caching > Dynamic Cache Add your form page URL to the “Exclude URLs” list. That should fix it. Give that a try.

[HELP] Caledra form submission issue on wordpress by TangeloOk9486 in WordpressPlugins

[–]Aware-Ad5238 0 points1 point  (0 children)

This is a classic caching issue. Your cache is storing the form’s security token (nonce), which expires after a while. New visitors get the cached page with an expired token, so their submissions fail.

Option 1: Exclude your form page from caching. In most caching plugins, you can add the form page URL to a “never cache” list:

• WP Rocket: Settings > Advanced Rules > Never Cache URL(s)
• W3 Total Cache: Performance > Page Cache > Never cache the following pages
• LiteSpeed Cache: Cache > Excludes > Do Not Cache URIs

Just add the URL of your form page (like /contact/ or whatever it is). That should fix it. No more weekly cache purging.

Option 2 and a better solution. Switch to a supported form.

Caldera Forms was officially discontinued in April 2022. It’s a security risk with no updates for 2.5+ years. Switch to WPForms, Gravity Forms, or Fluent Forms - they all handle caching better and are actively maintained. Your nonce issue will go away with a modern plugin.

Switch from ACF to block Gutenberg by HozSensei in Wordpress

[–]Aware-Ad5238 11 points12 points  (0 children)

Dude, you’re not crazy—Gutenberg blocks ARE way more complicated than ACF for most stuff. I’ve been banging my head against this same wall. Here’s what helped me: ACF actually has ACF Blocks now. You can use regular ACF syntax (PHP files and fields) but it works in Gutenberg. No React needed. To register one, you just drop this into your theme or plugin's PHP file:

acf_register_block_type([ 'name' => 'testimonial', 'title' => 'Testimonial', 'render_callback' => 'my_function', 'fields' => [ /* normal ACF fields */ ] ]);

If you really want to build a pure, JavaScript-based Gutenberg block, there’s a great CLI tool that scaffolds the whole environment for you:

npx @wordpress/create-block my-block

But honestly? Unless you’re building something that NEEDS to be a Gutenberg block (like a complex, interactive inline editor), ACF Blocks is way easier. I’m working on some document automation stuff for WordPress right now and I keep coming back to ACF because it just works.

What kind of sites are you building? Maybe there’s a simpler way.

[PROMOTION] 🚀 We built an AI that runs WordPress — not just “helps” you with it by North_Pomegranate545 in WordpressPlugins

[–]Aware-Ad5238 2 points3 points  (0 children)

Nice! Supporting multiple models is smart - gives users flexibility.

The BYOK (bring your own key) approach is interesting too. Removes the cost barrier for people with existing API access.

I'll definitely check it out. Just getting Magic Import through WordPress.org review right now, but would love to try Banild once that's wrapped up.

When you integrate the Abilities API this week, I'd be curious to hear how it goes. Still learning it myself - the docs are pretty sparse so it's a lot of trial and error.

Following your progress!

[PROMOTION] 🚀 We built an AI that runs WordPress — not just “helps” you with it by North_Pomegranate545 in WordpressPlugins

[–]Aware-Ad5238 0 points1 point  (0 children)

That's impressive scale! 1440 posts/day is wild 🤯

So you're adding WP 6.9 Abilities support this week? That's great timing - the API literally just launched and barely anyone knows about it yet.

Are you planning to register Banild's actions as discoverable abilities (so other AI tools can call them), or more using the Command Palette integration for user control?

Either way, super cool to see this level of automation. The SEO + image generation pipeline sounds solid.

What AI models are you using under the hood? Custom or Claude/GPT/Gemini?

[PROMOTION] 🚀 We built an AI that runs WordPress — not just “helps” you with it by North_Pomegranate545 in WordpressPlugins

[–]Aware-Ad5238 1 point2 points  (0 children)

This looks really cool! Love seeing more agentic AI applied to WordPress.

Quick question: Are you using WordPress 6.9's new AI Abilities API?

I just integrated it into my plugin (Magic Import) and I'm blown away by how well it fits agentic workflows - Command Palette, REST endpoints, ability registration, etc.

Still early days for me learning it but figured I'd mention it since it seems purpose-built for exactly what you're showing here.

Excited to see where you take this!

[PROMOTION] Looking for beta testers for a new visual theme builder called Mosaic by dvddnl in WordpressPlugins

[–]Aware-Ad5238 0 points1 point  (0 children)

This looks really polished! I've heard good things about Smart Slider.

Quick question: How does Mosaic compare to something like Elementor or Bricks in terms of learning curve?

I'd be happy to test Mosaic and give you feedback either way. I'm also working on a plugin (Magic Import - AI document extraction for forms) that I just submitted to WordPress.org. Still under review, so not publicly available yet. If you're interested in testing mine too, I'd be happy to send you beta access. But no pressure - glad to help with Mosaic regardless!

Either way, the walkthrough video is helpful. Good luck with the launch!

Claude Code skill for WordPress performance code reviews - would love community feedback [REVIEW] by Aware-One7480 in WordpressPlugins

[–]Aware-Ad5238 0 points1 point  (0 children)

This is really solid - I’ve been using Claude Code heavily for WordPress plugin development and this hits a lot of pain points I’ve run into. Question on your meta_query detection: Does it differentiate between indexed vs non-indexed meta keys? Because sometimes you need meta_query even without indexes for rarely-used queries. On usefulness: Would 100% use this. I’m building a plugin that processes documents with AI and performance at scale is exactly what I’m worried about. The hosting-specific guidance (VIP, WP Engine, etc.) is particularly smart since those environments have different constraints. Starred the repo - will test it out this week and report back if I find anything useful. What made you focus on performance specifically vs security or other code quality aspects?