3 bugs?

Try the latest development version.

Hi LordOfChaosPT

This problem is weird as is_user_logged_in() is a standard WordPress function.

I have activated WordPress Access Control on both my WordPress 3.4.2 and 3.5.1 sites with the development version of Frontend without problems so it’s related to your site. However some users have experienced the same problem with WordPress Access Control.

In order to help I’m going to ask you a few specifics so I can nail down the problem. If that doesn’t work admin access might be required.

1. What is your version of WordPress?
2. What is your version of WordPress Access Control?
3 .Does Frontend work with WordPress Access Control deactivated?
4. When does the Fatal Error occur. On activation of Frontend? On display of main page?
5. Does it occur when logged in as admin?
6. What options of Frontend have you changed (Screen Shot link or email would help)
7. What options of WordPress Access Control have you changed (Screen Shot link or email would help)

If you want to email me your links or give me admin access your can send them to me at abruinATihugDOTcomDOTau

Ahhh…I think the textdomin functions might be the cause.

Access Control hooks the ‘get_pages’ WordPress function and substitutes it’s own get_pages function which calls is_user_logged_in() and crashes because somehow the WordPress has managed to lose track of it’s included file wp-includes/pluggable.php which contains is_user_logged_in().

get_pages() is used by Frontend. Both Frontend and Access Control set the text domain.

Strange it works for me but not you.

Now investigating further.

Actually the load_textdomain warning you posting is generating by the CodeStyling plugin. The problem with is_logged_in() still occurs with this disabled.

NOTE: The following technical info is for those who experience similar problems.

Somehow Access Control is triggering to Frontend function wpuf_get_pages() to run before all the plugins have been loaded.

wpuf_get_pages calls get_pages which is hooked by Access Control and calls is_user_logged_in() which is in wp-includes/pluggable.php which doesn’t get loaded till after the plugins have been loaded as shown from wp-settings.php (called at WordPress init)

wp-settings.php
================

// Load active plugins.
foreach ( wp_get_active_and_valid_plugins() as $plugin )
	include_once( $plugin );
unset( $plugin );

// Load pluggable functions.
require( ABSPATH . WPINC . '/pluggable.php' );
require( ABSPATH . WPINC . '/pluggable-deprecated.php' );

The idea here is that plugins can substitute their own versions of the functions in pluggable.php.

Check your email

Have found the problem!!!!

Basically during the loading of Frontend it calls a function wpuf-get-option() in the file:function attachment.php:__construct() which is called during the construction of the class WPUF_Attachment in which it resides.
This eventually results in the calling of the file:function wpuf-functions.php: wpuf_get_pages() which calls WordPress function get_pages().

get-pages() normally works fine until WordPress Access Control is enabled which hooks this function. The problem is that the WordPress Access Control hook function calls is_user_logged_in() which is a WordPress pluggable function which isnt loaded till after all plugins have been loaded. Hence the Fatal Error.

In summary this is a WordPress Access Control bug as it shouldn’t be using a pluggable function in it’s hook.

The development version doesn’t use wpuf-get-option during the construct phase anymore so it doesn’t have a problem (NB The attempt to load the development version reported above failed leaving the old version and error intact)