search

jetbalsa / pos-tracker-eve

Automatically exported from code.google.com/p/pos-tracker-eve
0 stars 0 forks source link

Patch for /trunk/includes/class.pos.php #44

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Use 'break' so additional keys that are working can still be used. Consider 
changing error notification to append for multiple API errors.

Original issue reported on code.google.com by scott.mu...@gmail.com on 29 Sep 2011 at 7:55

Attachments:

GoogleCodeExporter commented 9 years ago 
The failure for a API pull because of a bad key was in sense on purpose so an 
admin would notice. Will dive into this at a late date and look into adding 
some messaging because otherwise cron users will never know of a bad API key 
with such a patch.

Original comment by frozenic...@gmail.com on 29 Sep 2011 at 11:23

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
A possible solution could be displaying the last time the API key was used 
successfully for each key listed in the admin panel. If the admin only uses 
updates via cron but notices a key hasn't been successful for over 24 hours, he 
could then look into it. I understand this would not give the reason for the 
failure. A manual update should provide that information though.

Original comment by scott.mu...@gmail.com on 7 Feb 2012 at 3:33