Dave Loodts

I guess this is more a support question for the thema author.
Or install the Troubleshooting plugin first to deactivate the plugins and see if the title is again visible. Then you’ll find the plugin that conflicts.

Hi, via woocommerce settings => Products you see the “shop page”; probably that is now store-page. Just fill in there the homepage.

But a better approach is to leave the setting open, select no page. But create the homepage with the WooCommerce blocks in the Gutenberg editor.

Hi, probably there is a conflict with another plugin or your theme. So, WooCommerce could show the error, but in the end it can be caused by another thing.

Do install the Troubleshooting & Healt plugin.
If you can’t install anything, log in via FTP and go to the folder wp-content/plugin and rename it temporarely to wp-content/plugins-OUT.
Log back in and then rename it back.

Good luck!

The easiest (and probably best) solution here is to point to a zip-file that’s on your dropbox. So, 1 ZIP-file that contains all your stuff; could be even with a read-first.doc file. Seen at a customer of mine, works great and no battling with folders or multiple links.

Hi, are you referring to the unauthentification notification?
You can ignore that. Some security plugins mentions this as an ‘issue’, others don’t. I guess there is still some debate, but from what i am aware of; it’s not immediatly a major problem.

Thanks!

This is really really custom coding. And not really that fast to explain via this forum, certainly if you want a seperate UI to add states.
About the App-request: i’m my opinion it’s undoable without even building a new app. You could also use an sms-service like Twilio that sends out an sms when a new order is passed.

I would just go for two receivers; so entering both mailadresses in the Woocommerce -> settings -> E-Mail. Cause if they login as an “admin” they see “each others” orders anyway. And they need be logged in probably to complete the order.

Double entry of ticket: this is the original:
https://www.ads-software.com/support/topic/multisite-db-call-error/

I believe it’s better to ask support at Gravity Forms, as this is a Premium plugin and this forum is not supporting questions on that part.

Besides that i can advice you first to scan your site with a security plugin,like for eample wordfence. Cause it is indeed strange. I’m a 10y Gravity Form user, never had issues like that. So, yes: check at Gravity Forms, their support is great.

There are some things you can do like:

• check your site via gtmetrix.com; check the waterfull; any big files?
• right click mouse in chrome browser and see if there are any errors
• install a caching plugin
• install a imag compression plugin
• install the plugin Query Monitoring, which also indicates which plugins or elementor potentially slow it all down
  

Check the “WooCommerce Cart Abandonment Recovery” of Cartflows to do that. However be aware (certainly for european consumers) that this practice is not GDPR compliant. So, using it without less risks is how good your bound is with your customer.
But another question you could ask: is there a potential reason why people abondon: unclear shipping costs, unclear return conditions, asking tou much info in the checkout that is not needed; like phone number.

By the way: this isn’t really the forum place to ask this question. This forum is about WordPress, not WooCommerce. But i hope you have an idea with my answer.

Seems alright by my when i downsize my browsers. Could a local issue with browser cache. Try another browser. Same result?

I guess this is not really a WooCommerce thing but WordPress theme thing. As you are using (seems like) a Premium Theme called Gecko, try to ask it to the Theme Author over there.

I can’t see the cookie banner/popup. I guess the plugin is already deactivated. If you want to find out which plugin caused some trouble, just use the official Troubleshooting plugin.

Auwh, that is a real mess. For bigger sites such as that probably is, first always take a backup. I would advice to make one via WPCLI; the command wp db export

Since it’s very hard to differentiate the injected “bad” posts to the real posts; i guess it’s nothing else then doing the manual labour. Or otherwise reinstall a previous backup.

Another thing you can do: create now a new staging copy site; and test out your own solution; which could be okay in some ways. But when you’re a bit unsure; do test that on staging.

Good luck!