Cannot add images to posts

Hi,

By default, the administrator is whitelisted and should never be blocked.
Could you check if that option has been disabled ? Go to “NinjaFirewall > Firewall Policies”, scroll down to the bottom of the page and you will see the “Do not block WordPress administrator (must be logged in)” which should be set to “Yes, do not block the Administrator”.

Otherwise, you can disable cookies sanitizing: “NinjaFirewall > Firewall Policies > Cookies > Sanitise cookies”, set this option to “No” and save the changes.

Hello,

“Do not block WordPress administrator” was set to Yes

Under NinjaFirewall > Firewall Policies > Cookies > Sanitise cookies”
I changed to No and saved the changes.

Myself (administrator) and the editors still cannot add an image to a post.

Hi,

Did you check your firewall log to see if there was anything ? The firewall will always write any action to its log.
The “cookies sanitizing” was not the problem.

The admin is always whitelisted, but not the publisher.
You can go to the Firewall Policies menu, then in the “Block direct access to any PHP file located in one of these directories” section, uncheck the “/wp-includes/*” list of files because it could prevent plublishers from using the TinyMCE WYSIWYG editor (there is a warning about this right below that option).

I am not sure what I am looking for in my firewall log.
I posted a copy of todays Firewall Log at https://pastebin.com/5K3J2gEb

I unchecked the “/wp-includes/*” list of files, however we are not using TinyMCE WYSIWYG editor.

Still cannot add images to posts.

The last line of the log shows that there was an upload and the firewall accepted it. But besides this, there is nothing else. That would mean that the firewall does not block you, but you may have another script or plugin that does not work well with it.

If you try to disable NinjaFirewall from its “Firewall Options > Firewall protection > Disabled” menu, does it solve the problem ?

Disabled NinjaFirewall and this does not solve my problem.

I think it might have been caused by an update to Genesis 2.1.2.

Many thanks.