Report bugs for Out of Games.
Trying to import the using the JSON importer fails every time. Sometimes I get a cloudflare warning and I have to log back in.
// join_the_conversation
Sign in to share your thoughts, vote on comments, and connect with the community.
Trying to import the using the JSON importer fails every time. Sometimes I get a cloudflare warning and I have to log back in.
Are you using HSTD on Windows? If so, I'd recommend using our Plugin
https://outof.cards/hearthstone/decktracker-plugin/
It eliminates the hassle of the manual work involved in updating a collection, even if it is just copy-pasting a blob of JSON.
I'll have to dig deeper into exactly what is failing with it though. Cloudflare error is kinda weird, if it happens again I'd love the exact error you're getting and the code that comes with it so it can be referenced in logs.
It definitely should not be logging you out though, it makes me think you're being redirected to the generic server error page which does not contain any login data on it. If you go back to the homepage (or any page) from a server error page, you should be able to use the site as normal.
I gave up on any self-management of my personal computer years ago. Went from duel boot Windows+Linux to Apple. One of the reasons for playing HS. It works on my 6 year old laptop.
You are right about the logging out thing - that's an anomaly.
The sequence I follow, consistently is:
Here's an error heading:
Ray ID: 639ccb0a0dc45415 • 2021-04-02 20:26:36 UTC
I've made some rather large changes to how we're dealing with these now and we shouldn't see any more cloudflare errors due to timeouts.
When you submit JSON, it is now destructive - anything not in your string is going to be removed from your collection if it previously existed. This was something we were missing for a long time and I'm happy to announce has changed.
Your collection will also now be queued without your browsing waiting for a response on its status. We update your local collection immediately based on the data submitted and then we store a copy when our queue has time to do so. There could be a potential issue during high site load where you will be browsing and we'll send you an old copy of your collection, but that should be quite rare and fixed shortly after as the details process on our end.
Previously we had two different systems for updates, the one that runs for deck tracking clients and the manual input here, now they both use the same system.
Works well.
It is a little disconcerting that there's a notification for queuing, but nothing on completion. But, it is pretty obvious when you go back to viewing specific decks.
Thanks! :)
Leave a Comment