Differences between host;uri and host_uri in MatchOrder ?

Next topic

Author	Message
Jerome Despatis	Friday 01 July 2011 1:54:07 am For now, I have a multilingual website, I wanted uri like domain.com/fr, domain.com/zh etc.. So I've used MatchOrder=host;uri, And i've renamed the default siteaccesses (coded on three characters by default), for example 'fre' to 'fr' and so on for all siteaccesses Now, until eZ 4.5 (or 4.4, I can't remember), the MatchOrder=host_uri has appeared... Anyone could explain me the difference between the both ? the advantages of host_uri in regards of host;uri in fact Thanks
Jérôme Vieilledent	Friday 01 July 2011 5:30:38 am Hi Jerome The difference is in the way eZ Publish tries to figure out which siteaccess to use to handle the request. host;uri will try first the host mode, and then the URI mode if the host mode failed host_uri will take the 2 as a whole (host + URI at the same time)
Jerome Despatis	Friday 01 July 2011 7:30:06 am Ok thanks I understand. But it leads me to another question: I'd like to have the FrontEnd and the BackEnd multilingual for example, to fully understand Here I definitely need host_uri I guess So i do something like, for example: MatchOrder=host_uri HostUriMatchMapItems[]=adminezpublish11.poseidon.dev;;ezwebin_site_clean_admin HostUriMatchMapItems[]=adminezpublish11.poseidon.dev;es;ezwebin_site_clean_admin HostUriMatchMapItems[]=wwwezpublish11.poseidon.dev;en;en;end HostUriMatchMapItems[]=wwwezpublish11.poseidon.dev;es;es;end I go to http://adminezpublish11.poseidon.dev/es I was thinking page would be exactly the same as http://adminezpublish11.poseidon.dev as same siteaccess is used But I get indeed 'es' is an undefined module (kernel 20 error) The logic is however good for FE Any idea ?

Author

Message

Friday 01 July 2011 1:54:07 am

For now, I have a multilingual website, I wanted uri like domain.com/fr, domain.com/zh etc..

So I've used MatchOrder=host;uri, And i've renamed the default siteaccesses (coded on three characters by default), for example 'fre' to 'fr' and so on for all siteaccesses

Now, until eZ 4.5 (or 4.4, I can't remember), the MatchOrder=host_uri has appeared...

Anyone could explain me the difference between the both ? the advantages of host_uri in regards of host;uri in fact

Thanks

Jérôme Vieilledent

Friday 01 July 2011 5:30:38 am

Hi Jerome

The difference is in the way eZ Publish tries to figure out which siteaccess to use to handle the request.

host;uri will try first the host mode, and then the URI mode if the host mode failed
host_uri will take the 2 as a whole (host + URI at the same time)

Jerome Despatis

Friday 01 July 2011 7:30:06 am

Ok thanks I understand.

But it leads me to another question: I'd like to have the FrontEnd and the BackEnd multilingual for example, to fully understand

Here I definitely need host_uri I guess

So i do something like, for example:

MatchOrder=host_uri
HostUriMatchMapItems[]=adminezpublish11.poseidon.dev;;ezwebin_site_clean_admin
HostUriMatchMapItems[]=adminezpublish11.poseidon.dev;es;ezwebin_site_clean_admin
HostUriMatchMapItems[]=wwwezpublish11.poseidon.dev;en;en;end
HostUriMatchMapItems[]=wwwezpublish11.poseidon.dev;es;es;end

I go to http://adminezpublish11.poseidon.dev/es

I was thinking page would be exactly the same as http://adminezpublish11.poseidon.dev as same siteaccess is used

But I get indeed 'es' is an undefined module (kernel 20 error)

The logic is however good for FE

Any idea ?

eZ debug

Timing:	Jan 18 2025 02:54:21
Script start
Timing:	Jan 18 2025 02:54:21
Module start 'layout'
Timing:	Jan 18 2025 02:54:21
Module start 'content'
Timing:	Jan 18 2025 02:54:21
Module end 'content'
Timing:	Jan 18 2025 02:54:21
Script end

Main resources:

Total runtime	0.0145 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.0052	588.1563	152.6563
Module start 'layout'	0.0052	0.0027	740.8125	39.5156
Module start 'content'	0.0078	0.0047	780.3281	90.1016
Module end 'content'	0.0125	0.0019	870.4297	34.2891
Script end	0.0144		904.7188

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0024	16.3265	14	0.0002
Check MTime	0.0011	7.2670	14	0.0001
Mysql Total
Database connection	0.0007	4.9347	1	0.0007
Mysqli_queries	0.0022	14.9307	3	0.0007
Looping result	0.0000	0.1383	1	0.0000
Template Total	0.0017	11.4	1	0.0017
Template load	0.0009	6.1724	1	0.0009
Template processing	0.0008	5.1980	1	0.0008
Override
Cache load	0.0006	4.2664	1	0.0006
General
dbfile	0.0003	2.1381	8	0.0000
String conversion	0.0000	0.0955	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