Error on Latest Plugin Update

Thank you Samuel, now we are talking.
But again, it’s impossible to access the website.
An entirely different issue is that Wordfence claims that its compatible with a lower that 3.7.1 version, but that should be discussed somewhere else, about “accountability issues”. ??
So now we narrow in to the why – which leaves the all important HOWTO.

@nsnbc: As I stated to you before, you will need to use FTP or SSH to access the files on your website itself in order to remove a malfunctioning plugin.

If you do not have any ability to access the files on your website directly, well, then you’re kinda stuck. I mean, the bottom line is that it’s your site. You need to be able to manipulate the files on that site.

WordPress is just software that runs on the top layer of the site. It’s a publishing tool, not a file management system. It just gives you a way to easily publish content, it doesn’t actually have total control over the site itself.

If you don’t know how to access the files on your site, and you don’t know what FTP and SSH mean, then I suggest you contact your web hosting service and ask them for support.

We do have some information about FTP and such in the codex, but really, this is super-basic first-step kind of stuff. You cannot create a website without manipulating files on the site.

https://codex.www.ads-software.com/FTP_Clients
https://codex.www.ads-software.com/Using_FileZilla

I am running WordPress 3.8.1 and I didnt have this issue before I upgraded WordFence today.

Same here…

blogbaladi, TrinitysKitchen, I’m sorry that other people seem to have invaded your topic with their own problems. This is why we ask people to post their own topics, so that problems don’t get overlooked.

If you’re getting some other message that is not “Call to undefined function wp_get_current_user()”, then my response about WordPress versions does not apply to you. The “is_404” message is almost certainly a problem with the plugin instead.

For you, please see my comment earlier about “display_errors”. You need to disable this on your webhost. “Notice” messages should be disabled on your configuration, for security. Error messages like these should be turned off on your web host.

I know we all should update to 3.8.1 but due to some reasons of theme or other plugins compatibility, not all of us can do this. The plugin says is compatible since 3.3.1: “Requires: 3.3.1 or higher” and after this update, that is not true. You should modify this if the error will not be fixed.

formulaclick: I am not the author of this plugin. If they wish to modify their supported version number, then that is their business.

I am merely providing information. This is not the only plugin in the directory that could cause that specific problem. If you cannot upgrade WordPress because of some other incompatible code, then you should get rid of the incompatible code and upgrade anyway. Not upgrading leaves you vulnerable to known security risks which are fixed in later versions. And you will increasingly run into problems like these because you are lacking critical core bugfixes.

Not upgrading is not a valid option. Upgrade. Save yourself the trouble later down the line.

You have the latest version of WordPress.

If you need to re-install version 3.8.1, you can do so here or download the package and re-install manually:

I also have the latest version and still get that message

@samuel Wood,
I have 3.8.1. and i updated my wordfence today
This is my error message:

Notice: is_404 was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.) in /…./wp-includes/functions.php on line 3049

When i disable the plugin it disappears
Not sure what’s wrong and what i need to do. Isn’t there some problem with this update that I made? The previous version worked fine.

Here’s a quickfix for the is_404 notices if you want to keep the wordfence plugin running but can’t turn off the notices for whatever reason(do try to turn the notices off).

In the meantime, you can suppress these two is_404 notices and keep them from displaying, using these instructions, until you manage to turn the notices off alltogether, or the wordfence team issues the official update fixing these issues

Log in to your FTP and edit the following two files:

1.wp-content/plugins/wordfence/lib/wordfenceClass.php:

line 270
change

if( empty($wfFunc) && is_404() ){
to
if( empty($wfFunc) && @is_404() ){

and

2.wp-content/plugins/wordfence/lib/wfLog.php:

line 392:
change
(is_404() ? 1 : 0),

to

(@is_404() ? 1 : 0),

That fixed the message for me zoranc. I’m using WP 3.8.1 and the notice appeared immediately after upgrading Wordfence tonight.

As I said , it is meant as a quickfix to prevent these two specific notices from displaying. It is by no means a permanent solution.

I tried it zoranc and it didn’t fix it for me. I ll just wait for wordfence to see if they r gonna fix it anytime soon.

This is a long thread. Just wanted you to know I’m busy reading it and investigating…

Will have a response soon.

Regards,

Mark Maunder.

Firstly, thanks very much Otto for weighing in here.

For the folks that are complaining about this issue, you have the following setting in your wp-config.php file which should not be used in production sites:

define(‘WP_DEBUG’, true);

That is the only way that this error can possibly be generated and made visible to your customers.

I strongly recommend you disable debugging if you’re running a production website.

I’d appreciate it if some of the folks here can confirm that this setting IS in fact enabled in wp-config.php and also give me some insight as to why you would do this. Not looking to hen-peck our users, but I’d like to gain a deeper understanding of how you choose to configure your sites.

We changed the order in which the logging code is run as a performance enhancement in the newest version and it looks like is_404() is being called too early. So we’re working on a fix which will be released shortly.

Regards,

Mark.

Not sure why my last message was not posted by the board. Trying again after I waited 5 mins. Sorry if a duplicate appears:

Firstly, thanks very much Otto for weighing in here.

For the folks that are complaining about this issue, you have the following setting in your wp-config.php file which should not be used in production sites:

define(‘WP_DEBUG’, true);

That is the only way that this error can possibly be generated and made visible to your customers.

I strongly recommend you disable debugging if you’re running a production website.

I’d appreciate it if some of the folks here can confirm that this setting IS in fact enabled in wp-config.php and also give me some insight as to why you would do this. Not looking to hen-peck our users, but I’d like to gain a deeper understanding of how you choose to configure your sites.

We changed the order in which the logging code is run as a performance enhancement in the newest version and it looks like is_404() is being called too early. So we’re working on a fix which will be released shortly.

Regards,

Mark.