You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 13, 2023. It is now read-only.
Majority of the users we're going to get are not technical/devs by nature. We should not require anyone to have to view-source on anything to set up the necessary credentials for our plugin here. Creating the API key is going to be cumbersome enough, but that one I know we can't get around. What we can get around is retrieving the store ID.
I propose we move things to providing a field to provide the shop name. "EndlessSkys" for an example from the forums. What we do is use that, and make a request to the following API endpoint, and retrieve the store IDs ourselves.
Majority of the users we're going to get are not technical/devs by nature. We should not require anyone to have to view-source on anything to set up the necessary credentials for our plugin here. Creating the API key is going to be cumbersome enough, but that one I know we can't get around. What we can get around is retrieving the store ID.
I propose we move things to providing a field to provide the shop name. "EndlessSkys" for an example from the forums. What we do is use that, and make a request to the following API endpoint, and retrieve the store IDs ourselves.
From the returned results, we should be able to pluck out the appropriate ID, and save that to meta like we already would be with the CMB2 field.
After that, we carry on like we had been. I see enough issues come through related to the API requests, that we need to make it more straightforward.
The text was updated successfully, but these errors were encountered: