rename login page problem

Hi Ruud,
Which version of AIOWPS do you have installed?

Does the issue go away when the “Anticipate” plugin is deactivated?

Hi,

Sorry for the delay. I’ve been away for two days.
AIOWPS is version 4.1.1.
When I deactivate Anticipate, I can access my login page at https://test.rhfw.nl/trythis. The URL https://test.rhfw.nl/wp-admin stills returns the error message.

Ruud.

Hi Ruud,

I see the following error at https://test.rhfw.nl/wp-admin/:

Fatal error: Call to undefined function et_is_ab_testing_active() in /home/rhfwnl/public_html/test/wp-content/themes/Divi/includes/builder/framework.php on line 54

Does Divi theme come with A/B testing feature? If so, can you try what happens, if you disable it?

Cheers,
?eslav

Yes, it comes with split testing. You can use it on any Divi building block, but as far as I know, I cannot disable it. I haven’t used it on any building block. In fact, this is an empty site, to test the issue with AIOWPS/Divi/Anticipate.

Ruud.

Hmm, it’s a bit hard to debug this problem since Divi is a premium theme.

It would be useful to have at least a traceback of function calls that led to this Fatal Error. Can you perhaps edit the [...]/Divi/includes/builder/framework.php file at the test install and put the following two lines just before line 54 (ie. before call to et_is_ab_testing_active() function):

$e = new Exception();
echo $e->getTraceAsString();

This should print a traceback to the front-end (just before the execution dies with Fatal Error).

When I go to https://test.rhfw.nl/wp-admin/ I do not see a fatal error. I see “Not available”. This is correct behaviour and how it should work.

Yes it is. But please try again, and see what happens after I enabled the “Enable Front-end Lockout:” on the AIOWPS Maintenance tab.

@chesio: I added the lines to framework.php with this result on https://test.rhfw.nl/wp-admin
#0 [internal function]: et_builder_load_modules_styles(”) #1 /home/rhfwnl/public_html/test/wp-includes/plugin.php(525): call_user_func_array(‘et_builder_load…’, Array) #2 /home/rhfwnl/public_html/test/wp-includes/script-loader.php(1076): do_action(‘wp_enqueue_scri…’) #3 [internal function]: wp_enqueue_scripts(”) #4 /home/rhfwnl/public_html/test/wp-includes/plugin.php(525): call_user_func_array(‘wp_enqueue_scri…’, Array) #5 /home/rhfwnl/public_html/test/wp-includes/general-template.php(2528): do_action(‘wp_head’) #6 /home/rhfwnl/public_html/test/wp-content/plugins/all-in-one-wp-security-and-firewall/other-includes/wp-security-visitor-lockout-page.php(17): wp_head() #7 /home/rhfwnl/public_html/test/wp-content/plugins/all-in-one-wp-security-and-firewall/classes/wp-security-wp-loaded-tasks.php(34): include_once(‘/home/rhfwnl/pu…’) #8 /home/rhfwnl/public_html/test/wp-content/plugins/all-in-one-wp-security-and-firewall/classes/wp-security-wp-loaded-tasks.php(22): AIOWPSecurity_WP_Loaded_Tasks::site_lockout_tasks() #9 /home/rhfwnl/public_html/test/wp-content/plugins/all-in-one-wp-security-and-firewall/wp-security-core.php(207): AIOWPSecurity_WP_Loaded_Tasks->__construct() #10 [internal function]: AIO_WP_Security->aiowps_wp_loaded_handler(”) #11 /home/rhfwnl/public_html/test/wp-includes/plugin.php(525): call_user_func_array(Array, Array) #12 /home/rhfwnl/public_html/test/wp-settings.php(414): do_action(‘wp_loaded’) #13 /home/rhfwnl/public_html/test/wp-config.php(89): require_once(‘/home/rhfwnl/pu…’) #14 /home/rhfwnl/public_html/test/wp-load.php(37): require_once(‘/home/rhfwnl/pu…’) #15 /home/rhfwnl/public_html/test/wp-blog-header.php(13): require_once(‘/home/rhfwnl/pu…’) #16 /home/rhfwnl/public_html/test/index.php(17): require(‘/home/rhfwnl/pu…’) #17 {main}

Thanks, this is somehow helpful ??

I guess the problem is that, when maintenance mode is active, AIOWPS outputs maintenance page that includes call to wp_head(). However, in this case, the request is effectively for an admin page and Divi theme probably does not include file with et_is_ab_testing_active() function in admin context (when is_admin() is true).

@wpsolutions I think AIOWPS should just ignore maintenance mode in such case and call wp_die() with 403 code like it does otherwise. Quite likely this can be an issue with other themes as well.

OK, that would be great.
Thank you very much!

@tsfkar,
Aha yes – I was going to ask next whether you had front end lockout enabled and you’ve fortunately answered my question ??

@chesio – yeah thanks and I agree that maybe I will need to change the response to wp_die in this case.

Thanks for the update 4.1.2. Works like a charm!