Event Calendar improvements

Author Message

paul bolger

Wednesday 04 May 2011 5:57:42 pm

As a suggestion, could we have some improvements to the Event Calendar please?

At present the 'event' class can only handle events which have a set start and end time. It'd be nice to be able to stipulate 'all day' events, and to be able to enter limited recurring events (take a look at Google Calendar to see some of the possibilities: events that occur fortnightly for the next 13 weeks etc.

I realise that adding these features isn't that difficult, and I have extended the Calendar in the past, but wouldn't it be good for an eZ staff developer to spend a couple of days bringing this into line with what users expect out of an online calendar?

Paul Bolger

Quoc Huy Nguyen Dinh

Thursday 05 May 2011 2:57:15 am

You could maybe fork the GIT repository of eZ and request a pull. This would help eZ staff developers as they have a lot to work on already and if you already have done the improvements then it will save a lot of time.

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 18 2025 00:52:52
Script start
Timing: Jan 18 2025 00:52:52
Module start 'layout'
Timing: Jan 18 2025 00:52:52
Module start 'content'
Timing: Jan 18 2025 00:52:53
Module end 'content'
Timing: Jan 18 2025 00:52:53
Script end

Main resources:

Total runtime1.0156 sec
Peak memory usage4,096.0000 KB
Database Queries54

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0103 594.9063152.6250
Module start 'layout' 0.01030.0080 747.531339.4531
Module start 'content' 0.01830.9953 786.9844532.1484
Module end 'content' 1.01360.0020 1,319.13288.1641
Script end 1.0155  1,327.2969 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.00310.3016160.0002
Check MTime0.00130.1244160.0001
Mysql Total
Database connection0.00300.295010.0030
Mysqli_queries0.970895.5901540.0180
Looping result0.00050.0466520.0000
Template Total0.968795.420.4844
Template load0.00230.222120.0011
Template processing0.966495.162020.4832
Template load and register function0.00010.012210.0001
states
state_id_array0.00140.142110.0014
state_identifier_array0.00190.185020.0009
Override
Cache load0.00140.1399100.0001
Sytem overhead
Fetch class attribute can translate value0.00060.060920.0003
Fetch class attribute name0.00120.122340.0003
XML
Image XML parsing0.00130.124420.0006
class_abstraction
Instantiating content class attribute0.00000.000840.0000
General
dbfile0.00100.0983240.0000
String conversion0.00000.000740.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1node/view/full.tplfull/forum_topic.tplextension/sevenx/design/simple/override/templates/full/forum_topic.tplEdit templateOverride template
2content/datatype/view/ezimage.tpl<No override>extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tplEdit templateOverride template
2content/datatype/view/ezxmltext.tpl<No override>extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tplEdit templateOverride template
2content/datatype/view/ezxmltags/paragraph.tpl<No override>extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tplEdit templateOverride template
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 8
 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs