WooCommerce: My store fails the importing test
During the process to add a store to Metorik, you may run into an issue during the import's testing stage, where it tests that the keys Metorik has for your store actually work. This can happen for a number of reasons, but typically, it's due to either:
- You have no orders on your store. If so, try create a test/dummy order and it may work.
- Jetpack being installed but not set up completely. Deactivate it if you aren't using it.
- A security plugin blocking Metorik from accessing your site. Try deactivate any you have to see if that's the case - you can view more about this here.
- A plugin breaking the WooCommerce API on your site. Please see the list of plugins that break the WooCommerce API below.
- If you're entering your site with www., try removing it and enter it without www. Similarly, if you are entering your site without www., try enter it with www.
- We need your site to have HTTPS, as in some case's its the only way we can connect to your site. If you already have it, but it's a self-signed certificate, you may need to replace it with a proper functioning one. We recommend the free and best option - Let's Encrypt.
- Your server has PHP running as FCGI, as it can stop your server from understanding our requests. You can check with your host about this and try not using FCGI, but often this is fixed by your site having HTTPS, so that may be an easier solution.
It can be worth installing a plugin such as Error Log Monitor, or checking the PHP error logs, to see what errors are happening when Metorik tries to connect. This can help you figure out which plugin is causing the issue.
When in doubt, contact Metorik support and we'll walk you through it and solve any issues you're having.
Plugins that may cause issues
Try deactivating these plugins and then re-connecting your store to be sure
- Uptime Robot Plugin / Web Tracker plugin (breaks the WC API's endpoints - says unauthenticated when authenticated)
- Intense Plugin (breaks the WC API's products endpoint)
- Upload Quota per User (breaks the WC API's endpoints - says unauthenticated when authenticated)
- Flipbook plugin (breaks the WC API's products endpoint sometimes)
- JWT Authentication Plugin (breaks WooCommerce's built-in authentication)
- WPGraphQL JWT Authentication Plugin (breaks WooCommerce's built-in authentication, but this commit may fix it)
- The SEO Framework (breaks the WC API's products endpoint if you are using it to block products)
- Comet Cache Pro (breaks some WC API endpoints as it caches results even when new data is there - can be fixed by disabling their 'enforce canonical URLs setting')
- IconPress Plugin (breaks the entire WC API)
- Yoast SEO WooCommerce Addon (breaks the WC API's customers endpoint if a /customer/* regex is setup)
- Harrys Gravatar Cache (breaks the entire WC API)
- Password Protector
Firewall issues due to security plugins
You may run into an issue caused by a firewall on your end added by a security plugin.
If so, make sure that the WordPress API endpoints are not being blocked. In Sucuri for example, you can whitelist these endpoints like so:
The document was not found error
If you get an error saying "the document was not found" it is most likely due to your permalink settings in WordPress. WordPress comes "out of the box" using the "Plain" permalink structure, but in most cases you'll want to use the "Post name" structure. Head to your store's permalink settings and select the 'post name' structure:
Important: Ensure you've checked with your web team before changing your permalink structure. If you've got an established website and it's not using the "Post name" structure, there may be a deliberate reason for this. If you're unsure, click the chat icon and we can see if we can help.
This should solve the issue. If you are still seeing the error after, get in contact with us over email.