Home › Forums › BulletProof Security Pro › Plugin Conflicts, Actively Blocked Plugins, Plugin Compatibility
- This topic has 25 replies, 8 voices, and was last updated 2 months, 3 weeks ago by
AITpro Admin.
-
AuthorPosts
-
AITpro Admin
Keymaster@ murrysim – Just run the Pre-Installation Wizard and Setup Wizard again on each site to fix that issue. The Setup Wizard will automatically create an AutoRestore exclude rule for the root htaccess file.
murraysim
ParticipantOk I will try that thank you, though I am pretty sure that has been run many times and it still happens. I will run it on this site and make a note of dates and see if it continues. Much obliged 🙂
murraysim
ParticipantHi, I just checked one of my sites and it has a bunch of wflog files in quarantine, yet it seems I had already done the
auto restore exclude wflogs thing previously? How can that be?
Here is the log of that site:
[BPS Pro 16.7: wp-content File Quarantine Logged: June 5, 2022 4:32 am]
Quarantined Filename: config-livewaf.php
Quarantine Path: /home/bcals/public_html/wp-content/bps-backup/quarantine/wp-content/wflogs/config-livewaf.php
Restore Path: /home/bcals/public_html/wp-content/wflogs/config-livewaf.php[BPS Pro 16.7: wp-content File Quarantine Logged: June 5, 2022 4:32 am]
Quarantined Filename: ips.php
Quarantine Path: /home/bcals/public_html/wp-content/bps-backup/quarantine/wp-content/wflogs/ips.php
Restore Path: /home/bcals/public_html/wp-content/wflogs/ips.php[BPS Pro 16.7: wp-content File Quarantine Logged: June 5, 2022 4:32 am]
Quarantined Filename: config.php
Quarantine Path: /home/bcals/public_html/wp-content/bps-backup/quarantine/wp-content/wflogs/config.php
Restore Path: /home/bcals/public_html/wp-content/wflogs/config.php[BPS Pro 16.7: wp-content File Quarantine Logged: June 5, 2022 4:32 am]
Quarantined Filename: attack-data.php
Quarantine Path: /home/bcals/public_html/wp-content/bps-backup/quarantine/wp-content/wflogs/attack-data.php
Restore Path: /home/bcals/public_html/wp-content/wflogs/attack-data.php[BPS Pro 16.7: wp-content File Quarantine Logged: June 5, 2022 4:32 am]
Quarantined Filename: config-transient.php
Quarantine Path: /home/bcals/public_html/wp-content/bps-backup/quarantine/wp-content/wflogs/config-transient.php
Restore Path: /home/bcals/public_html/wp-content/wflogs/config-transient.php[BPS Pro 16.7: wp-content File Quarantine Logged: June 5, 2022 4:32 am]
Quarantined Filename: .htaccess
Quarantine Path: /home/bcals/public_html/wp-content/bps-backup/quarantine/wp-content/wflogs/.htaccess
Restore Path: /home/bcals/public_html/wp-content/wflogs/.htaccess[BPS Pro 16.7: wp-content File Quarantine Logged: June 5, 2022 4:32 am]
Quarantined Filename: template.php
Quarantine Path: /home/bcals/public_html/wp-content/bps-backup/quarantine/wp-content/wflogs/template.php
Restore Path: /home/bcals/public_html/wp-content/wflogs/template.php[BPS Pro 16.7: wp-content File Quarantine Logged: June 5, 2022 4:32 am]
Quarantined Filename: rules.php
Quarantine Path: /home/bcals/public_html/wp-content/bps-backup/quarantine/wp-content/wflogs/rules.php
Restore Path: /home/bcals/public_html/wp-content/wflogs/rules.php[BPS Pro 16.7: wp-content File Quarantine Logged: June 5, 2022 4:32 am]
Quarantined Filename: config-synced.php
Quarantine Path: /home/bcals/public_html/wp-content/bps-backup/quarantine/wp-content/wflogs/config-synced.php
Restore Path: /home/bcals/public_html/wp-content/wflogs/config-synced.phpAITpro Admin
Keymaster@ murrysim – The timestamp for the log entries is June 5. So those are older log entries. Double check that you have done the steps below correctly to exclude the wflogs wp-content folder. If there is still a problem then send me a WordPress Administrator login to your site to: info@ait-pro.com.
1. Go to AutoRestore > Exclude wp-content Folders tab page.
2. Enter “Exclude wflogs Folder” for the label.
3. Enter: wflogs for the folder name to exclude. Note: Do not add any slashes or any other folder path information. Just enter the folder name.
4. Click the Save Folder Exclude Rules button.
5. Go to Quarantine and restore all the wflogs files from Quarantine.Neha gi
ParticipantStep 1: Clear Your Browser Cache. As simple as it might appear, clearing your browser’s cache can help sort out this problem.
Step 2: Consider Creating a Staging Site.
Step 3: Switch to WordPress Default Theme.
Step 4: Deactivate Your Plugins.
Step 5: Reactivate The Plugins.David Langston
ParticipantHello,
After removing WP Cerber and running the setup wizard in BPS Pro, I keep getting this error in the PHP logs:
[08-Nov-2022 12:05:18 UTC] Cron unschedule event error for hook: cerber_scheduled_hash, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:false,”args”:[“\/home\/dynamowmoles\/public_html\/wp-content\/uploads\/wp-cerber-5XZD8MEUGQYSH042P6I7\/tmp\/all-in-one-wp-migration-unlimited-extension.zip”]}
[08-Nov-2022 12:05:18 UTC] PHP Warning: Cannot modify header information – headers already sent in /home/flowgoyoyo/public_html/wp-content/plugins/litespeed-cache/src/vary.cls.php on line 735Can you advise how I can get rid of this?
Many thanks!
David Langston
ParticipantHello,
I sorted my issue above using Advanced Cron Manager
Many thanks!
David Langston
ParticipantActually, I still can’t remove the cerber_scheduled_hash cron. It comes straight back even with the plugin removed. Any ideas would be great! Many thanks!
AITpro Admin
KeymasterFirst purge/delete all plugin cache (LiteSpeed, etc). Next go to the BPS Pro > Tools > Scheduled Crons tool > click the Reset|Clear All Cron Jobs button.
David Langston
ParticipantMany thanks, that worked.
Any ideas on how to fix this one?
[08-Nov-2022 13:37:45 UTC] PHP Warning: Cannot modify header information – headers already sent in /home/flowgoyoyo/public_html/wp-content/plugins/litespeed-cache/src/vary.cls.php on line 735
AITpro Admin
Keymaster“headers already sent” errors are usually caused by using the WP_DEBUG constant in your wp-config.php file (ironic, but is the nature of the debugging beast). Check your wp-config.php file and if WP_DEBUG is set to true then change it to false:
define('WP_DEBUG', false);
. Important Note: make sure there is no whitespace after “define”. Should bedefine(
and notdefine (
-
AuthorPosts
- You must be logged in to reply to this topic.