tzshng

Thanks for getting back to me. I’ve reviewed the optimizations you mentioned. While normal loading and reading aren’t major issues, we hit a bottleneck when there are a lot of posts and over 50 forms in the backend. Even with no submissions, new form submissions slow down after we reimport those forms.

When we get to over 5,000 submissions, an underpowered server freezes up with just a 300MB+ database when a visitor submits a form. The issue mainly happens when writing to the database, and the query monitor isn’t much help (or maybe I’m not using it correctly).

I understand that moving to AWS makes the database perform much faster, and submissions are very quick. However, this seems to be an architecture or database design issue that should be addressed fundamentally. Changing the implementation will help Ninja Forms perform faster as well.

Yes, that is the plugin I’m using. But even disabled the plugin isn’t helping the log in the plugin to work correctly.

You can just use the whitelist function. But be careful, most people don’t have a fixed IP address, so if you changed IP address one day, you might not able to login to the website.

Thank you for explaining. However, I find that pasting variables from a txt file, and even editing them in the text box, is more convenient for importing settings where we want to import settings with a slightly different login URL.

The import file method now requires us to edit it in a txt file before we can import it, which increases the friction in importing the setting.

I hope to reconsider removing the text box import method.

Thank you for your prompt response. However, I’ve noticed that even the account activity log and 404 monitoring aren’t working. I don’t believe we can disable the account activity log, correct?

So I believe it boils down to a code conflict.

I’m having the same problem, and I’m convinced I was on 7.4. (as this is set as default on my server).

After checking, the website is using 7.3 for some reason. I can export it without issue once I change it to v7.4.

Here are some of the htaccess code I insert into the custom rules and seems to fix most of the problem I reported earlier.

RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
Header Set Strict-Transport-Security: max-age= 31536000;
Content-Security-Policy: default-src https:

<IfModule mod_headers.c>
Header set X-XSS-Protection “1; mode=block”
Header always append X-Frame-Options SAMEORIGIN
Header set X-Content-Type-Options nosniff
</IfModule>
ServerSignature Off`

Yup, facing the same issue as well. Anybody already found a fix?
I’m using Divi theme.

Facing the same problem as well. It it is from root user. ??

Hey guys, seems like the problem still persist in the latest version. It is quite tedious to login under maintenance mode. ;(

Both options are enable in the plugin. But I still don’t see the field appear.

It seems like Google is showing the exact title you told it to show.
Double check your post title setting. Screen shot and post it here might help others to answer your question.

I’m facing the same problem as well. I thought it is my plugin or wordpress version conflict. It seems like the same problem affect others as well.

awesome! Thanks a lot.

I’m sure I will write about your plugin if I have a chance. I can’t find any better plugin for now.

Well done and thanks for your hard work.