krmoorhouse
Forum Replies Created
-
Following up on this topic.
The request referenced here is an asynchronous call, which is specifically initialized after the page has already loaded. The only thing it delays on the page is the loading of the associated Ninja Form.
That said, our development team is looking into alternative solutions to making this request, if for no other reason than to avoid the perception that we’re delaying page load.
Hey @daymobrew,
The files you’re referencing are required update files that manage upgrading our database tables. In order to accurately track which of these upgrades have already run, we’re incrementing the version as they’re stepped through in the update process.
So, this version number is for internal tracking, and it shouldn’t mean anything to anyone outside of our development team at this point in time.
Hopefully, this answers your question.
-KR
Hey @educationguideonline ,
This functionality is required for form submission. So, there isn’t a way to disable it. The code needs to run on any page where a Ninja Form exists. As it appears you are including an email subscription form in the footer of your WordPress site, this code will execute on every page where that footer exists.
That said, while the call appears long at first glance, the only thing the AJAX call delays is the display of the Ninja Form. Any other content on the page is not blocked by the call.
Looking through the network waterfall for your page, I can see that this specific call isn’t even made until 2.3 seconds into page load. So, if your issue is the load time of the overall page, I would suggest looking further up the waterfall for what might be slowing it down.
From a glance, it looks like reCaptcha is taking quite some time to load, but the main load time is on the site itself, which indicates your theme is probably where the bulk of your load time is coming from.
Thank you very much for pointing this out to us. We’ve released a new version of Ninja Forms (3.3.1), which should resolve the issue for any future submissions.
Unfortunately, pre-existing records created via the new action cannot be repaired. They will need to be resubmitted to get proper data into the data export tool.
-KR
We’ve released a new version of Ninja Forms (3.3.1), which should resolve the issue. However, as stated by @pixeldinamico you will need to roll back to a previously working version of our plugin to download the new update.
(Alternatively, you could uninstall the plugin and download a new copy from the repo.)
We apologize for any inconvenience caused by the faulty code in our latest version release.
-KR
- This reply was modified 6 years, 10 months ago by krmoorhouse.
Thank you for reporting this. Our development team is working on a fix for this right now.
-KR
Thank you for reporting this. Our development team is working on a fix for this right now.
For the purpose of keeping the issue confined to a single thread, I’m marking this topic as resolved. Please look for follow up in the thread below.
-KR
Hey,
Unfortunately, there isn’t currently a feature to do this within the plugin. You would need to make some database modifications to correct the submission IDs.
Aside from the _seq_num meta_key on the postmeta table for each submission, there is also a _seq_num key on the nf3_form_meta table for each form. This value determines what the next submission will be numbered as. So, if you regroup the submissions, you’ll probably want to set this value to 1 higher than the new most recent submission. That way, it doesn’t leave a huge gap between your reconstructed group and any new submissions.
-KR
Hey,
Do you need to re-order them, or just re-sort them by date created (minus your test submissions)?
-KR
Hey,
Most often, when the Form Builder doesn’t load, it’s because another plugin is interfering with our code. Can we get you to disable all plugins that aren’t Ninja Forms and switch to a default theme, such as Twentysixteen to see if that resolves the issue? If that’s the case, please re-enable your theme and plugins one at a time, checking for the issue after each one. When it returns, you’ll know that the last thing you activated was the cause of the problem.
If this doesn’t resolve the problem, could we get you to open up the console in your browser and see if there are any errors present? If so, could you send us a screen capture of that error?
Hey,
At the end of the day, improper use of autop is what causes the issue. However, we’ve tried to ensure that our plugin prevents that from breaking it.
-KR
Closing due to lack of activity.
Hey,
A File Upload Field cannot currently be used to trigger Conditional Logic. However, you can make the File Upload Field a “Required” Field, which prevents the Form from Submitting unless a file has been uploaded.
-KR