thomasunise

Hey there, so I found a different workaround and I think it’s working.

But the edits I made were to make the add to cart button redirect to the checkout page skipping the cart overview.

And the way I did it was I switched the settings in WooCommerce advanced settings moving the checkout page into the cart page setting and I think it created an error with the plugin.

https://tinyurl.com/yda5wvor (screen cap of change)

I’ve reset the pages and used the WordPress booster plugin to redirect and it seems to be functioning

Appreciate the response

• This reply was modified 2 years, 7 months ago by thomasunise.
• This reply was modified 2 years, 7 months ago by thomasunise.

I ran into this same issue – it was a nightmare.

The way I fixed it:

Step zero warning: DO NOT REFRESH/RELOAD ANYTHING UNTIL THE VERY END.

Ok, so first I did a search in filezilla for all files and directories matching patior and vim

Then I deleted those – there were a bunch all over.

Then I logged into my file manager through my host. (I could not do this step through a FTP client for some reason. My updates wouldn’t take)

Then I looked in the folders includes and admin and found some other htaccess files – I deleted those.

Then I opened the htaccess file and the index file from the root.

In the htaccess file I pasted the default htaccess code:

# BEGIN WordPress

RewriteEngine On
RewriteRule .* – [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

# END WordPress

then in the index file I pasted the default index code

<?php
/**
* Front to the WordPress application. This file doesn’t do anything, but loads
* wp-blog-header.php which does and tells WordPress to load the theme.
*
* @package WordPress
*/

/**
* Tells WordPress to load the WordPress theme and output it.
*
* @var bool
*/
define( ‘WP_USE_THEMES’, true );

/** Loads the WordPress Environment and Template */
require __DIR__ . ‘/wp-blog-header.php’;

Obviously update/save them after pasting.

Then I went to my domain but logged in through wp-login.php

This would look like – yourdomain.com/wp-login.php

and boom I was in and my admin page was no longer broken. (You’ll want to go to your permalinks in your settings after doing this because it resets them.)

I don’t know if there is any code deeper in the server, but I’m looking into this because for me the timestamps on the files htaccess and index show they are from feb 2021 when it’s march 2022.

But I suggest once you get back in your site, runner other maleware scanners. like sitelock, wordfence, or wp cerber and keep it clean.

Also be sure to empty your trash in your server.

Good luck! Hope this helps someone.

• This reply was modified 2 years, 8 months ago by thomasunise. Reason: formatting
• This reply was modified 2 years, 8 months ago by Yui.