Caldera Forms has grown thanks to its amazing users, and starting today, we are offering an easier way for users and developers to pay for the form builder through pricing bundles.
Yesterday we announced that we are consolidating CalderaWP, Ingot and our WordPress training into one company, Caldera Labs. We are celebrate this new unity in the most sensible way possible: an Ingot for Caldera Forms add-on.
Earlier today I was informed of a security issue in Caldera Forms, which they have classified to be of medium severity, which has now been fixed.
It is not always required to use an SSL certificate for your WordPress site, with the risks being serious, and the rewards of using HTTPS being what they are, you really should just do it to protect your data, reputation and SEO.
The more dynamic and AJAX driven a site is the harder it is to see errors, even with WP_DEBUG enabled. In this post I’m going to show you how to use the debug logging features in WordPress to record and detect errors that might not otherwise be visible to you.
The new Caldera Forms adds better file upload fields, form in modals and advanced usage tracking. It is available today!
We have added improved conditional logic for Stripe payments, API updates for PayPal. We also want to share a quick preview of Caldera Forms 1.3.5.
After a month spent improving the performance & reliability of Caldera Forms, we have 2 new features, better performance, many bug fixes and add-on updates.
What did we update today? We updated all the things! Ok, well, not all the things, but we did put out bug fix releases for Caldera Forms and 2 add-ons.
The first Caldera Forms update of 2016 — Caldera Forms 1.3.2 is now here. It’s got no shiny new features, but we’ve put a lot of effort into improving the reliability of form submissions via AJAX and other “under the hood” improvements.