Google calendar manages your homepage

Previous topic

Developer

Next topic

Author	Message
Philipp Kamps	Friday 06 October 2006 2:40:33 pm New extension: http://ez.no/community/contribs/hacks/googlescheduled The extension allows you to manage and schedule the content with your google calendar. It is not about scheduling the layout, neither scheduling the structure of the home page, but more simply about scheduling the contents that are placed in the placeholders defined in the home page. These placeholders called "zones" use a template fetch function that is accessing your google calendar to figure out what content supposed to be published at the very moment. In your Google Calendar you create appointment with the node_id in the title field. If the template function finds an appointment in your google calendar and can read a node_id it will show this node_id in your predefined "zones". In a configuration file you can specify fallback node_ids in case there is no appointment for the actual time. This extension is a prove-of-concept - it is not supposed to run in a productive environment in its current form. The extension contains an example "pagelayout.tpl" file that shows how to define a zone in your page layout. You may want to enable the caching once it is successfully running in your environment. INSTALL - enable the extension - configure "googlescheduled.ini" ( see inline doc) - have a look to "extension/googlescheduled/design/googlescheduled/templates/pagelayout.tpl" to define your zones - comment your feedback - have fun Please don't use the forum for feedback but the extension comments, thanks. http://www.mugo.ca Mugo Web, eZ Partner in Vancouver, Canada

Author

Message

Philipp Kamps

Friday 06 October 2006 2:40:33 pm

New extension:
http://ez.no/community/contribs/hacks/googlescheduled

The extension allows you to manage and schedule the content with your google calendar. It is not about scheduling the layout, neither scheduling the structure of the home page, but more simply about scheduling the contents that are placed in the placeholders defined in the home page. These placeholders called "zones" use a template fetch function that is accessing your google calendar to figure out what content supposed to be published at the very moment.
In your Google Calendar you create appointment with the node_id in the title field. If the template function finds an appointment in your google calendar and can read a node_id it will show this node_id in your predefined "zones". In a configuration file you can specify fallback node_ids in case there is no appointment for the actual time.

This extension is a prove-of-concept - it is not supposed to run in a productive environment in its current form.

The extension contains an example "pagelayout.tpl" file that shows how to define a zone in your page layout. You may want to enable the caching once it is successfully running in your environment.

INSTALL

- enable the extension
- configure "googlescheduled.ini"
( see inline doc)
- have a look to "extension/googlescheduled/design/googlescheduled/templates/pagelayout.tpl"
to define your zones
- comment your feedback
- have fun

Please don't use the forum for feedback but the extension comments, thanks.

http://www.mugo.ca
Mugo Web, eZ Partner in Vancouver, Canada

eZ debug

Timing:	Jan 18 2025 11:40:17
Script start
Timing:	Jan 18 2025 11:40:17
Module start 'layout'
Timing:	Jan 18 2025 11:40:17
Module start 'content'
Timing:	Jan 18 2025 11:40:18
Module end 'content'
Timing:	Jan 18 2025 11:40:18
Script end

Main resources:

Total runtime	0.7508 sec
Peak memory usage	4,096.0000 KB
Database Queries	46

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0054	589.7891	152.6250
Module start 'layout'	0.0054	0.0021	742.4141	39.4453
Module start 'content'	0.0075	0.7417	781.8594	470.9141
Module end 'content'	0.7492	0.0015	1,252.7734	8.1563
Script end	0.7507		1,260.9297

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0032	0.4282	16	0.0002
Check MTime	0.0014	0.1896	16	0.0001
Mysql Total
Database connection	0.0007	0.0869	1	0.0007
Mysqli_queries	0.7062	94.0624	46	0.0154
Looping result	0.0005	0.0607	44	0.0000
Template Total	0.7211	96.0	2	0.3605
Template load	0.0025	0.3301	2	0.0012
Template processing	0.7186	95.7103	2	0.3593
Template load and register function	0.0001	0.0135	1	0.0001
states
state_id_array	0.0014	0.1856	1	0.0014
state_identifier_array	0.0014	0.1923	2	0.0007
Override
Cache load	0.0021	0.2732	19	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0007	0.0975	1	0.0007
Fetch class attribute name	0.0008	0.1032	2	0.0004
XML
Image XML parsing	0.0006	0.0790	1	0.0006
class_abstraction
Instantiating content class attribute	0.0000	0.0005	2	0.0000
General
dbfile	0.0008	0.1116	15	0.0001
String conversion	0.0000	0.0010	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
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
3	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
3	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 10 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs