Synch secondary to primary error
-
Just setting up free version before moving to Pro – our primary to secondary test connection is OK but secondary to primary fails with this error
<p>The document has moved <a href=”https://www.yoggiebear.nz/wp-json/wc/v2/?consumer_key=invalid&consumer_secret=invalid”>here</a>.</p>
I see it mentions the invalid key so on primary, I deleted the original and created a new rest API connection (twice actually) with the same result.
Any ideas?
Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)
- The topic ‘Synch secondary to primary error’ is closed to new replies.