gurra

Hi @aurangajeb,

Thanks for your answer! The Basic Question form is now completed and sent.

Hi @shaylee,

Thanks for your answer. Well, hardly resolved, I don’t know if I understand you correctly, but if I enable “Legacy Submissions” (the box marked) I don’t see the old submissions (those before April/March 2022). If I disable I see all submissions, the old as well, i.e. the opposite to what you say. And in any case, even when I see all the submission, the big problem is that the old submissions can’t be deleted.

It was when I found out that the old submissions couldn’t be deleted I made a try by clicking the button in the settings called “Delete All Ninja Forms-data at uninstalling” (a translation from Swedish so it may not be exact). And furthermore I deleted Ninja Forms completely. But still, when checking the database all the “wp_cf_form tables”, with all the info included were still there, i.e all the old submission messages.

I guess, to solve the problem I start with finding a plugin that may clean the database. Hope it work. If not I contact you on your Ninja support.

By the way, the advantage to enable “Legacy Submissions” is that it will show the trash. Good if I delete new submissions and will empty the trash. Quite as important as the first click to delete.

Only worked partly. Strange. I’ll try again.

I doubt your suggestion will help to find an explanation. As said above (in my second comment) the problem disappears only when I deactivate aiowps. It didn’t help to only disable the security features and firewall rules. So I guess disabling the features and rules one by one should not make any difference, meaning it would show some special feature or rule having an effect on the problem.

I guess the conclusion of this also will be, as partly discussed earlier, that it is nothing wrong with the site as such (all works okey when deactivating aiowps), but the problem is a conflict between the plugins PublishPress Permissions or Theme My login and aiowps. Possibly I could get this conclusion confirmed by deactivating the plugins mentioned, but I rather not want to, because it should make documents public that shouldn’t be (and also I am not sure if all of the settings I have done with these plugins remains when activating them again).

If you think it is important to continue trying to find an explanation because of security reasons, I will continue testing based on your suggestions. But if quite sure no security risk, I think the best is to close this topic.

No. When deactivating aiowps, the issue disappears – i.e. the Profile page can be opened the ordinary way. (It wasn’t enough to disable security features and firewall rules, I had to deactivate.)

Just a thought – maybe the plugins PublishPress Permissions and/or Theme My Login cause the problem (these plugins are only used on the sites with the problem).

Anyway, as partly said, the focus on my question is if the problems to open my Profile page the ordinary way indicates any security risk. If not, there is no reason to put more work on the issue, because of the Profile page can be opened via WP security/user accounts.

Hi,

Yes that is correct.

I am not sure if you missed the point, when you describe where I find the feature. I know where it is, and I use it.

The problem? Not the feature as such. The scan is performed, the mail report is sent. The problem is that my IP provider since some weeks ago stops the mails. See explanation above.

I have found a work around. See above.

Perhaps you may not see the problem as yours, and that may be correct. But probably you will meet this issue again, and to avoid the need to answer future support questions about this problem, it may be an idea that you change how the aiowps plugin creates and sends scan report mails. This is solely a kindly suggestion, aimed to help.

Best regards

…just want to add that that site in general works okay now. Just want to be sure it has as secure protection.