WordPress Error: Nothing found for Wp-admin Post PHP

Recently I was working on a blog post which, for some reason, failed to save. Instead, it generated the following error:
Nothing found for Wp-admin Post Php

The post was longer than average, so my first thoughts went to a PHP memory issue… but that rabbit hole did not bear fruit. After much searching, I narrowed the error to an Apache security module called mod_security. At first it did not make sense to me that a failure to post could be related to a security issue as shorter posts, and long test posts saved just fine. What I found out was that my problem post contained enough SQL keywords (such as SELECT, FROM, WHERE, JOIN, etc) to cause concern to a SQL injection detection algorithm. (as it was explained to me by my Liquidweb guy)

The problem was quickly fixed by adding my web site domain to a mod_security white list using the following syntax:

SecRule SERVER_NAME “simonbaier.com” phase:1,nolog,allow,ctl:ruleEngine=off

By the way, if you are looking for a great hosting company, I can’t say enough good things about Liquidweb. Their pricing is very reasonable with shared hosting starting at around $15/month, and dedicated at around $200. What really differentiates Liquidweb is their service. For me it’s like having a part time employee looking after my web server. I have always received an answer from their 24/7 telephone tech support, and have found them to be very knowledgeable, and eager to solve my problems.

6 Replies to “WordPress Error: Nothing found for Wp-admin Post PHP”

  1. Hi,

    I had the exact same problem but the workaround didn’t work for me (I am already using Liquidweb).

    My problem was due to having the word SELECTION followed later on the page by FROM so I used an even simpler workaround – I changed the wording on the page and the job’s a good ‘un!

    Thanks for the pointer though. I have had the problem with Joomla sites but this is the first time it’s shown itself in WordPress. Once I found your post I knew exactly what to look for (had already spent a day trying to find out the cause though).

    All the best.

    1. I was trying to upload a post where I had written “SELECT” all over the place, and after changing words to “choose/pick/click on” instead of “SELECT” it worked like a charm. Thank you so much!

  2. Wow, thanks a lot for this post. I was going crazy trying to figure out how this random error was preventing me from writing a testimonials page. I finally decided I would take the extreme route of writing one word, then previewing the page after each word I wrote. “Selection” made the Internal Server Error message come up, and that led me to finding this page through google as a solution to that problem. Hopefully my server admin can add my domain to the white list, otherwise I’m going to be altering my customers’ testimonials 🙂

  3. Well, i have read about disabling mod_security on another blog but was not able to do that. what they have suggested is to add the following lines to .htaccess

    SecFilterEngine Off
    SecFilterScanPOST Off

    but my guess was most of the hosting companies won’t allow users to disable mod_security @ their ends, until you raise a support ticket and ask the support guy to put your domain in white list.

  4. Thank you! Was very frustrated and found your post and correction via Google right away. By the way, if you use the ConfigServer ModSec Control for WHM/cPanel, you can just add domains to whitelist. It’s free.

Leave a Reply