That isn’t a rule within the CSS we are serving up.
You may want to try the page without an extensions loaded, it seems like one might be injecting CSS & breaking the page for you.
That isn’t a rule within the CSS we are serving up.
You may want to try the page without an extensions loaded, it seems like one might be injecting CSS & breaking the page for you.
This is now fixed. I apologize again for the outage!
We have the new cert but ran into some issues getting it installed tonight. Everybody’s pretty beat so it’ll go in as soon as we can tomorrow.
Sorry, this got missed in our checklists of places to updated certs. We’ll make sure it doesn’t happen again.
We’re still trying to figure out what the plan will be going forward. Nothing to report yet.
This did remind me to go rip through the whitelisting queue though, I’ll try to get to that more regularly from here on out.
Sorry, I didn’t get the memo that the world linking was updating. EU updated (I needed to update NA slightly before reset as well, sorry)
This should be correct now, but some users are still seeing old values. Will investigate further when we get a chance.
I’m whitelisting things when I remember. Ping me in gitter if it’s been a day or so and I haven’t gotten to it.
Sorry about the delay on the tiles. The process for updating them is complicated and Lawton’s the only one w/ his machine correctly configured to update them atm.
This has been fixed.
This should be fixed, thanks for letting us know & sorry for the trouble!
Still a somewhat manual process to whitelist new items (in an attempt to prevent spoilers/datamining ourselves). Sorry for the delay, Friday was a really odd day here!
We were asked to discontinue OAuth2 due to phishing concerns. It won’t be coming back in the foreseeable future.
It’s a manual process and we were all up very late. Give it some time please.
Long story short: they are very aware about the issue and are also annoyed by it, but they haven’t been able to fix it or change it because they used a third party software that’s no longer supported, and no one there was able or had chances to learn how stuff works in order to be able to fix it.
This is correct. It would take substantial time to fix and it’s not a priority for the company right now.
Sorry, I wish search worked better too.
We’ve got low-priority plans to offer an API endpoint for it, just for consistency’s sake. That way if the timers do ever change in content there’s an always-up-to-date version in a consistent spot providing machine-readable values.
Low, LOW priority though.
DB servers backing the Trading Post were having some issues, we took the TP down while working on it. Should be fixed now.
Got the ok to expose the data, won’t have future sales or anything and may be missing a few items if we can’t come up w/ a good way to represent them.
This data is super-easy to get, so shouldn’t take long. I’ll try to get a PR together at some point.
Asking around to see how people feel about exposing that data.
Working for me currently, still broken for you?
APIs will be only providing read actions for the foreseeable future.
Sorry gang, I checked internally and this isn’t something ArenaNet is interested in offering at this time.
It’s not. Anything we built like that would lose all your settings after each patch at the moment like Evon Gnashblade mode. Each option also increases the development/testing time exponentially and it’s not something we’re able to support with our current workload.
The decision on those sorts of questions is out of our hands, and the decision on that is no.
Sorry, we’ll do the best we can within the constraints we’re under.
Auto-focus was a workaround for some technical limitations that we believe are fixed, so yes, we should be able to remove it sometime here.
Easier to fix than expected, these should be good now. Fixes may take a few minutes to show up.
Should be fixed, may take a few minutes to show up.
Nice catch, not sure where those bits wandered off too. We’re investigating.
The scroll position changing may or may not be fixable, there’s a not-particularly-interesting-but-deeply-technical reason why that is happening. We’ve mitigated it as much as we could in the short term in order to prioritize getting the TP UI fast again. We’ll swing back around and take another stab at it now that the bulk of the optimization work is sorted.
Glad you noticed, sorry it took a bit. We’ve been heads-down on HOT stuff and finally got some space to go spelunking into the changes since v2.0 shipped to figure out what had happened.
Hooray for fixing issues we caused! XD
Glad it’s working better for you now.
Shadowblade, send an email to support@arena.net with the subject “GW2 App blocked by Google” and a copy of your initial forum post and they’ll try to get you sorted.
Sorry for the trouble, our legal team will be working to clarify the TOSes for this sort of situation so it should get better in the future!
Hey gang, I’ve raised this question internally to try to get some clarification on the situation.
It looks ok to me from this machine, have you tried clearing your cache or trying it on your phone to rule out ISP strangeness?
Pro debugging tips shadow, couldn’t have said it better myself!
None of this sounds like TP-specific issues and seems more indicative of general computer slowness/difficulty running GW2. Due to how the BLTC dialog works it’s more susceptible to computer resource starvation than other game UI, so it’ll often be the first place you notice slowdown.
Contact support if you really lost gold/items, but in general as others have said it’ll be waiting for you in the delivery box.
As a temporary workaround try going to https://account.arena.net and logging out first, then logging in again via the forums.
Hey there, I’m just here to let you know the authenticated APIs are not working properly since the new build came out:
{"text":"ErrBadData"}
Edit: Seems to be working again
Hotfixes tend to break the APIs for a bit, we’re working on it
hot.staticwars.com isn’t served over HTTPS, unlike most of our *.staticwars.com domains. That’s what is tripping up HTTPS Everywhere.
Unfortunately that isn’t an easy fix on our end, so your best bet is probably to disable HTTPS Everywhere on heartofthorns.guildwars2.com
Ugh, sorry this slipped through. Working on this now.
Working on this, sorry for the delay.
I know it seems like we’ve forgotten about the APIs from time to time, but I promise we haven’t. Some of this data is just a real adventure to get into usable form that we can expose!
Should be fixed now, sorry about that. Underlying platform supplying the data changed behavior a bit and the web code needed a minor change to get the request to the right spot.
Maybe you can remove the [Beta] tag from it too while you are at it, it is literally been out for over 3 years now…
We don’t have the source art, and it’s baked into the image alongside the text because custom font loading wasn’t reliable at that time. I’ve looked at it a few times and it isn’t worth making the title look like garbage.
When was the last time the HOM successfully looked up a character for you?
Looking into this, thanks for the heads-up.
A server deploy changed some behind-the-scenes behaviors which means any keys older than about mid-July are broken. Server programmer is working on a fix, but in the mean time newly-created keys should be fine.
Sorry for the hassle
We’re taking a look.
Looks like page_size does indeed work. Thanks! Didn’t think to try it since it wasn’t in the docs.
http://wiki.guildwars2.com/wiki/API:2 mentions it (& is generally a more-useful resource than the API landing pages anyways)
Not affiliated with ArenaNet or NCSOFT. No support is provided.
All assets, page layout, visual style belong to ArenaNet and are used solely to replicate the original design and preserve the original look and feel.
Contact /u/e-scrape-artist on reddit if you encounter a bug.