Try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.
If that does not resolve the issue, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel (consult your hosting provider’s documentation for specifics on these), navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue (theme functions can interfere like plugins).
Hi James,
Thank you for your reply.
I have tried manually resetting each plugin, but that sadly didn’t solve the problem. I am wary about forcing the default theme to activate, as I am very scared that all my content, and manual design, will be lost at the same time. I have read other places that the warnings are actually not because something is wrong with my website, but something about the latest upgrade and that WP cores is working on a fix.
I have no idea what to do, or if there is anything I could do, as I would really love to be able to log in.
All the best,
Miriam
If I go to line 601 of /var/www/miriamveksebo.dk/public_html/wp-includes/plugin.php, as the warning is about it says (Line 601-622):
call_user_func_array($the_[‘function’], array_slice($args, 0, (int) $the_[‘accepted_args’]));
} while ( next($wp_filter[$tag]) !== false );
array_pop($wp_current_filter);
}
/**
* Check if any action has been registered for a hook.
*
* @since 2.5.0
*
* @see has_filter() has_action() is an alias of has_filter().
*
* @param string $tag The name of the action hook.
* @param callable|bool $function_to_check Optional. The callback to check for. Default false.
* @return bool|int If $function_to_check is omitted, returns boolean for whether the hook has
* anything registered. When checking a specific function, the priority of that
* hook is returned, or false if the function is not attached. When using the
* $function_to_check argument, this function may return a non-boolean value
* that evaluates to false (e.g.) 0, so use the === operator for testing the
* return value.
——————————————————————————
I am thinking that the value is set to zero, and if zero equals false, I could maybe test to see is an other value would be better. But as I have no clue what I am doing, I would really love your input. Does something look of to you? Should I insert something, or change something?
Thanks a bunch!
The problem isn’t with the /wp-includes/plugin.php file itself, but rather with a function being passed through it, either a plugin or theme function.
If it wasn’t a plugin, it’s likely your theme.
