dogstalker

Note that reverting to the shortcodes on cart and checkout pages helped for me, but the “Paypal smart button” on the single product page did still hung trying to connect to paypal and so needed to delete it. Those having this issue might want to check if it works for you.

(Settings>Payments tab>Standard Payments tab).

Also initially also had issues deleting the established woocommerce blocks to add the shortcodes. I think activated the Woocommerce Blocks plugin allowed me to edit but can’t remember what the process was.

Hi – thanks so much for your reply. I discovered that it’s not firing twice so much as the pages appear to be loading more than once on mobile. I spoke to my host who initially thought it was an issue with my theme, and then they thought it was a caching issue on their end. They fixed the caching issue, which helped one page that kept reloading on mobile, but some (not all) other pages are still doing it. I’m still trying to solve the issue but just thought I’d pass it on in case someone else runs into something similar.

Thanks, again.

Thank you jkeysemg this helped me, too. I noticed there was no location chosen and was not able to choose one. I disconnected square through woocommerce and reconnected and it went through.

That was super helpful – thank you. I hadn’t been looking into the right place for the logs. Turns out it’s working as it should. I also had a 16 x 24 package in there with the same height. Guess you can pack 8 x 12s side by side in that package! It never occurred to me it would have done that.

Thanks again!

I tried that, but w3tc was installed on only one site and it had been disabled when I started to try to trouble shoot. What I ended up doing was deleting W3tc plugin as a precaution (and purged the cache) and deleted all three of the WF plugins plus the tables & data for all three sites on activation, and started from scratch.

My multisite has run successfully twice and hung up once when I was in debugging mode (perhaps a server thing), but no error. I will re-introduce W3tc soon. The other two sites also ran successfully. So hopefully, this fixed it and I will mark it as resolved.

Thank you for replies and responses. Very appreciated. Hopefully my experience will help someone else out. For anyone who runs into this same kind of problem, there is an option on the options page to do this – just make note your settings before you do.

Thanks again.

I tried that, but w3tc was installed on only one site and it had been disabled when I started to try to trouble shoot. What I ended up doing was deleting W3tc plugin as a precation (and purged the cache) and deleted all three of the WF plugins plus the tables & data for all three sites on activation, and started from scratch.

My multisite has run successfully twice and hung up once when I was in debugging mode (perhaps a server thing), but no error. I will re-introduce W3tc soon. The other two sites also ran successfully. So hopefully, this fixed it and I will mark it as resolved.

Thank you for replies and responses. Very appreciated. Hopefully my experience will help someone else out. For anyone who runs into this same kind of problem, there is an option on the options page to do this – just make note your settings before you do.

Thanks again.

Thanks for this, but no luck. I contacted my host about it, they’re the ones that actually added the both codes to the .htaccess file. They weren’t able to get the scans to finish either. I just emailed you the log again. Not sure if that helps.

Done. Thank you!

Thank you. Sorry for the length, I was trying to provide all relevant details.

I set “Maximum execution time for each scan stage” to 20 and enabled “Start all scans remotely” on a non-multisite, and ran into the same error.

Wordfence version 6.3.6

Plugins that are installed and activated plugins on this site are:
-Contact Form 7
-Google Analytics for WordPress by MonsterInsights
-Jetpack
-NextGEN Gallery

EDIT: I’m sorry I didn’t see the previous message before I wrote this. Trying your suggestion now.

I’ve tried adjusting the “Maximum execution time for each scan stage” to 15 (and blank, and 20 and 240). I’ve checked with my host and they don’t think there any server updates around the time it stopped working. I see now that the three sites stopped scanning at different times, I thought they were all around October, but one was in late September. I also forgot to mention that I deactivated the current theme except for 2016 as well as all the plugins besides Wordfence and tested it that. Still getting the errors.
I’m submitting a ticket to their tech support. If you can think of anything else, please let me know. Thanks!

• This reply was modified 7 years, 11 months ago by dogstalker.

Thank you for responding so quickly! They did it for me, but the problem wasn’t resolved and they assume the problem is with woocommerce so there isn’t much I can do. Thankfully I was able to roll back the site to a previous version!

Thanks for the reply. Yes, I have WF installed on the other two websites (they are not multisites), and none are finishing. However, I just had a look on the multisite activity log and saw this error when it automatically started up the scan earlier this morning:

“Wordfence could not find a saved cron key to start the scan so assuming it started and exiting.”

Perhaps that sheds some light? I’ve seen it before, but I thought it was because I had been running scans because it wasn’t consistent.

• This reply was modified 7 years, 11 months ago by dogstalker.
• This reply was modified 7 years, 11 months ago by dogstalker.

Thank you – I will try that!

After awhile I reloaded the page and the bucket turned up. So.. until I see if eveything gets migrated, I would mark this resolved.

I am also experiencing this on my sites and with the exception of one, updated by wordpress.

Wordfence scans plugin files and compares them against the repository versions for changes. One example of the difference between the so-called original version (presumably what is in the repository) does not have: 'avoid_wp_cron' => true, on line 22 of jetpack/sync/class.jetpack-sync-settings.php that is in the version of my file on my server.

Wordfence states in their info that “some developers do not follow the official guidelines that WordPress provides for plugin developers and will modify a “tag” or a version of their plugin that has already been released by adding new code to an existing release. They do this by checking in code into a “tag” into the repository. The result is that this leaves customers with a released version with code that does not match what is in the repository.”

Maybe that helps?

• This reply was modified 8 years, 4 months ago by dogstalker.