Repeating Events/Caledar Items

Next topic

Author	Message
Jim Thaxton	Tuesday 21 October 2008 2:34:06 pm I am relatively new to using ez Publish, but have experience with other CMS products and work with a solid team of developers who are more familiair with ez Publish. I am working on a university project and they would like to have repeating events, specifically for student seminars and symposiums. I was wondering how others have tackled repeating events. Most other CMS tools I have used have some repeating event functionality, or we rolled it by hand. Esentially, we always created distinct objects (or nodes in ez terms) for each event as determined by the repeating criteria, for example, every Monday for the next 4 weeks, etc. Are there other approaches or tactics that might be more useful in ez Publish? It would be great to hear what other groups have tried and where their successes have been and what pieces are tougher. I assume an ez Component will be put together to handle the repeating events, but if this wheel has already been invented, I'd love to reuse existing work or help improve any current projects. Thanks in advance! --Jim Thaxton Senior Developer Duo Consulting Web Developer Coupon Cabin Chicago, IL
Łukasz Serwatka	Tuesday 21 October 2008 4:14:58 pm Hi Jim and welcome to the eZ Publish Community! It should be easy to enhance ezwebin calendar functionality without involving any extra libs. Everything you can solve using eZ Publish tpl language. I would enhance a event class from Website Interface by adding repeat option then on tpl level do some logic for repeating events. Data you can fetch from DB using eZ Publish fetch functions. http://ez.no/doc/ez_publish/technical_manual/4_0/reference/template_fetch_functions Personal website -> http://serwatka.net Blog (about eZ Publish) -> http://serwatka.net/blog

Author

Message

Tuesday 21 October 2008 2:34:06 pm

I am relatively new to using ez Publish, but have experience with other CMS products and work with a solid team of developers who are more familiair with ez Publish.

I am working on a university project and they would like to have repeating events, specifically for student seminars and symposiums. I was wondering how others have tackled repeating events. Most other CMS tools I have used have some repeating event functionality, or we rolled it by hand. Esentially, we always created distinct objects (or nodes in ez terms) for each event as determined by the repeating criteria, for example, every Monday for the next 4 weeks, etc.

Are there other approaches or tactics that might be more useful in ez Publish? It would be great to hear what other groups have tried and where their successes have been and what pieces are tougher.

I assume an ez Component will be put together to handle the repeating events, but if this wheel has already been invented, I'd love to reuse existing work or help improve any current projects.

Thanks in advance!
--Jim Thaxton
Senior Developer
Duo Consulting

Web Developer
Coupon Cabin
Chicago, IL

Łukasz Serwatka

Tuesday 21 October 2008 4:14:58 pm

Hi Jim and welcome to the eZ Publish Community!

It should be easy to enhance ezwebin calendar functionality without involving any extra libs. Everything you can solve using eZ Publish tpl language. I would enhance a event class from Website Interface by adding repeat option then on tpl level do some logic for repeating events. Data you can fetch from DB using eZ Publish fetch functions.

http://ez.no/doc/ez_publish/technical_manual/4_0/reference/template_fetch_functions

Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog

eZ debug

Timing:	Jan 18 2025 21:17:01
Script start
Timing:	Jan 18 2025 21:17:01
Module start 'layout'
Timing:	Jan 18 2025 21:17:01
Module start 'content'
Timing:	Jan 18 2025 21:17:03
Module end 'content'
Timing:	Jan 18 2025 21:17:03
Script end

Main resources:

Total runtime	2.0726 sec
Peak memory usage	4,096.0000 KB
Database Queries	54

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0088	589.0469	152.6250
Module start 'layout'	0.0088	0.0040	741.6719	39.4609
Module start 'content'	0.0128	2.0582	781.1328	526.7188
Module end 'content'	2.0710	0.0015	1,307.8516	8.3203
Script end	2.0725		1,316.1719

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0039	0.1899	16	0.0002
Check MTime	0.0017	0.0830	16	0.0001
Mysql Total
Database connection	0.0017	0.0842	1	0.0017
Mysqli_queries	2.0221	97.5638	54	0.0374
Looping result	0.0006	0.0302	52	0.0000
Template Total	2.0243	97.7	2	1.0122
Template load	0.0020	0.0941	2	0.0010
Template processing	2.0224	97.5791	2	1.0112
Template load and register function	0.0002	0.0080	1	0.0002
states
state_id_array	0.0010	0.0503	1	0.0010
state_identifier_array	0.0022	0.1074	2	0.0011
Override
Cache load	0.0016	0.0767	16	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0010	0.0494	2	0.0005
Fetch class attribute name	0.0016	0.0764	3	0.0005
XML
Image XML parsing	0.0008	0.0392	2	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0009	3	0.0000
General
dbfile	0.0009	0.0447	18	0.0001
String conversion	0.0000	0.0004	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
2	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
3	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 9 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs