Those posts didn’t really apply to my post.
I’m trying to figure out why I can call:
wp_signon()
wp_insert_user()
wp_create_user()
wp_update_user()
all with no problems.
When specifically only wp_logout() is causing this error after logging a person out.
I don’t think adding “allow for all” because this one function is throwing an error when it’s calling wp-cron.php is the right solution. Why does it need wp-cron.php? What is wp-cron.php doing? Why does wp-cron.php operate on different premissions that the other files used by wp_logout()? Does it try to call wp-cron.php after logging the person out and that’s why they no longer have permissions?
I was hoping to save some time tracing through the source code yet again. The project is finished. There’s just this one outstanding issue.
I was clearing my cache at the same time I was calling wp_logout(). Duh!
Fixed.
Nope. It’s still writing an error message to the domain error_log:
client denied by server configuration: /home/user/public_html/clubzone/blog-it/wp-cron.php
function wp_logout() {
wp_clear_auth_cookie();
do_action(‘wp_logout’);
}
I’m thinking it’s clearing the authentication cache, then trying to do some other things but it is no longer authenticated.
I’ve looked at do_action, but I haven’t been able to find the location where the variables are set up for the do_action function to perform the logout. Does anyone know where the initialization occurs for all of the do_action calls?
I’m calling wp_logout from a directory above the blog.
Using:
<?php
require_once($_SERVER[‘DOCUMENT_ROOT’].”/../conf/wp_conf.php” );
require_once($_SERVER[‘DOCUMENT_ROOT’].$base.”wp-includes/user.php”);
require_once($_SERVER[‘DOCUMENT_ROOT’].$base.”wp-includes/registration.php”);
require_once($_SERVER[‘DOCUMENT_ROOT’].$base.”wp-includes/pluggable.php” );
wp_logout();
?>
https://domain/clubzone/blog-it/wp-login.php?loggedout=true
Writes an error message to the error log, too!
client denied by server configuration: /home/user/public_html/clubzone/blog-it/wp-cron.php