toulouse

@dwinden

Thank you for your reply.
Yes I have tried and played with the settings. However it is not clear to me what the setting Custom Login Action is supposed to do.

I have looked at the php code of the plugin and I can’t find anything about the ability to add exceptions to the redirecting. If this functionality is not in the plugin I guess this would be more of a feature request.

Are you a developer of this plugin or just a really active member on the WordPress support forums? I could try and make a pull request for this feature?
I can change it for my own website, but then my client would not be able to update the plugin or my changes would be overwritten.

I saw this post of another user about too many Database Backups. Can you check if there are too many backups being created?

I think your next steps are trying to pinpoint which part of iThemes is giving you trouble. Try disabling all features and enabling them one by one to find what is causing this issue.

Hi Donna,
Just reacted to your other post but I guess this is the real problem then. I’ve been looking around in the plugin files and the backup settings are stored in the option itsec_backup. What is the value of this option for you (it is a serialized array)?

I also found it uses your timezone settings, and this is a WordPress setting I believe. What is the value of the option gmt_offset? And what is the output of the php function time()? Maybe the time settings of the server are wrong?

Try
<?php
date('G:i d-F-Y', time());
?>

Hey Donna, this sounds like it may be an other problem, and it is not related to the hide backend module.
Do you mean if you disable the plugin it runs like a champ, or if you only disable the hide backend part of the plugin it runs like a champ?

Could you test what the side does when you disable the hide backend module?

Are you able to change the module to disabled? You can also do this in the database I think.
To disable the hide backend feature from the database I think you can do it by editing the itsec_hide_backend option and change the part where it says
s:7:"enabled";b:1;
to
s:7:"enabled";b:0;

Hi Donna,

Did you resolve the issue yet?
I found a solution in better-wp-security/core/modules/hide-backend/class-itsec-hide-backend.php.
In your database go to the [prefix]_options table and look for the option_name of itsec_hide_backend. This is a serialized string with options. Here you change the theme_compat to 0.

For example itsec_hide_backend should look something like this.

<br />
a:7:{s:7:"enabled";b:1;s:4:"slug";s:6:"[your_custom_login_url]";s:17:"theme_compat_slug";s:9:"not_found";s:16:"post_logout_slug";s:0:"";s:12:"theme_compat";b:0;s:12:"show-tooltip";b:0;s:8:"register";s:15:"wp-register.php";}<br />

You can copy paste this, just change [your_custom_login_url] to the url you want to use for logging in.

Let me know if this helped.

edit: to be clear, you should change this part:
s:12:"theme_compat";b:1;
to this:
s:12:"theme_compat";b:0;
The rest you can leave the same. Or just copy paste the complete code I posted and change the [your_custom_login_url].

Hey,

This post also had a Premature end of script headers: index.php error. There it was a problem with the setup of the server, the memory limit was reached. Could this be the problem?

This post also had a problem with the setup of the server, but with the timeout set.

Are you able to debug the server further, enable a higher level of logging?

Disclaimer: I’m not an expert, just saw your post and wanted to help ??

Hello,
I also got this notice when wp_debug was enabled.

dwinden, you are correct, the line number has changed to 220.

The theme I used had wp_deregister_script('jquery') in it’s functions.php file. That was why $wp_scripts->registered['jquery'] was not an object.

I changed line 220 to:

if ( is_object ( $wp_scripts->registered['jquery'] ) ) {
	$jquery_ver = $wp_scripts->registered['jquery']->ver;
} else {
	$jquery_ver = null;
}

This got rid of the notice. Themes deregistering jquery is probably not good practice, but with this check you can avoid the notice when using such themes.

p.s. sorry if there are formatting errors. Just created this account to post this.

Edit: This actually gave me another notice (undefined index jquery). What I use now:

if ( isset ( $wp_scripts->registered['jquery'] ) && is_object ( $wp_scripts->registered['jquery'] ) ) {
	$jquery_ver = $wp_scripts->registered['jquery']->ver;
} else {
	$jquery_ver = null;
}