3.2 url management question

Next topic

Author	Message
Paul Forsyth	Wednesday 27 August 2003 2:44:11 am I'm playing with url translation but im a little stuck. I thought that url translation meant that we would be able to control the way urls display in the browser, like the current 3.1 method for nice urls. But when i try all i get is a redirect. instead of displaying the text for the current screen the system tries to load in that new page... For example, im trying to hide my content/edit calls, so i try in the url translation screen: content/edit/100/2 -> my_folder/my_place when i then goto my edit screen ez tries to interpret 'my_folder' as a module and complains. on my system 'my_folder' is a standard folder object and so should resolve properly. 'my_place' is a made up name as it is just text i want the user to see. if i blank out the text for where the url is meant to point to i get a redirect to the home page. In addition i would like to remove the content object id and version information from the url, so i would prefer: content/edit/* -> wherever or content/edit/// -> wherever Is this possible with url translation? I seem to be missing the correct usage for this function. Can some documentation for it be created? paul
Volker Lenz	Saturday 13 September 2003 3:15:10 am You try to use nice urls with module functions other that view. For editing or creating content, the ez documentation recommends to avoid using nice urls, since nice urls are designed for (and depend on) existing node objects in the content tree.
Paul Forsyth	Saturday 13 September 2003 11:22:03 am My hope here is to not use nice urls but to have ez 'mask' the real url with url i have given it. In the example i gave i can't use nice urls as i am editing a node. I don't want the user to see the content/edit part. Though i haven't tried this with beta 2. Can someone from ez comment on this? Paul

Author

Message

Wednesday 27 August 2003 2:44:11 am

I'm playing with url translation but im a little stuck.

I thought that url translation meant that we would be able to control the way urls display in the browser, like the current 3.1 method for nice urls. But when i try all i get is a redirect. instead of displaying the text for the current screen the system tries to load in that new page...

For example, im trying to hide my content/edit calls, so i try in the url translation screen:

content/edit/100/2 -> my_folder/my_place

when i then goto my edit screen ez tries to interpret 'my_folder' as a module and complains. on my system 'my_folder' is a standard folder object and so should resolve properly. 'my_place' is a made up name as it is just text i want the user to see. if i blank out the text for where the url is meant to point to i get a redirect to the home page.

In addition i would like to remove the content object id and version information from the url, so i would prefer:

content/edit/* -> wherever

content/edit/*/*/ -> wherever

Is this possible with url translation?

I seem to be missing the correct usage for this function. Can some documentation for it be created?

paul

Volker Lenz

Saturday 13 September 2003 3:15:10 am

You try to use nice urls with module functions other that view. For editing or creating content, the ez documentation recommends to avoid using nice urls, since nice urls are designed for (and depend on) existing node objects in the content tree.

Paul Forsyth

Saturday 13 September 2003 11:22:03 am

My hope here is to not use nice urls but to have ez 'mask' the real url with url i have given it.

In the example i gave i can't use nice urls as i am editing a node. I don't want the user to see the content/edit part.

Though i haven't tried this with beta 2. Can someone from ez comment on this?

Paul

eZ debug

Timing:	Jan 18 2025 11:13:02
Script start
Timing:	Jan 18 2025 11:13:02
Module start 'layout'
Timing:	Jan 18 2025 11:13:02
Module start 'content'
Timing:	Jan 18 2025 11:13:03
Module end 'content'
Timing:	Jan 18 2025 11:13:03
Script end

Main resources:

Total runtime	0.7266 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.0061	589.0313	152.6250
Module start 'layout'	0.0062	0.0031	741.6563	39.4453
Module start 'content'	0.0092	0.7160	781.1016	501.0156
Module end 'content'	0.7252	0.0013	1,282.1172	12.3203
Script end	0.7266		1,294.4375

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0037	0.5034	16	0.0002
Check MTime	0.0013	0.1815	16	0.0001
Mysql Total
Database connection	0.0008	0.1071	1	0.0008
Mysqli_queries	0.6792	93.4792	57	0.0119
Looping result	0.0005	0.0679	55	0.0000
Template Total	0.6889	94.8	2	0.3445
Template load	0.0023	0.3130	2	0.0011
Template processing	0.6866	94.4962	2	0.3433
Template load and register function	0.0002	0.0324	1	0.0002
states
state_id_array	0.0009	0.1266	1	0.0009
state_identifier_array	0.0020	0.2721	2	0.0010
Override
Cache load	0.0018	0.2490	23	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0008	0.1124	2	0.0004
Fetch class attribute name	0.0012	0.1609	4	0.0003
XML
Image XML parsing	0.0007	0.0997	2	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0014	4	0.0000
General
dbfile	0.0011	0.1471	16	0.0001
String conversion	0.0000	0.0011	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
3	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.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: 9 Number of unique templates used: 5

Time used to render debug report: 0.0002 secs