WordPress.org

Ready to get started?Download WordPress

Forums

Error when searching for posts in the backend (illegel offset) (4 posts)

  1. Ian
    Member
    Posted 3 years ago #

    I get this error when I try to search for a post by name in the backend (under custom post types)

    Warning: Illegal offset type in isset or empty in /home/tro_admin/tradereadingorder.com/wp-includes/post.php on line 811

    If I try to search again from that page, it shows a blank page with "Invalid post type" in the middle. I can back up a couple times and search again, but I get the original line 811 error again.

    Any ideas? My post types are registered in the functions.php and I don't seem to have other problems (that give an error anyway)

  2. Ian
    Member
    Posted 3 years ago #

    Update:

    Disabling my plugins one by one, it seems to be a problem with the extending admin post filter plugin:

    "Extended Admin Post Filter"

    http://wordpress.org/extend/plugins/extended-admin-post-filter/

    I do need to be able to sort by custom taxonomy though. Are there any other ways to add in this functionality? Anyone else have experience with this plugin?

  3. captremo
    Member
    Posted 3 years ago #

    I have the same problem, but with a different plugin. But, I can't figure out which plugin is the problem yet. I'm not sure if this if the cause, but I'm getting super high CPU usage 8% (on shared) with almost no traffic. I'm also sending nearly 10Gb out of the server, but only have about 256Mb of data on the server.

    [Tue May 03 14:42:17 2011] [error] [client 67.195.110.190] PHP Warning: Illegal offset type in isset or empty in /home/creat296/public_html/wp-includes/post.php on line 811

    Does anyone have any suggestions? Thanks.

  4. captremo
    Member
    Posted 3 years ago #

    My problem is resolved. It appears that our host had installed SecureLive to help protect our installation. Sounds good, but apparently there were two files php.ini and .htaccess that required a small script to work. The script was missing from both files (perhaps do to an update or a mistake by our host to not actually save the code into the file) that caused our huge issues. Our shared server loads have now dropped from around 10% to less than 0.2%.

    If you have a similar issue and check your logs you might find lots and lots of calls from SecureLive. If so, you may have the same issue. Regards, Reme

Topic Closed

This topic has been closed to new replies.

About this Topic