JSON feed of nodes

Next topic

Author	Message
Luigi Spagnolo	Monday 25 May 2009 11:42:29 am Since I have to integrate Simile Exhibit (http://www.simile-widgets.org/exhibit/ ) inside ezPublish 4, I need to obtain lists of nodes encoded in a custom JSON format. I looked for extensions already doing this task, but seems that the only one available (http://projects.ez.no/json) is not siutable for ezPublish 4.x. Can you confirm this? If so, can you suggest me what is the simplest way to obtain ez nodes encoded in JSON format? I've thought of introducing a view parameter "format" so that I would modify the pagelayout.tpl as follows: {if $view_parameters.format\|eq('json')} {* Display the content in JSON format using additional external templates if needed... } {else} { Display the content in xHTML, as usual... *} {/if} Is there a better solution, also for what concerns performance? Do you think is better to intervene on the tpl or creating a module in php? Thank you in advance
Gaetano Giunta	Monday 25 May 2009 1:49:31 pm The ggxmlview on projects.ez.no extension already provides a basis for creating json-formatting of nodes via the templating system. It can be taken as-is or as an example. You can of course use an {if} inside your pagelayout to switch to the desired output format, but I would rather a - set up a wildcard url-alias rule, so that eg. www.mysite.com/json/23 redirects to www.mysite.com/layout/set/json/content/view/json/23 b - use a different siteaccess, dedicated to json, where the default pagelayout and node_view_full templates are the json ones. This means you do not need to set up url-alias rules and will benefit from virtual urls The advantage is that - you keep your standard templates clean of json stuff - you can set up a proper content-type header for json content The thing you have to consider is the view-cache: by default only the full view of nodes benefits of it, so if you use a different view mode you will need to change your settings accordingly. Principal Consultant International Business Member of the Community Project Board
Luigi Spagnolo	Tuesday 26 May 2009 2:10:57 am Thank you very much for your precious suggestions. :)

Author

Message

Monday 25 May 2009 11:42:29 am

Since I have to integrate Simile Exhibit (http://www.simile-widgets.org/exhibit/ ) inside ezPublish 4, I need to obtain lists of nodes encoded in a custom JSON format.
I looked for extensions already doing this task, but seems that the only one available (http://projects.ez.no/json) is not siutable for ezPublish 4.x. Can you confirm this?

If so, can you suggest me what is the simplest way to obtain ez nodes encoded in JSON format?
I've thought of introducing a view parameter "format" so that I would modify the pagelayout.tpl as follows:

{if $view_parameters.format|eq('json')}
{* Display the content in JSON format using additional external templates if needed... *}

{else}
{* Display the content in xHTML, as usual... *}

{/if}

Is there a better solution, also for what concerns performance?
Do you think is better to intervene on the tpl or creating a module in php?

Thank you in advance

Gaetano Giunta

Monday 25 May 2009 1:49:31 pm

The ggxmlview on projects.ez.no extension already provides a basis for creating json-formatting of nodes via the templating system. It can be taken as-is or as an example.

You can of course use an {if} inside your pagelayout to switch to the desired output format, but I would rather
a - set up a wildcard url-alias rule, so that eg. www.mysite.com/json/23 redirects to www.mysite.com/layout/set/json/content/view/json/23
b - use a different siteaccess, dedicated to json, where the default pagelayout and node_view_full templates are the json ones. This means you do not need to set up url-alias rules and will benefit from virtual urls

The advantage is that
- you keep your standard templates clean of json stuff
- you can set up a proper content-type header for json content

The thing you have to consider is the view-cache: by default only the full view of nodes benefits of it, so if you use a different view mode you will need to change your settings accordingly.

Principal Consultant International Business
Member of the Community Project Board

Luigi Spagnolo

Tuesday 26 May 2009 2:10:57 am

Thank you very much for your precious suggestions. :)

eZ debug

Timing:	Jan 31 2025 01:25:23
Script start
Timing:	Jan 31 2025 01:25:23
Module start 'layout'
Timing:	Jan 31 2025 01:25:23
Module start 'content'
Timing:	Jan 31 2025 01:25:23
Module end 'content'
Timing:	Jan 31 2025 01:25:23
Script end

Main resources:

Total runtime	0.0222 sec
Peak memory usage	4,096.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0047	588.1094	151.1953
Module start 'layout'	0.0047	0.0041	739.3047	220.6563
Module start 'content'	0.0088	0.0119	959.9609	997.7734
Module end 'content'	0.0207	0.0014	1,957.7344	33.9922
Script end	0.0222		1,991.7266

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0025	11.1664	14	0.0002
Check MTime	0.0010	4.6460	14	0.0001
Mysql Total
Database connection	0.0006	2.6460	1	0.0006
Mysqli_queries	0.0024	10.9944	3	0.0008
Looping result	0.0000	0.0806	1	0.0000
Template Total	0.0010	4.6	1	0.0010
Template load	0.0008	3.6336	1	0.0008
Template processing	0.0002	0.8963	1	0.0002
Override
Cache load	0.0005	2.3494	1	0.0005
General
dbfile	0.0003	1.2574	8	0.0000
String conversion	0.0000	0.0451	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs