wp_nonce_create fatal error

This is usually an indication that your php memory limit or max_execution_time is set too low. See below:

You can define this in your php.ini file (usually found in /etc on linux systems check your documentation for windows servers). Look through he file for a line like this:
memory_limit = 128M
Keep in mind the 128M is probably different. That’s the amount of memory that php is allowed to consume. If you have 10 plugins and combined they consume more memory than you have allocated, you’re going to have problems. You can assign more by increasing this value. (my personal sites have 256M allowed, but this is for a pretty big site with a substantial number of hits and plugins). Make sure and restart httpd (apache) after making changes here.

Let5 me know if this fixes it.

tim

Just FYI, this has nothing to do with memory. The error says the function you’re calling is in fact not defined. It doesn’t exist. Not yet anyway at the time you’re calling it. Maybe you need to wrap it in a hook so it gets run later in the WP process.

Another example of the same problem:
https://wordpress.stackexchange.com/questions/30583/fatal-error-call-to-undefined-function-wp-create-nonce

I should mention I’m seeing the same error in my logs.

I’m starting to see it again too — I think it may have originally happened when people could access wfUnlockMsg.php directly (loading the file when WP wasn’t loaded), but that file is now blocked by .htaccess in that folder, as long as the server is configured to respect all .htaccess files.

I noticed today that it happened at the same time as an access to admin-ajax.php was blocked by Wordfence (with a 503 HTTP status) in my access_log — it sounds like Wordfence may be trying to display that message when ajax requests are blocked. Bug?

I’m seeing this error too. Hope it clears up with updates.