Fatal error: Call to undefined function: is_admin() “What the

Yes, absolutely back up the database first – if i hadn’t, i’d be crying right now.

My webhost doesn’t limit the mem setting; and i’ve happily run wp-2.7 – 2.9b with the mem limit set at 128; worked just fine.

The really strange aspect to me is my add-on domain http://www.websitenamehere.com *requires* more than 32mb, and is actually running fine with a mem limit = 128 in the wp-settings.php in its directory (for http://www.websitenamehere.com) – I keep waiting for the add on site to break because of mem limit=32 in the primary domain directory being the only setting that works; and yes, I’ve tried 64m, 92m, 128m – anything over 32m in the primary wp-settings.php file breaks that site, and all the sub sites.

ok. i just now manually reinstalled *everything* yet again – still have the same issue re: any mem limit over 32m in the primary domain folder’s wp-settings.php file breaks all of my wordpress sites – including the primary domain.

if this is a bug – what is the correct escalation path to alert the dev team to this issue?

thank you….!

Thanks Portent. I had my blog hacked and re-uploaded the wp-includes file but still had the same error thrown as the original poster. So I followed your advice and uploaded the wp_settings.php file for ver. 2.9 and now I’m back online (hopefully for good….)

And I just wiped mine. That was some hard work there.

Please, please fix this.

Hey everyone,

I had the same problem and fixed it this way:

1. I get the error about memory limit when I am trying to auto upgrade a commerce plugin.

2. I went into wp-settings.php and changed 32 to 64

3. i get the ‘Fatal error: Call to undefined function: is_admin()’ error and I can’t get into the site on any page and the sky goes dark and I hate wordpress.

4. I read this thread and decide to not get too dramatic just yet, so I manually download wp 2.9.1 and copy across the files : wp-setings.php and vars.php to my site that is down.

5. Now it is back up and running again. So I recommend just trying this first before you backup databases, content folders etc.

Thanks for this thread, it helped me out. Help bloggers rule.

WordPress dev team – dudes, seriously, how can you release even such a minor update and have it break heaps of peoples sites. It makes us loose faith. Less updates, more stability I say. WordPress is flippn awesome but when something goes wrong the whole wordpress structure goes to hell. Less updates, more stability please.

Thank you

I did what others have said to do on this page – I copied the original wp-content folder and wp-config.php and installed wordpress (2.9.1) onto my computer. I uploaded the new installation of wordpress onto my domain and then copied the original content folder and wp-config.php file… my site ran, but it was blank. Should I have backed up the database, too? I’m guessing that’s what the problem is.
Sorry if I’m an annoying newb…

I hit this same issue while upgrading from 2.8.ish to 2.9.2.

Problem was specifically a bad upload of wp-settings.php — the old version of the file was still on the FTP server, and did not contain a definition of is_admin(). The new version of that file does have is_admin() defined.