series/show.xml returning escaped XML

[Israel]

The series info call is returning escaped xml which makes parsing difficult :). The "work" node looks like the culprit with all the tags surrounded by lt; and gt; entities.

[Dariusz]

Wow, after two years this bug is still unresolved.

I just started working on some useful tool for GoodReads (in my opinion of course), but one request per second limit and api bugs not resolved for two years (yep, I found it too) sounds discouragingly.

[[deleted user]]

Hi Israel and Dariusz,

Sorry to hear you're having issues. Can you give me the exact endpoint you're hitting, with work/book id params included, where you're seeing this error? I'll look into what's happening.

-Nichole

[Dariusz]

Hi Nichole,

Please check sample url from api documentation for series.show function (https://www.goodreads.com/series/4032...), when you look at source of response you will see that whole "work" item is html-encoded. So response is not well-formed xml.

[[deleted user]]

Dariusz,

Thanks so much for the link...yeah that does look pretty wonky. I'm filing a ticket for this (for our reference, IOS-2520). We'll try to fit this in soon and I'll update this ticket again when it's fixed.

[Dariusz]

No problem, I hope that issue will be solved soon.

[Dariusz]

Unfortunately I've noticed one more bug in this function - if user_position contains ampersand it is NOT encoded into entity. So parsing of that file is not possible. For example - https://www.goodreads.com/series/4095...

[Joshua]

I'm noticing the exact same thing. Hoping this will get resolved soon. It would be much easier to parse the data if it was pure XML.

[Ettore]

Dariusz, Joshua: I added your additional details to the ticket.

[Joshua]

I just thought I'd try the series XML call again, but I'm still getting the same issue. Is there any update on this?

[Jeff]

No update on this yet, we'll try to fit it into an upcoming sprint.

[[deleted user]]

Hi all,

Happy to announce that this bug should be fixed now. Let us know if that doesn't seem to be the case!

[Joshua]

Thanks! It looks like it's working now.