Casino Gods no deposit bonus.Claim Your Free 999 Pesos Bonus Today

Resolved Mihal Zasse
(@mihalzasse)

7 years, 3 months ago
Goodnight. @wpwhitesecurity @1uinmko @deanysus

On our website, the same error appeared.
```
A plugin automatically created the following custom post: NULL.
Moved the custom post NULL of type customize_changeset to trash. Post URL was...
```
On WordPress, in the support section of the WP Security Audit Log plugin, I found two topics.
Here are the links to them:
1. https://www.ads-software.com/support/topic/pinpointing-the-plugin/
2. https://www.ads-software.com/support/topic/would-you-tell-me-about-meanings-of-2-message/
However, they do not disclose either the reasons for how to correct this mistake.

When you look for it, it was revealed that it occurs as a result of any changes to the settings of the WPtouch plugin.
Please look and give your opinion. Is not it dangerous, in terms of vulnerability of the web site.

I look forward to hearing from you.
- This topic was modified 7 years, 3 months ago by Mihal Zasse.
The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)

Plugin Author WPWhiteSecurity
(@wpwhitesecurity)

7 years, 3 months ago

Hello @mihalzasse,

Thank you for using our plugin and reporting this issue.

We never got enough details from the users who reported this issue before, so we were unable to solve this. Though from your post, and after doing some more testing it seems that some plugins (such as WPTouch) create / use custom post types to store settings etc, and our plugin is capturing that.

While it is good to see that our plugin is capturing even these subtle things, I understand that such behaviour can generate many alerts and can pollute the audit log. I am currently looking into this with the developers and we are trying different fixes / solutions.

We are trying to see if we are able to determine if a custom post was created to store settings etc, or if it was temporary, so we can better handle this issue. I will keep you posted with any updates we might have.

In the meantime, should you have any further queries please do not hesitate to ask. Thank you for taking the time to report this issue.

Thread Starter Mihal Zasse
(@mihalzasse)

7 years, 3 months ago

Good afternoon… @wpwhitesecurity

Thank you very much for your operativeness. I look forward to hearing from you.

Plugin Author WPWhiteSecurity
(@wpwhitesecurity)

7 years, 2 months ago

Hello @mihalzasse,

We just released version 2.6.8 which has an updated sensor that does not capture the temporary custom posts created by plugins that have a NULL value etc. These are typically created temporarily to save settings etc, hence no need to report them.

Please install the latest update. Thank you very much for reporting this issue and for using our plugin.

Please do not hesitate to ask should you have any further questions.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘A plugin automatically created the following custom post: NULL.’ is closed to new replies.

Tags