Get json object from asset listing

mahearn · 2012-07-01 01:12:49 UTC

Hi

I'm using an asset lister to make a json object from the assetids of the standard pages under a nominated root node. The result page of the asset lister returns the correct values:

{{"assetid":"134732"}, {"assetid":"134733"}, {"assetid":"146018"}, {"assetid":"146039"}, {"assetid":"146040"}, {"assetid":"146049"}, {"assetid":"146050"}, {"assetid":"146017"}}

but when I try to get these values returned from a jQuery getJSON call, it fails. My code is as follows:

    
    var getURL = "./?a=138204"; // Retrieve standard page assetids from asset lister (json format)
    		$.getJSON(getURL, function( data ){
    			$.each(data, function(key, val){
    				$('#listing').append(val + "");

    				console.log(val);
    			});
    		})
    		.error(function( ) { 
    				console.log("error");
    		});

I've checked permissions, and the page is accessible to public read. I've run out of ideas. Anyone?

nnhubbard · 2012-07-01 21:06:02 UTC

What do you see if you add an alert(data) inside of $.getJSON?

mahearn · 2012-07-01 21:52:52 UTC

[quote]
What do you see if you add an alert(data) inside of $.getJSON?

[/quote]

Hi Nick

data is not returned - no success - I'm just getting error.

nnhubbard · 2012-07-01 23:20:30 UTC

[quote]
Hi Nick

data is not returned - no success - I'm just getting error.

[/quote]

Are you sure that the ./?a= url style is getting converted to a real URL? I would use %globals_asset_url:138204% instead.

mahearn · 2012-07-01 23:25:13 UTC

[quote]
Are you sure that the ./?a= url style is getting converted to a real URL? I would use %globals_asset_url:138204% instead.

[/quote]

According to source, it is converting correctly, but jic, I tried the full URL, still no luck.

Put some error handling stuff in and getting this back, but not sure what is causing the "unexpected token":

200

SyntaxError

arguments: Array[1]

get message: function () { [native code] }

get stack: function () { [native code] }

set message: function () { [native code] }

set stack: function () { [native code] }

type: "unexpected_token"

proto: Error

Anthony_Barnes · 2012-07-01 23:43:41 UTC

[quote]
Put some error handling stuff in and getting this back, but not sure what is causing the "unexpected token":

[/quote]

Unexpected token means the json object is broken. In the sample you posted your nested objects don't contain a property. I would look at changing the format of your JSON, eg:

    
    {data: [{"assetid":"134732"}, {"assetid":"134733"}, {"assetid":"146018"}, {"assetid":"146039"}, {"assetid":"146040"}, {"assetid":"146049"}, {"assetid":"146050"}, {"assetid":"146017"}]}

mahearn · 2012-07-01 23:55:40 UTC

[quote]
Unexpected token means the json object is broken. In the sample you posted your nested objects don't contain a property. I would look at changing the format of your JSON, eg:

    
    {data: [{"assetid":"134732"}, {"assetid":"134733"}, {"assetid":"146018"}, {"assetid":"146039"}, {"assetid":"146040"}, {"assetid":"146049"}, {"assetid":"146050"}, {"assetid":"146017"}]}

[/quote]

Thanks Anthony, that sounds like the answer.

mahearn · 2012-07-02 00:02:50 UTC

Actually, to complicate matters, I've just noticed that the asset lister is returning html - I think this is the problem.

nnhubbard · 2012-07-02 04:38:21 UTC

[quote]
Actually, to complicate matters, I've just noticed that the asset lister is returning html - I think this is the problem.

[/quote]

Yeah, you need to apply a special Design asset to the listing. Basically a blank design with a json content type.

mahearn · 2012-07-02 05:12:21 UTC

[quote]
Yeah, you need to apply a special Design asset to the listing. Basically a blank design with a json content type.

[/quote]

Thanks Nick

I ended up nesting the asset listing inside a script tag and getting the object from the DOM. But I'll use your suggestion and try the xhr method again - much less complicated.

Michael

nnhubbard · 2012-07-02 18:07:38 UTC

[quote]
Thanks Nick

I ended up nesting the asset listing inside a script tag and getting the object from the DOM. But I'll use your suggestion and try the xhr method again - much less complicated.

Michael

[/quote]

Just use the following in your Design:

mahearn · 2012-07-03 00:09:35 UTC

[quote]
Just use the following in your Design:

[/quote]

Nic, we tried this and it still didn't work. The error indicates a "<" in the first index of the returned array.

This is a one-off script, so I'll stick with my nested content solution - don't have any time to stuff around.

It would be good to know why the other isn't working though, for future reference.

nnhubbard · 2012-07-03 00:12:55 UTC

[quote]
Nic, we tried this and it still didn't work. The error indicates a "<" in the first index of the returned array.

This is a one-off script, so I'll stick with my nested content solution - don't have any time to stuff around.

It would be good to know why the other isn't working though, for future reference.

[/quote]

Can you give me a link to the page?

mahearn · 2012-07-03 00:15:24 UTC

[quote]
Can you give me a link to the page?

[/quote]

Can't, it's on a server that's not yet publicly available - we're doing a website redev. I can supply source code from the browser if that helps.

nnhubbard · 2012-07-03 00:16:01 UTC

[quote]
Can't, it's on a server that's not yet publicly available - we're doing a website redev. I can supply source code from the browser if that helps.

[/quote]

Yeah, source would be great.

mahearn · 2012-07-03 00:35:08 UTC

[quote]
Yeah, source would be great.

[/quote]

I've just realised that the asset lister with the json in it doesn't have a url, as it's in a folder outside our new site asset. This may be why the getJSON method is failing.

M

nnhubbard · 2012-07-03 16:47:31 UTC

[quote]
I've just realised that the asset lister with the json in it doesn't have a url, as it's in a folder outside our new site asset. This may be why the getJSON method is failing.

M

[/quote]

Yeah, it needs a URL for it to work with that jQuery method.