ezidentifier

Next topic

Author	Message
Rene Sack	Friday 03 June 2005 5:33:31 am Hello! First of all greetz from Austria and thanks a lot for the new features in 3.6. Some things would make Administration much more easier. :-) But now we have some troubles with the ezidentifier at our company: As we had eZPublish 3.4.2 it was possible that the ezidentifier only counted, if a document was published. Now we moved to Version 3.6 and the ezidentifier is always counting. He is counting even if you save a document as a draft, and also after canceling a job. Now we can´t move our Database because for us it´s very important to get this feature running because every new published Articel should have an consecutive numbering (Document ID) Now we loose a lot of ID´s because of that problem. Our Question 1: Is this a bug. If yes how can we get this problem solved. Our Question 2: If this is this a wanted feature, where can I change this. In the ini Settings i didn´t find any possibility to change this. thanks in advance Greenvalley is waiting
Jan Borsodi	Monday 06 June 2005 12:28:15 am Re: Question 1: Is this a bug. It is not a bug, it was changed because the other behaviour gave other problems, such as not being able to use the attribute as title of the object. Re: Question 2: If this is this a wanted feature, where can I change this. There is not an INI setting for this as of now. However if you are really interested in this you should add a suggestion for it in the bug system, we can then have a look at it for one of the next 3.6 releases. -- Amos Documentation: http://ez.no/ez_publish/documentation FAQ: http://ez.no/ez_publish/documentation/faq

Author

Message

Friday 03 June 2005 5:33:31 am

Hello! First of all greetz from Austria and thanks a lot for the new features in 3.6. Some things would make Administration much more easier. :-) But now we have some troubles with the ezidentifier at our company:

As we had eZPublish 3.4.2 it was possible that the ezidentifier only counted, if a document was published.

Now we moved to Version 3.6 and the ezidentifier is always counting. He is counting even if you save a document as a draft, and also after canceling a job.

Now we can´t move our Database because for us it´s very important to get this feature running because every new published Articel should have an consecutive numbering (Document ID) Now we loose a lot of ID´s because of that problem.

Our Question 1: Is this a bug. If yes how can we get this problem solved.
Our Question 2: If this is this a wanted feature, where can I change this. In the ini Settings i didn´t find any possibility to change this.

thanks in advance

Greenvalley is waiting

Jan Borsodi

Monday 06 June 2005 12:28:15 am

Re: Question 1: Is this a bug.

It is not a bug, it was changed because the other behaviour gave other problems, such as not being able to use the attribute as title of the object.

Re: Question 2: If this is this a wanted feature, where can I change this.

There is not an INI setting for this as of now. However if you are really interested in this you should add a suggestion for it in the bug system, we can then have a look at it for one of the next 3.6 releases.

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

eZ debug

Timing:	Jan 18 2025 11:08:26
Script start
Timing:	Jan 18 2025 11:08:26
Module start 'layout'
Timing:	Jan 18 2025 11:08:26
Module start 'content'
Timing:	Jan 18 2025 11:08:27
Module end 'content'
Timing:	Jan 18 2025 11:08:27
Script end

Main resources:

Total runtime	0.6754 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.0062	587.7891	152.6094
Module start 'layout'	0.0062	0.0028	740.3984	39.4141
Module start 'content'	0.0090	0.6649	779.8125	528.0781
Module end 'content'	0.6739	0.0014	1,307.8906	8.1953
Script end	0.6754		1,316.0859

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0033	0.4884	16	0.0002
Check MTime	0.0014	0.2091	16	0.0001
Mysql Total
Database connection	0.0011	0.1618	1	0.0011
Mysqli_queries	0.6281	92.9883	54	0.0116
Looping result	0.0005	0.0745	52	0.0000
Template Total	0.6451	95.5	2	0.3226
Template load	0.0022	0.3195	2	0.0011
Template processing	0.6429	95.1900	2	0.3215
Template load and register function	0.0001	0.0188	1	0.0001
states
state_id_array	0.0008	0.1189	1	0.0008
state_identifier_array	0.0016	0.2302	2	0.0008
Override
Cache load	0.0018	0.2641	17	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0008	0.1118	2	0.0004
Fetch class attribute name	0.0011	0.1670	4	0.0003
XML
Image XML parsing	0.0029	0.4251	2	0.0014
class_abstraction
Instantiating content class attribute	0.0000	0.0010	4	0.0000
General
dbfile	0.0027	0.3925	23	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
2	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.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	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