richsadams

I had the same warning as @abigailm from WordFence: “Unknown file in WordPress core: wp-admin/fw_filesindex.php”. I also found the “fw_files” folder @catr noted above.

Per your directions I removed the “fw_filesindex.php” file as well as the “fw_files” folder.

I used the link to download the updated file. However your instructions say to “Find the plugin “Spam Protection by CleanTalk”. I do not have a plugin by that name.

I do have the paid plugin “Anti-Spam by CleanTalk”. Are they one in the same? Is it safe to deactivate and delete that plugin and install the new “CleanTalk-spam-protect” plugin file I downloaded?

TIA!

• This reply was modified 3 years, 2 months ago by richsadams. Reason: Typo

@webguyjon79, glad it’s working for you now.

FWIW this particular client site is on SiteGround where you can create staging sites by cloning the live site. I test everything out on the staging site before implementing it.

Here’s a good article about creating staging sites if your host provider doesn’t offer it:

https://www.wpbeginner.com/wp-tutorials/how-to-create-staging-environment-for-a-wordpress-site/

@pluggabl, success! I updated to Version 5.4.6 on the staging site, placed five separate orders and the “Order Numbers” sequential order numbering is now working as expected.

Thank you very much for the prompt support!

BTW, the good news is that Track Sales Add-on appears to be working as expected after testing it on my client’s live site. No idea why it didn’t work on the staging site, but I’m just glad it’s working normally in the live environment now.

Thank you.

@webguyjon79, just as an FYI, I was testing Booster’s “sequential orders” and some other modules to see if Booster could replace some existing plugins including the “Custom Order Numbers for WooCommerce” plugin on a staging site. That’s when I ran into the sequential order number issue. The staging site is also on WC v5.6.0.

The “Custom Order Numbers for WooCommerce” plugin is working normally on my client’s live site so it looks like an issue with the Booster plugin, possibly triggered by the latest version of W.C.?

Apologies, my client did not forward your initial response. I have it now. However I am unable to log into your HelpDesk to reply to the ticket. I created a new thread regarding that.

Thank you.

I created a second support ticket for the paid add-on but have not received any reply.

I don’t plan on removing the plugin at this time, but it would be valuable to know how.

TIA!

Even just adding some type of date filter would be helpful.

Thank you @rayrutjes, your time and consideration are truly appreciated.

Thank you very much for the quick reply @rayrutjes!

I would also like to know the answer to this question. However the developers haven’t answered in over two months and the plugin hasn’t been updated in over 9 months.

I’m wondering if this plugin abandoned?

Thanks, all good info @mtg169. I may give an MU plugin a shot and see how it goes. ??

Thanks also to @mtg169 Code Snippets is a “go to” plugin but I only use it on staging sites and then most often to locate the string I’d like to modify. Then I head to the original files to see what can be accomplished behind the scenes.

As mentioned above, I’m leery about adding plugins that can do serious harm by others that have access, even unintentionally. I know I could hide it from other Admins – with yet another plugin – but I tend to prefer keeping customizations under the hood for the most part.

If I get hit by a bus a decent developer should be able to sort out what I’ve done inside the child theme’s files. I always, always add an explanation to all coding for those that follow plus every client has a “Tweaks” file to pass along.

Thanks again and welcome any other insights!

• This reply was modified 3 years, 6 months ago by richsadams.

Thanks @gabrielfuentes for the advice and link to the interesting article. I think I’ve read its evil twin… “Use as few plugins as possible”. ??

Over the years, I think like you, I’ve developed a more-or-less hybrid work ethic since I’ve been burned by ill-formed plugins or outright abandonment as well as poor code scripts, snippets and choices.

In general I’ve tried to follow the golden rule, “don’t mess with core files”, period. I’ve stuck to that for the most part but Woocommerce is a bit of a different animal. Some of the files date back years while others are updated more often. That’s always the worrisome element. Customizing leaves the site vulnerable to updates not only by the devs, of WC in this case, but other plugins and site code updates that can, through no one’s fault directly, interact and break small things or the entire site.

So I’m a firm believer in child themes and keeping things as simple as possible. But let’s face it, WC is not a simple plugin by any measure. It’s great but can be a challenge when it comes to making it do what a client would like.

Thanks again, much appreciated!

• This reply was modified 3 years, 6 months ago by richsadams. Reason: Typo
• This reply was modified 3 years, 6 months ago by richsadams.
• This reply was modified 3 years, 6 months ago by richsadams.

Apologies for not replying to this thread sooner Robert. Your reply must have gotten lost on my end.

I’m currently running WP version: 5.7.2 and Woocommerce Version 5.3.0 and all are running without any issues.

Thank you again for your time, it’s truly appreciated.