object name pattern and ezdatetime

Next topic

Author	Message
Mads Ovesen	Wednesday 21 December 2005 1:31:55 pm Hi, I have a class of meetings with (among others) a startdate attribute (ezdatetime). I have chosen the startdate combined with the header of the meeting as the object name pattern of the class. The problem is that ez returns this pattern as a datetime + header. For examlple: Wednesday 29 June 2005 2:00:00 pm Ph.d.-defense. In this way I cannot sort all the meetings in the backend by name, so that they appear a chronological order. Is there any way to remove the weekday name, so that they will be listed chronologically in the backend?? Thanks in advance! /m
Mads Ovesen	Wednesday 21 December 2005 2:16:30 pm Ok I solved this by overriding the folder.tpl in admin. All meetings must be children of a folder. I then check if the contentclass id of the children is that of the meeting class. If it is, I fetch the objects and sort them by the startdate attribute, else I sort them by $sort_array. Doesn't seem as the most elegant solution though. /m

Author

Message

Wednesday 21 December 2005 1:31:55 pm

Hi,

I have a class of meetings with (among others) a startdate attribute (ezdatetime). I have chosen the startdate combined with the header of the meeting as the object name pattern of the class. The problem is that ez returns this pattern as a datetime + header. For examlple:
Wednesday 29 June 2005 2:00:00 pm Ph.d.-defense. In this way I cannot sort all the meetings in the backend by name, so that they appear a chronological order. Is there any way to remove the weekday name, so that they will be listed chronologically in the backend??

Thanks in advance!

Mads Ovesen

Wednesday 21 December 2005 2:16:30 pm

Ok I solved this by overriding the folder.tpl in admin. All meetings must be children of a folder. I then check if the contentclass id of the children is that of the meeting class. If it is, I fetch the objects and sort them by the startdate attribute, else I sort them by $sort_array. Doesn't seem as the most elegant solution though.

eZ debug

Timing:	Jan 19 2025 07:20:00
Script start
Timing:	Jan 19 2025 07:20:00
Module start 'layout'
Timing:	Jan 19 2025 07:20:00
Module start 'content'
Timing:	Jan 19 2025 07:20:00
Module end 'content'
Timing:	Jan 19 2025 07:20:00
Script end

Main resources:

Total runtime	0.0264 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0079	589.2578	152.6250
Module start 'layout'	0.0079	0.0039	741.8828	39.4453
Module start 'content'	0.0119	0.0120	781.3281	89.2266
Module end 'content'	0.0239	0.0025	870.5547	30.3047
Script end	0.0263		900.8594

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0026	10.0066	14	0.0002
Check MTime	0.0012	4.5469	14	0.0001
Mysql Total
Database connection	0.0010	3.9842	1	0.0010
Mysqli_queries	0.0044	16.7627	3	0.0015
Looping result	0.0000	0.0724	1	0.0000
Template Total	0.0021	7.8	1	0.0021
Template load	0.0011	3.9878	1	0.0011
Template processing	0.0010	3.8168	1	0.0010
Override
Cache load	0.0006	2.3721	1	0.0006
General
dbfile	0.0003	1.0241	8	0.0000
String conversion	0.0000	0.1520	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