-
Thank you for the report. We identified a bug that impacts users with a significant number of devices wherein newly registered devices do not display properly. We are actively working on a fix and apologize for the inconvenience.
-
Thank you for the report. I confirm this behavior and we are working on a fix.
-
Thanks for the report! We are actively working to consolidate duplicate authors and publishers and to improve search results for both. We hope to have this project completed by the end of first quarter 2020; it involves reworking data for all of our products and resources. I agree that a search for "wipf & stock" should return the same results as a
-
[quote user="Mark Barnes"] [quote user="DAVID DIVELY"] So is there anyone anywhere that can verify purchases of Libronix programs in the past, specifically Ages Software? [/quote] If you synced your Libronix licences with the servers, then Faithlife will have a record of all your Libronix resources. [/quote] Note that we disabled the webservices (per
-
[quote user="MJ. Smith"]when parens appear to have no effect[/quote] This is a regression bug that we introduced when fixing search for product titles that explicitly have parentheses in them (e.g. `X Commentary Set (12 vols.)`). We'll have a fix out soon (hopefully tomorrow) so that advanced searching like `(John Piper) OR (Bible Study)` works again
-
[quote user="Kolen Cheung"] I see that it is now requiring authentication. Could you tell us what's the rate limit? [/quote] The rate limit is currently 4000 requests per hour for the GetMetadata route.
-
[quote user="Kolen Cheung"] Thanks for letting me know. I did try to find the limit and see there's 300 requests per minute from the Products API but not mentioned in ResourceMetadata API. Will it be ok if I limit it at the same rate (300 requests per minute)? [/quote] We'll probably set a rate limit much lower than 300 requests per minute in the near
-
[quote user="Kolen Cheung"] Thanks Mark again. I just started to use this and it is actually quite useful. The only bump I got is I spent almost an hour just to figure out resourceIds is something like 'LLS:EEC15EZR' not '24998' (which I assumed from the REST API...) [/quote] We appreciate your enthusiasm for our products and your desire to programmatically
-
Wishlists have been restored to full functionality.
-
Thanks. I fixed my original URL to no longer erroneously include a comma at the end.
-
As of this afternoon we have transitioned wishlists into a read-only state. You can view all of your wishlists at https://www.logos.com/account/wishlists but due to load on the site we are still disabling the ability to add anything to your wishlists from product pages and from search results. Thanks again for your patience and understanding.
-
Due to much higher load on our websites this week we have proactively disabled a few non-essential features, including wishlists. We plan to turn them back on again as soon as our systems are able. Thanks for your patience and understanding.
-
I suggest contacting Customer Service ( https://www.logos.com/contact ). They can confirm if the code you are trying to use on www.logos.com/redeem was previously used by another customer.
-
Mark, Thank you for your report. We detected and fixed an issue on mobile where some users were not able to access the latest version of the ESV Bible but were able to use the latest ESV audio. This made the audio be out of sync with the Bible. The Bible and audio should now be in sync for all users. If you have downloaded the ESV or ESV audio locally
-
The issue has been resolved. Please let us know if you still experience issues.
-
We've fixed the issue and are rolling out the fix to all affected users over the next twelve hours or so. You do not need to do anything to get the fix; it should download automatically. If anyone is still having issues at the close of business hours tomorrow (3/8) please let us know.