In your opinion, would it come soon enough I should wait? I can also see my customers needing to register for updates in three different ways this year annoying too.
I would wait, the new API doesn’t provide any easier methods for a buyer to verify their purchase. Just stick with the two current methods ( which are getting a user to register an API key to get the download url for updates, or getting a user to enter their purchase code to verify a purchase )
Now that this huge project of moving to a new API framework is done they can start building cooler stuff (like 1 click purchase verifications via oAuth without the need for buyers to enter purchase codes or API keys).
@ThemeBlvd yes this new API is the same as the old API – so in the same way as before (register an API key) the buyer will have to register a personal token.
However with the new API the user doesn’t really need to input their username, just the personal token.
Hopefully this is improved later on (so the buyer doesn’t have to register a personal token or anything, hopefully soon we can just let the buyer “Login” to authenticate their purchase and not worry about purchase codes or tokens or api) – they’re working on it
@Gewora returning with
?code= in URL is standard for oAuth (e.g. facebook login etc..)
it’s still possible to use rewrite, e.g.
overwriting the return URL is a security issue, hence not allowed with oAuth (e.g. facebook again).
Is there any way for someone on an Author Team to see a “dashboard” summary of recent item comments?
If an author team member doesn’t have any items, it seems to show this message instead of item comments.
It would be great if comments could be shown (instead of this message) if the user is part of a team.
EDIT Oh I see, the dashboard summary was never a feature of author teams, author team members still have to visit each item page to see if there are any new comments. +1 for pulling those comments into the dashboard.