xorcise

Thats great, many thanks!

Hi, I am looking to remove the blue section on the left.

If I wanted to remove the whole footer (blue and purple sections) can this be done also?

Many thanks

Hi

I have uploaded a log from one of my sites to:
https://www.dropbox.com/s/okff2w7xj9x6kz8/log.a3c161d10e21.txt?dl=0.
On this site, backups (File & DB) are set to run weekly and retain the last 4. There are 10 in the Existing Backups window: Oct 23, 17, 09 & 02, Jun 12, May 13, May 02, Apr 30 & Apr 29. Would these possibly be manual backups?

This is the log from the website which has 10 backups when only 5 is set: https://www.dropbox.com/s/9p0wz102ldpcuix/log.2b3ea984234c.txt?dl=0. The backups dates are Oct 23, 17, 09 & 02, Sep 25, 18, 11, 04, 03 & 02. I think I must have changed from Daily to Weekly backups. Interestingly the View Log button is only available for the most recent 6 backups, and not for Sep 11, 04, 03 or 02. This log is from the oldest log available, Sep 18

After disabling/removing ithemes and All In One the error log does recreate itself, but much slower – only 15 new lines appeared in the last while.

I took a look at the database, and noticed that the tables for this site all have two AUTOINCREMENT options set, as below. MySQL allows you to specify what number to begin auto incrementing from using the autoincrement=X option, but I am thinking maybe having it listed twice here is causing some sort of problem. This is the only site from this server which has autoincrement=X set.

Is the problem bigger than just these two plugins do you think?

error_log entries:

[23-Feb-2020 09:06:53 UTC] WordPress database error Duplicate entry '742237' for key 'PRIMARY' for query INSERT INTOha_options(option_name,option_value,autoload) VALUES ('_transient_doing_cron', '1582448813.2843890190124511718750', 'yes') ON DUPLICATE KEY UPDATEoption_name= VALUES(option_name),option_value= VALUES(option_value),autoload= VALUES(autoload`) made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘init’), WP_Hook->do_action, WP_Hook->apply_filters, wp_cron, spawn_cron, set_transient, add_option

[23-Feb-2020 09:08:06 UTC] WordPress database error Duplicate entry ‘742237’ for key ‘PRIMARY’ for query INSERT INTO ha_options (option_name, option_value, autoload) VALUES (‘_transient_doing_cron’, ‘1582448886.0096879005432128906250’, ‘yes’) ON DUPLICATE KEY UPDATE option_name = VALUES(option_name), option_value = VALUES(option_value), autoload = VALUES(autoload) made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘init’), WP_Hook->do_action, WP_Hook->apply_filters, wp_cron, spawn_cron, set_transient, add_option`

MySQL settings:

-- AUTO_INCREMENT for tableha_options
ALTER TABLE ha_options
MODIFY option_id bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=738181;
—
— AUTO_INCREMENT for table ha_postmeta
ALTER TABLE ha_postmeta
MODIFY meta_id bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=6839;
—
— AUTO_INCREMENT for table ha_posts
ALTER TABLE ha_posts
MODIFY ID bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=894;`

Hi @davidvee, can you tell us please what the environment conditions need to be on the test server where we are running this plugin, or what are the CLI approaches that can get around the server timeout issues which you mention? I have copied my clients site to my test server, and am getting this error message. I increased max_execution_time in php.ini to 3000 (50 minutes), and after 20 minutes all 15 plugins were scanned and all had this error message against them. Just how should we set up a test environment for this plugin to work?

Hi @davidvee, can you tell us please what the environment conditions need to be on the test server where we are running this plugin. I have copied my clients site to my test server, and am getting this error message. I increased max_execution_time in php.ini to 3000 (50 minutes), and after 20 minutes all 15 plugins were scanned and all had this error message against them. Just how should we set up a test environment for this plugin to work?