krmoorhouse
Forum Replies Created
-
No, front-end.js should absolutely be running, but almond.js should not.
Could you link us to the page where you saw almond.js loading?We’ll have to take a look at the issue for mobile devices, but just for a quick reference, you’ve referenced CPU time. Is that also the page loading time, or is the CPU just continuing to run after the Form is rendered?
Forum: Plugins
In reply to: [Ninja Forms - The Contact Form Builder That Grows With You] The old problemHey sjsakib,
Without seeing the actual settings on your Form, I can’t say for sure, what’s going on. However, there are some basic steps you can take to troubleshoot the issue.
1. Disable all other plugins on your installation and switch to a default theme, such as twentysixteen. If the Form sends email after that, one of your other plugins or your theme is causing the issue, and you can determine which by enabling them one at a time and testing the Form after each one.
2. If that doesn’t correct the problem, please consult our documentation to confirm that everything is setup properly. (https://ninjaforms.com/docs/troubleshooting-email-problems/)
3. Once you’ve confirmed that everything is configured properly, and assuming the email is still not fixed, try creating a new Email Action (not duplicating it), and fill it out with the information with the old Email Action. Then, disable the old action and enable the new one.
If none of these steps resolve the issue, please contact us at https://ninjaforms.com/contact/ for further troubleshooting.
Hey programmin,
No ids should be changed on upgrade. If that was the case, something didn’t process correctly.
If your ids changed and disconnected your Form from its data somehow, you can roll back to the 2.9 codebase through the Ninja Forms settings menu.
Forms->Settings->Advanced Settings->Rollback
All 2.9 data should be restored to how it was. However, any changes made since upgrading to the 3.0 codebase will be lost.
In cases where the upgrade doesn’t process correctly, we suggest rolling back and re-attempting the upgrade with all other plugins disabled and your theme set to a default, such as twentysixteen. If the upgrade is still unsuccessful, please submit a support ticket through our website, which will allow us to do more in-depth troubleshooting.
Hey xcept,
The intent of the {calc:calcname:2} merge tag was to be a bandaid for a bigger development issue, which we have resolved in an upcoming version of Ninja Forms. I would suspect that the merge tag isn’t properly correcting your decimal places because your decimal separator is a comma instead of a period, which the original fix probably wasn’t built to properly handle. That is something that our upcoming release also resolves, but it should allow you to be more specific with how many decimals you want to round to.
Could you provide us with a link to the Form in question?
almond.js shouldn’t be loading at all on the front end. So, we’d like to see the Form to get a better idea of what’s going on.