Thanks for those kind words, @KBConcepts 
To be honest, those two years also included about 2 months of learning shell scripting. But the rest was all spent writing, testing, rewriting, retesting, … the code of WP Sweeper.
An important factor is that WP Sweeper isn’t an update tool, but more a crash-recovery tool in case of hacks. So it will replace the current version of WordPress with clean files of the exact same release, which is especially handy when the hack is so extensive you don’t have back-end access anymore.
As for the backups:
Version 1.1 will bring Restore Point support, meaning a backup can be made before initiating the actions and thus providing an easy means of rolling back (both files and database!) in case something does go wrong. This should go live later this month.
If interested you could register on https://wpsweeper.gumroad.com and follow the project for development updates.
At this point WP Sweeper will only be able to replace the source code for themes available on the wordpress.org repository. However, I am looking into developing features that will allow you to use custom repositories too.
__ ___ __ _____ _____ ___ _ __ ___ _ __
\ \ /\ / / '_ \/ __\ \ /\ / / _ \/ _ \ '_ \ / _ \ '__|
\ V V /| |_) \__ \ V V / __/ __/ |_) | __/ |
\_/\_/ | .__/|___/ \_/\_/ \___|\___| .__/ \___|_|
| | | |
|_| |_|
wpsweeper.com
######### WordPress Plugins #########
Replaced WordPress version 5.8.2 with new corefiles from the WordPress.org repository.
######### WordPress Plugins #########
Below you'll find the plugins that were succesfully replaced by a new version, downloaded from the WordPress.org repository.
If a replacement is listed as FAILED, this is caused by one of these reasons:
- The plugin is a premium plugin (which we can't automatically replace for you).
- The plugin is removed from the WordPress.org repository.
- The plugin a custom developed code that isn't published to the WordPress.org plugin repository.
FAILED: Goodbye-You was not replaced. Not available for download on the wordpress.org plugin repository.
SUCCESS: akismet
SUCCESS: blocs-developer
SUCCESS: brave-payments-verification
FAILED: combell-disabler.php_ was not replaced. Not available for download on the wordpress.org plugin repository.
SUCCESS: cryptocurrency-donation-box
SUCCESS: hello-dolly
SUCCESS: jetpack
SUCCESS: koko-analytics
SUCCESS: litespeed-cache
SUCCESS: mailin
SUCCESS: mainwp-child
SUCCESS: query-monitor
SUCCESS: wordfence
SUCCESS: wordpress-seo
SUCCESS: wp-security-audit-log
######### WordPress Themes #########
Below you'll find the themes that were succesfully replaced by a new version, downloaded from the WordPress.org theme repositor
y.
If a replacement is listed as FAILED, this is caused by one of these reasons:
- The theme is a premium theme (which we can't automatically replace for you).
- The theme is removed from the WordPress.org repository.
- The theme a custom developed theme that isn't published to the WordPress.org theme repository.
SUCCESS: rams
SUCCESS: twentythirteen
SUCCESS: twentytwelve
SUCCESS: twentytwenty
SUCCESS: twentytwentyone
To be fair I did not run the malware scan, so this isn’t included, as my site is free of any infections and you wouldn’t be much with an empty report section. But the above does give you an example of how such a log file would look like.
And this is how it gets stored on the server:
2.3K Jan 3 18:58 wpsweeper-2022-01-03.18:56:56.log
By saving them as simple text-files with the “.log”-extension, they can be opened in any text-editor.
Actually most hosting providers already indicate if it is Linux based. And to be fair, the most part is, since Windows-based hosting requires extra costly licenses for the operating system. A good indicator would be any Apache and MySQL references being present.
