Invalid JSON response in library section

Dev Community Dev/API Corner
1

I have encountered a bug in the JSON response of a library section. The JSON response is not valid JSON, as there is a comma missing between two directories. I have encountered this issue in one section, but the other three sections do not have the same issue.

 

I cannot provide a reproduction plan due to this, however I have attached the HTTP request and response. My media server is always online and is attached to myPlex in case one of the administrators wishes to verify the issue. The section ID is 2.

 

The issue appears between "Petite Princess Yucie" and "Pita Ten". Search for "}{".

{"_elementType":"Directory","ratingKey":7154,"key":"/library/metadata/7154/children","type":"show","title":"Petite Princess Yucie","summary":"Welcome to the Petite Princess Yucie guide at TV Tome.
Seventeen year old Yucie can never be taken seriously.  How can she when, she's been cursed to trapped in a ten year olds body.  Bright, cheerful and optimistic, Yucie has never let her curse get in the way of living a happy life.  Her life is about to change forever when she becomes a candidate to become the Platina Princess, an honor which will allow her ultimate wish to be granted!  Then she finds out that she is one of many candidates, and the competition gets intense! Opening Song:  \"Egao no Tensai\" by Maria Yamamoto, Yuki Matsuoka, Yukari Fukui, Ayako Kawasumi, Fumiko Orikasa Ending Song:  \"Genius of Smiles\" by Puchipurizu","index":1,"year":2002,"thumb":"/library/metadata/7154/thumb/1342544980","art":"/library/metadata/7154/art/1342544980","duration":1800000,"originallyAvailableAt":"2002-09-01","leafCount":26,"viewedLeafCount":0,"addedAt":1335088797,"updatedAt":1342544980,"_children":[]}{"_elementType":"Directory","ratingKey":7806,"key":"/library/metadata/7806/children","type":"show","title":"Pita Ten"

 

Information:

Operating System: Windows 8 64-Bit
Plex Server Version: 0.9.7.22

 

Request (DeathServer is the local network name of the server):

GET /library/sections/2/all HTTP/1.0
User-Agent: Fiddler
Accept: application/json
Host: deathserver:32400

 

Response (Paste due to the size):

http://pastebin.com/8WGQeDkE

2

Indeed, we've seen this problem. We have an internal issue filed and will hopefully get it fixed soon. Thanks for the report!

P.S. Working on anything fun? :]

3

Indeed, we've seen this problem. We have an internal issue filed and will hopefully get it fixed soon. Thanks for the report!

P.S. Working on anything fun? :]

Ah that is good news! Thank you for the quick response. I'm currently playing around with a prototype to allow an export of your library to an online site. The idea is to let other people browse around in your library without exposing administrative functionality or having to have your server running. The idea is to, eventually, allow a library to be published to an online source with all metadata and activity information in a clear manner. The earliest prototype can be viewed at http://www.roelvanuden.nl/plex/ running on a basic Apache server on some cheap hosting. :)

4

This issue has not yet been resolved. right? When requesting, recently added then plex return invalid json as descriped in Deathspike's post.

Request: 
 

GET http://10.0.0.3:32400/library/onDeck HTTP/1.1
User-Agent: Fiddler
Accept: application/json
Host: 10.0.0.3:32400
 

I'm not experiencing any issue with other requests. it's seems only to be an issue with recentlyAdded.

Server is running version, 0.9.8.6.175-88ffbb2.

5

I get the same issue on the recently added section but onDeck works fine.

http://plex.server.ip:32400/library/recentlyAdded when using "{Accept: application/json}" header

6

i get a json error when viewing TV show info from /library/metadata/XXXXXX/children (XXXXX is any shows ID)

if the show has only one season the json works.. but if there is more than one season the json results is invalid

Oz

7

Any update on when this issue is going to be fixed?

I have the exact same issue as Deathspike.

{HOST}/library/recentlyAdded is invalid json. Several place are missing ',' so there are '{}' groups.

8

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.