Zach Skaggs

It looks like this is a result of an out of date WordPress version plus an improper check on our end for some new functionality. I’m so sorry and take personal responsibility. Our team is on it now and will be updating ASAP.

This is releasing later today. Please note that this will ONLY work if the user completed the form while logged in…otherwise we have no way to map a submission to a particular user.

Hey, @dugabug!

I am the product owner for Ninja Forms at Saturday Drive. Would you be willing to talk soon about your experiences? Not looking to change your mind at all, I just want to know more about the breakages you’re talking about and experiences with the product, as this experience isn’t typical for most of our users. I want to make sure in the future that we get it right for users like you, though, so understanding your frustrations and pain points are my top priority.

If you are able and willing, please pick a time here to set up a one on one discussion: https://zachskaggs.youcanbook.me/

Thank you so much for your time.

3.2.21 launched just a few moments before your last comment, so you may have been auto updated to the new version quickly after my reply by WPEngine

Version 3.2.21 is now on SVN and should fully resolve this issue for anyone impacted.

Version 3.2.21 is now on SVN and should fully resolve this issue for anyone impacted.

Something broke in WordPress SVN…we’re trying to figure out what went wrong now. The v3.2.20 tag on GitHub WILL work if you need a fix ASAP. https://github.com/wpninjas/ninja-forms/releases

Hey, @idlegamer!

I think there are a few points of confusion here I want to clear up.

First, Ninja Forms is absolutely free, so there is no need to buy the core plugin.

Second, our styling addon makes it super easy to do multi column layouts with a drag and drop interface, but it’s not necessary at all to purchase it style your form or use multi column layouts.

Multi column layouts can be done easily with helper classes you can find here, and the form templates included with Ninja Forms also have examples of these classes in use: https://ninjaforms.com/docs/styling-your-forms/

Please let me know if you need any help with the above functionality, and I hope this information can help change your poor perspective on Ninja Forms! Thank you for your honest feedback.

Hey, @ninjastyler, can you reach out to me here? https://ninjaforms.com/contact/

In your message, tell them Zach asked you to reach out so they’ll send it to me. Thank you!!

The best way to handle this would be to use custom calculations instead of our product fields. Product fields are only intended for the most basic of use cases…though we have ideas for the future to make them viable for more.

You can find our calculations documentation here: https://ninjaforms.com/docs/calculations/

Please note that we only check these forums about once a week, so if you have any more questions and need assistance, please reach out to us at https://ninjaforms.com/contact/ for faster assistance!

Can you reach out to our support team with more data so we can assist? You can reach us directly here: https://ninjaforms.com/contact/

Please note that we only check these forums about once a week, so if you have any more questions and need assistance, please reach out to us at https://ninjaforms.com/contact/ for faster assistance!

I’ll pass this along to our marketing team for consideration in a future blog post! We’re also starting a partnership soon with a company in the WordPress space that works closely with Google Analytics, so stay tuned for that news as well!

I’m sorry you encountered this issue…we did introduce a bug related to help text that was fixed in 3.2.11, and we’ve added precautions to make sure this type of bug won’t be introduced again.

Please note that we only check these forums about once a week, so if you have any more questions and need assistance, please reach out to us at https://ninjaforms.com/contact/ for faster assistance!

Hey, @paulstenning!

I’m Zach, the current product lead for Ninja Forms. I’m the one who personally makes the call about when to ship updates to Ninja Forms.

At a minimum, you will see an update to Ninja Forms 2x per month. We are constantly looking to improve, and making improvements to Ninja Forms for our 1,000,000+ users, and most of them wouldn’t have it any other way.

This month, we released more updates than usual. This is a direct result of contact from the WordPress.com team asking us to make some changes for their VIP platform. There were many changes made, but one change in particular caused a problem for users with help text. If you didn’t use help text, you were not impacted by this issue.

For a very small number of users, though, their forms ceased to render. I made the call to release an off-step release to get those users back up and running. Two days later, we made one more tweak to that release to fix another fringe use case related to help text in the form output.

None of the changes made would cause your site to 500 and/or leave it in maintenance mode, and we have had no such reports from other users.

Can we do better testing? Of course we can! Inevitably, though, bugs will make it into production, especially in an unpredictable, “wild west” environment like WordPress. I, and most of our users, are proud that we have a team that no only updates frequently, but responds quickly to those bugs when they’re introduced into the product.

For you, this is a concern/complaint. It’s valid, and I understand your argument. For most of our users, though, the fact that we’re not afraid to push an update for our impacted users is a huge plus and lets them know that the product is not only updated often, but that we truly care about improving the experience of our users.

Thank you for your feedback. If you have any more questions, or still believe Ninja Forms is causing your site to 500, please feel free to reach out to us here: https://ninjaforms.com/contact/ and we’ll walk you through troubleshooting your site.

It is a shame. This is still true as of January 2017. We learned when we started looking into accessibility that we made some decisions in 3.0 that greatly impeded our ability to provide proper accessibility in Ninja Forms, and while we do have it on our road map to complete, the task has ended up being a much bigger endeavor than we anticipated.

The bottom line is that we’re sorry. We’re aware. This is important to us. We own these mistakes, and we’re in the progress of owning the fix.

Thank you for your feedback…its important and necessary to keep us focused on this goal.