URLTranslator Error Handling

Next topic

Author	Message
Björn Dieding@xrow.de	Thursday 26 June 2003 6:33:20 pm The Urltranslator is a nice thing, but it throws too many errors when you externaly link your site. Sample... Image a url got listed in some search engine http://www:92/english/home/company/news/webmail_server after the indexing into the searchengine you change your object name http://www:92/english/home/company/news/webmail_server_new When a vistor comes now from an external link that can't be resolved to a URL it eZ fails with "modul not found" For the future I recommend some kind of URLtranslator history, where old URL are stored. Maybe it makes also sense to store the urls path with the object version. An other idea would be to search through all object versions for a proper match. Starting from the left handside to the right. One thing I cann't tell is the influence on the system performance if we do my 2nd suggestion. What do you think? Björn Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs Looking for hosting? http://hostingezpublish.com ----------------------------------------------------------------------------- GMT +01:00 Hannover, Germany Web: http://www.xrow.com/
Björn Dieding@xrow.de	Wednesday 16 July 2003 2:13:28 am A document moved response + redirect would cool too. Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs Looking for hosting? http://hostingezpublish.com ----------------------------------------------------------------------------- GMT +01:00 Hannover, Germany Web: http://www.xrow.com/
Jan Borsodi	Wednesday 16 July 2003 2:36:48 am The url translator history sounds good. It could be a general url mapping table in which you could enter other urls as well (ie. for importing old ezp2.2 sites). We will make a note of this and see what we can come up with. -- Amos Documentation: http://ez.no/ez_publish/documentation FAQ: http://ez.no/ez_publish/documentation/faq

Author

Message

Thursday 26 June 2003 6:33:20 pm

The Urltranslator is a nice thing, but it throws too many errors when you externaly link your site.
Sample...
Image a url got listed in some search engine
http://www:92/english/home/company/news/webmail_server

after the indexing into the searchengine you change your object name
http://www:92/english/home/company/news/webmail_server_new

When a vistor comes now from an external link that can't be resolved to a URL it eZ fails with "modul not found"

For the future I recommend some kind of URLtranslator history, where old URL are stored. Maybe it makes also sense to store the urls path with the object version.

An other idea would be to search through all object versions for a proper match. Starting from the left handside to the right. One thing I cann't tell is the influence on the system performance if we do my 2nd suggestion.

What do you think?

Björn

Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs
Looking for hosting? http://hostingezpublish.com
-----------------------------------------------------------------------------
GMT +01:00 Hannover, Germany
Web: http://www.xrow.com/

Björn Dieding@xrow.de

Wednesday 16 July 2003 2:13:28 am

A document moved response + redirect would cool too.

Jan Borsodi

Wednesday 16 July 2003 2:36:48 am

The url translator history sounds good. It could be a general url mapping table in which you could enter other urls as well (ie. for importing old ezp2.2 sites).
We will make a note of this and see what we can come up with.

--
Amos

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

eZ debug

Timing:	Jan 18 2025 10:17:44
Script start
Timing:	Jan 18 2025 10:17:44
Module start 'layout'
Timing:	Jan 18 2025 10:17:44
Module start 'content'
Timing:	Jan 18 2025 10:17:44
Module end 'content'
Timing:	Jan 18 2025 10:17:44
Script end

Main resources:

Total runtime	0.6749 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.0064	589.0469	152.6250
Module start 'layout'	0.0064	0.0028	741.6719	39.4453
Module start 'content'	0.0093	0.6641	781.1172	544.1953
Module end 'content'	0.6734	0.0014	1,325.3125	12.1641
Script end	0.6748		1,337.4766

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0034	0.5002	16	0.0002
Check MTime	0.0014	0.2005	16	0.0001
Mysql Total
Database connection	0.0009	0.1351	1	0.0009
Mysqli_queries	0.6235	92.3845	57	0.0109
Looping result	0.0005	0.0698	55	0.0000
Template Total	0.6436	95.4	2	0.3218
Template load	0.0019	0.2788	2	0.0009
Template processing	0.6417	95.0827	2	0.3208
Template load and register function	0.0001	0.0140	1	0.0001
states
state_id_array	0.0009	0.1341	1	0.0009
state_identifier_array	0.0010	0.1476	2	0.0005
Override
Cache load	0.0015	0.2286	22	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0011	0.1593	2	0.0005
Fetch class attribute name	0.0010	0.1522	5	0.0002
XML
Image XML parsing	0.0010	0.1413	2	0.0005
class_abstraction
Instantiating content class attribute	0.0000	0.0017	6	0.0000
General
dbfile	0.0009	0.1285	23	0.0000
String conversion	0.0000	0.0012	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/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
3	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
4	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 15 Number of unique templates used: 6

Time used to render debug report: 0.0002 secs