• hi!

    i just updated to WP2.6 – now i get an error on the list for published pages. the error reads

    Fatal error: Call to a member function on a non-object in /www/htdocs/wp-admin/includes/template.php on line 557

    this appears only for published and all items. the drafts list is displayed fine.

    btw: posting pages itself works fine..

    any advice appreciated. thanks!

Viewing 13 replies - 1 through 13 (of 13 total)
  • Surprised this is still unanswered after 3 weeks. Any resolution, Huedrant?

    I get same error when I exceed 160 pages on WP2.6 and 261. Same on another webhost using copied dB. Just beginning my search, came here first.

    (I just want to post content but spend 70% of time playing geek).

    To be more precise:
    Fatal error: Call to a member function on a non-object in /../template.php on line 557

    And the 162ish pages ‘limit’ is where it happens but I now have to wind back (again) to prove it’s not a particular page being (re)posted.

    Just talking to myself here, folks, aiming to record how far I get.
    * Several restores and series of dummy posts determines no apparent limit aroung 160 pages – with my particular set of tools, anyway (WLW, plugins, theme).
    * Reasonably sure of particular page causing crash.
    * Removed affiliate code (AllPosters) and it posted without xmlrpc error (at last!) or WP error in admin Manage->Pages
    * However page failed to reach right spot in tree, and appeared in top level. Except not visible to WP nav online
    * Plugin “mypageorder.php” 261 was auto-deactivated. Bummer. Guess that starts to tell me something.
    * WP team, stand down.

    I’ve had this issue all week and after not being able to find a solution to this I had to manually add pages to my new wordpress location. This has something to do with the Import/Export feature.

    Also, I was unable to see my comment count on posts. The comment migrated but not the actual count of them.

    (ie: The post will say “No Comments” but when i click on the comment link, there are 32 comments.)

    Sucks, i know.

    Hi Chanel. (hmmm, dream of 32 comments :0)
    Still working on this, several MORE dB restores since last post. Still making notes to me. Might help you, below. Note, I am talking about pages, not posts, though it might apply to them.

    * Pinned it down to two pages, mother/child, at levels 2 and 3 in nav tree.
    * Only deleting and recreating them from sanitised text worked.
    * Posting suspect child pg to suspect mother pg resulted in Manage-Pgs showing <a href=" in manage->pgs listing instead of ‘published’ status – and wasinaccessible to web browsing.

    – unable to delete – required dB restore to fix
    – a colon ‘:’ in child page title AND suspect mother did this
    – text-only page heading posted under suspect mother ok
    – and, of course, colon in child pg title under ‘clean’ mother ok

    If you don’t have too many posts/pages, Chanel – AND you could identify which page/s – a delete/rewrite might be the go.

    Guess posting ‘dirty’ html while migrating to WP (and via WLW!) is a no-no.

    Hours later, another page with a colon : in the title breaks the theme (one of Milo’s recent). Pages have clean html but content contains many single parenths as the speech is a dialect. Page slug replaces with dash. Trouble deleting page via admin.
    Placing tilde for colon fixes prob. Need to test wpadmin editor to eliminate WLW.

    Whew phillwv. That sounds like a lot of work! lol.

    Yeah, I tend to get a lot of comments because I blog like once a week. I’m not a daily blogger like most people. ??

    Did anyone find a resolution on this? I have the same error after an import.

    I had the same error. It had something to do with too many pages messing up with my template.

    How I solved this was to go the pages, search for ‘a’. This brings up all the pages you have. What I did was to then delete my useless pages (ard 8 out of 12) and that solved the error.

    I just imported my blog from wordpress.com to my own installation and although I only have ONE page, I am having this error. I cannot post new posts or write new pages…. essentially, my new blog is USELESS.

    Can I please get a hand with this?

    Thanks….

    Thread Starter huedrant

    (@huedrant)

    oh, cool, i’m not the only one encountering this problem. my workaround so far was using “windows live writer” for posting and editing pages instead. worked like a charm. ??

    @d3athjam: wow, searching for “a” really brings up the list of pages. thats at least some rescue solution.

    did some of the developers read about this nasty bug? how can we make them know about our pain? ??

    cheers!

    wizteqcom

    (@wizteqcom)

    I recently switched hosting providers. I installed a fresh copy of wp on the new host then did a restore of my posts and pages. I had the same problem when I tried to manage my pages. Managing posts and creating new pages wasn’t a problem. I just couldn’t manage the pages after they were published. The good news is that the pages were visible on the site. I just couldn’t manage them.

    To get around this I had to logon to my wp-admin dashboard and change the theme back to the default theme. Then I clicked on View Site button. On the left panel you are able to click on the individual pages. Click on each page to view them. Then click on “edit this entry”. For me I just deleted the pages one at a time. The problem went away after I deleted the Child pages of one of the main Parent pages.

    I hope this helps.

    hopefully im not to late and someone sees this..
    i recently had the same problem and fixed it. firstly, what i did to fix it was find 3 files, admin-functions (in wp-admin), edit-pages (also in wp-admin) and post-template (in wp-includes), your going to want to delete these 3 files but before you do so make sure you’ve downloaded the latest version of wp. after deleting the 3 files, upload the same files from the newest version. pretty simple. thats what i did to fix it. hope this helped ??

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘backend: fatal error in template.php line 557’ is closed to new replies.