Closed gilbitron closed 2 years ago
@patrickposner I've just had a look at your updates and the API key input still isn't quite right:
One other minor thing I noticed: the settings link in the "Uh oh" error message incorrectly uses "https://" for the URL on my localhost. I'm not sure how lsData.settings_url
is being populated, but it should use the URL scheme of the site.
One other thing I've just realised, the products dropdown in the block is loading all products across all of the Lemon Squeezy stores that belong to the user. I think we should add a second "stores" dropdown above the products dropdown if the API key has access to multiple stores. That way products can be filtered by store.
@patrickposner I've got the OAuth implementation ready for review now. So you should ignore my comment above regarding changes to the API key implementation and just review the OAuth PR #5 instead.
I close this now.
Added an issue for the store option here: #7
Hey @jamesckemp @patrickposner. After giving the plugin an initial once over, here are some of the things I think need fixed/improved before launch:
Also, once the API key has been successfully entered we should stop showing it to prevent other WP users logging in and being able to see/steal the API key. For this state, I suggest we replace the input with a read-only input that displays a blanked out key showing the last X chars (e.g.
****************1234
) and change the button to "Disconnect from Lemon Squeezy" or similar.