Selection issue

Next topic

Author	Message
Rinze Cats	Wednesday 26 May 2004 9:01:02 am Hi, i have upgraded from 3.3.3 to 3.3.5. can someone tell if the following is the result of this upgrade, and if so, which file I have to edit to undo this change? My article class includes a selection attribute called 'issue'. This simply contains numbers indating the issue. I use this field in the objects name. So my articles appear as 16_articlename. This worked fine under 3.3.3. Now I have upgraded, the number displayed in the name is always one off. So if the issue is 15, 16 is displayed. I think this is because the id of the selection is used instead of the value (the selection starts with a blank, so the id / value has a difference of 1). However, i'm not sure! Has anybody experienced this or can someone tell me if there has been a change in this functionality? thanx rinze
Kåre Køhler Høvik	Thursday 27 May 2004 2:34:42 am Hi I think the selection datatype was fixed between 3.3-5 and 3.3-5. In 3.3-3 the index was : 0, 2, 3, 4, etc. In 3.3-5 it's fixed to : 0, 1, 2, 3, etc. -- Kåre Høvik Kåre Høvik
Rinze Cats	Friday 28 May 2004 3:12:29 am mmm, The class definition didn't change (of course), so when I open an existing instance of the class and view the source, the options are counting from 0, 2, 3, 4, 5 etc. If for existing classes index 14 was chosen, it would display the value related to index 14, say the string 'fourteen'. Howeverin 3.3.5, it will still load the index 14, but the display function uses a different count, and the index 14 is related to the next value, 'fifteen'. How can I solve this? Can I undo this fix (and if so which php file do I need to change?)

Author

Message

Wednesday 26 May 2004 9:01:02 am

Hi,

i have upgraded from 3.3.3 to 3.3.5. can someone tell if the following is the result of this upgrade, and if so, which file I have to edit to undo this change?

My article class includes a selection attribute called 'issue'. This simply contains numbers indating the issue. I use this field in the objects name. So my articles appear as
16_articlename. This worked fine under 3.3.3. Now I have upgraded, the number displayed in the name is always one off. So if the issue is 15, 16 is displayed. I think this is because the id of the selection is used instead of the value (the selection starts with a blank, so the id / value has a difference of 1). However, i'm not sure! Has anybody experienced this or can someone tell me if there has been a change in this functionality?

thanx
rinze

Kåre Køhler Høvik

Thursday 27 May 2004 2:34:42 am

I think the selection datatype was fixed between 3.3-5 and 3.3-5.

In 3.3-3 the index was : 0, 2, 3, 4, etc.
In 3.3-5 it's fixed to : 0, 1, 2, 3, etc.

--
Kåre Høvik

Kåre Høvik

Rinze Cats

Friday 28 May 2004 3:12:29 am

mmm,

The class definition didn't change (of course), so when I open an existing instance of the class and view the source, the options are counting from 0, 2, 3, 4, 5 etc.

If for existing classes index 14 was chosen, it would display the value related to index 14, say the string 'fourteen'. Howeverin 3.3.5, it will still load the index 14, but the display function uses a different count, and the index 14 is related to the next value, 'fifteen'.

How can I solve this? Can I undo this fix (and if so which php file do I need to change?)

eZ debug

Timing:	Jan 18 2025 19:32:19
Script start
Timing:	Jan 18 2025 19:32:19
Module start 'layout'
Timing:	Jan 18 2025 19:32:19
Module start 'content'
Timing:	Jan 18 2025 19:32:20
Module end 'content'
Timing:	Jan 18 2025 19:32:20
Script end

Main resources:

Total runtime	0.7768 sec
Peak memory usage	4,096.0000 KB
Database Queries	57

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0058	587.7891	152.6094
Module start 'layout'	0.0058	0.0029	740.3984	39.4141
Module start 'content'	0.0087	0.7665	779.8125	533.4063
Module end 'content'	0.7753	0.0015	1,313.2188	12.5078
Script end	0.7768		1,325.7266

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0033	0.4192	16	0.0002
Check MTime	0.0014	0.1823	16	0.0001
Mysql Total
Database connection	0.0011	0.1388	1	0.0011
Mysqli_queries	0.7279	93.7058	57	0.0128
Looping result	0.0006	0.0708	55	0.0000
Template Total	0.7434	95.7	2	0.3717
Template load	0.0020	0.2633	2	0.0010
Template processing	0.7413	95.4363	2	0.3707
Template load and register function	0.0002	0.0278	1	0.0002
states
state_id_array	0.0012	0.1500	1	0.0012
state_identifier_array	0.0010	0.1284	2	0.0005
Override
Cache load	0.0017	0.2208	22	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0006	0.0747	2	0.0003
Fetch class attribute name	0.0011	0.1370	4	0.0003
XML
Image XML parsing	0.0008	0.1062	2	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0014	4	0.0000
General
dbfile	0.0012	0.1592	15	0.0001
String conversion	0.0000	0.0013	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
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
7	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
4	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: 17 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs