Checkout unm?glich, drehendes R?dchen und Fehlermeldung
-
Seit ein paar Tagen ist bei meinem Shop der Checkout nicht mehr m?glich. Nachdem man die gewünschten Produkte in den Warenkorb gelegt hat und zur Kasse geht, drehen sich auf der rechten Seite nur zwei R?dchen, die normalerweise die Zahlungsweisen aktualisieren. Diese h?ren nur leider nicht auf und der Kunde kann keine Zahlungsweise ausw?hlen. Sollte man dennoch auf “Jetzt kaufen” klicken, erscheint die Fehlermeldung “FEHLER BEIM BEZAHLVORGANG. VERSUCHE ES BITTE NOCHMAL.”.
Das habe ich bereits getan/versucht:
- Alle Plugins, die noch nicht auf dem neuesten Stand waren geupdated
- Germanized langsam bis zum September letzten Jahres mit Rollback zurückgedated (mittlerweile wieder auf der neuesten Version)
- WooPayment aktiviert und registriert (da stand etwas von “wenn das nicht registriert ist, k?nnen Sie keine Zahlungen annehmen”; hat natürlich auch nichts gebracht, aber einen Versuch war es wert. Immerhin k?nnte ich jetzt Kreditkarten annehmen wenn ich wollte. Yeyy)
- Zahlungsarten in den Einstellungen überprüft, alles wie vorher auch
Das Problem ist irgendwann zwischen dem 4. und dem 9. M?rz aufgetreten, wann genau kann ich nicht sagen, heute ist es zum ersten Mal aufgefallen. Seit dem 4. M?rz kamen keine Bestellungen mehr durch.
Es wurden vermutlich Updates von Plugins in diesem Zeitraum gemacht, ich kann aber nicht genau sagen, welche Plugins das betraf.
Ein Kunde hatte das Problem und machte mich darauf aufmerksam. Er probierte es in drei verschiedenen Browsern mit mehren Adressen, keine Chance. Auch ich hatte keine M?glichkeit, egal was man tut, man kommt um dieses bl?de Drehr?dchen nicht herum.
The page I need help with: [log in to see the link]
-
Hey @omarfpg,
thank you very much for your suggestions!
I tried scanning the site with Wordfence: Installed its plugin (only the free version) and scanned the site. Except for 13 update suggestions (mostly Plugins that are installed but deactivated and 2 activated ones whose updates were released today or yesterday, which I haven’t updated yet) nothing else came up.
I then made a staging site using “WP Staging”, which leads to my domain name with a bunch of numbers behind. Inside this staging area I installed the plugin “WP file manager”, edited the wp-config.php with the following text:
// Enable WP_DEBUG mode define( 'WP_DEBUG', true ); // Enable Debug logging to the /wp-content/debug.log file define( 'WP_DEBUG_LOG', true ); // Disable display of errors and warnings define( 'WP_DEBUG_DISPLAY', false ); @ini_set( 'display_errors', 0 );All as explained before the “That’s all…” text.
Then I went to WooCommerce > Status > Logs inside my staging site and discovered: nothing! There were exactly two logs, one was for woopayments and the second one was a “test-log” file. No fatal logs or any other data. The test-log file was empty.
Do I have to wait longer in order for them to appear or is there something I missed? Thanks and have a nice day! ??
Adding on to the information: Using the staging site I just disabled every plugin, except for:
- Cache Enabler (to clear the cache between changes)
- WooCommerce
- PDF Invoices for WooCommerce (I was not able to deactivate this plugin, my try always brought me to the white site I encounter when making changes to content, Failure code 500() – also WordPress sends me a mail stating there was a critical error on my site, ending with: “…&plugin_status=active&paged=1&s&_wpnonce=ae536c361a”; also when clicking on “rollback” (to install a version prior) I get this error message: “rest_no_route”)
- WP Rollback
- WP Staging (to not kill the staging site somehow and with that kill my live one. Not sure if that fear is valid, never worked on a staging site before)
Additionally I reinstalled WordPress, deleted and reinstalled WooCommerce and switched to storefront only to find, that the problem is still there, no changes.
I try to include as many details as possible, maybe there is something interesting and helpful in one of them. Please let me know if I can provide any more information ??
Hello again and thank you to everyone who tried their best and helped me out!
Today I had help by two people and we tried and find the cause for the problem. And what can I say: we solved it! But it was a rocky process.
In my database another website is hosted, whose making was started, but never finished. I just saw it today, that this site also had some problems, in fact 49 malicious data files in the database were found. I did some other scans using plesk on my initial site and well… more malware found in files. They were all over the place, in uploads, plugin folders and even inside (!) the wp-config.php! They just changed the text inside this file a little, so they could crawl in.
Side-note: Wordfence never suspected anything. The site was clean and there was nothing unusual going on the whole time. So I am not sure if I like the plugin completely… Maybe it suspects stuff in other cases, but in this case it failed me.
It was the usual: two admin-accounts were created on the second site, a bunch of comments were written and approved by one of the “admins” containing suspicious links. The site was fortunately never filled with content so the 52 (!) comments could not be read anywhere. But… the files were also planted in the part of my first site. Nearly not as much as on the second one but still… impressive!
So, we did what every normal adult would do: sit down for two hours and go through every found malicious file on both websites and delete the whole thing. Mostly they were pretty easy to identify with names like “hjdoaa.php” or “rmlpfyn.php” but some were disguised as “profile.php” or other official sounding names. Only the wp-config was not deleted but edited to fit the original file.
And only after this last step (editing the wp-config!) the website worked like before! It took 2 hours… which is great considering I spend about 50 hours last week troubleshooting.
Can’t tell you how happy I am to say: This topic is fixed! The problem was and will always be: the user! ??
- The topic ‘Checkout unm?glich, drehendes R?dchen und Fehlermeldung’ is closed to new replies.
