Will EZpublish conflict?

Next topic

Author	Message
Derrick Penner	Wednesday 21 April 2004 6:57:56 am I posted an earlier thread about dropping the port from EZ and instead making the url http://www.mydomain.net/blog (compared to http://www.mydomain.net:8085/blog) The solution by Ole Morten Halvorsen was "Simply find your ezpublish.conf located in the apache_x.x.xx/conf (where x.x.xx is your apache version. This version may be different depending on which ezpublish version you downloaded.) and replace every occurence of 8085 with 80. (should be about 6 of them) Then restart apache by running /opt/ezpublish/bin/ezpublish restart I think the solution above will only drop off the port...which I want to do...but it won't give me the opportunity to forward the requests to www.mydomain.net/blog. I'm worried that EZpublish will conflict with my normal page if I use the solution above. I want to make the url separate from my normal webpage so that normal port 80 requests go to www.mydomain.net. The simple jist of it is that I want the blog to resolve itself as www.mydomain.net/blog instead of www.mydomain.net:8085/blog...so the real question is, will the solution Mr. Halvorsen posted do this for me? Or will it conflict with my normal webpage?
Derrick Penner	Wednesday 21 April 2004 10:29:46 am Well...I tried it and it doesn't conflict with my front web page on www.mydomain.net Instead, it doesn't even run. Changed 8085 to 80 on my ezpublish.conf file and I now can't reach the page at all. So I switched it back. Still waiting on a fix for this.

Author

Message

Wednesday 21 April 2004 6:57:56 am

I posted an earlier thread about dropping the port from EZ and instead making the url http://www.mydomain.net/blog (compared to http://www.mydomain.net:8085/blog)

The solution by Ole Morten Halvorsen was "Simply find your ezpublish.conf located in the apache_x.x.xx/conf (where x.x.xx is your apache version. This version may be different depending on which ezpublish version you downloaded.) and replace every occurence of 8085 with 80. (should be about 6 of them) Then restart apache by running

/opt/ezpublish/bin/ezpublish restart

I think the solution above will only drop off the port...which I want to do...but it won't give me the opportunity to forward the requests to www.mydomain.net/blog. I'm worried that EZpublish will conflict with my normal page if I use the solution above.

I want to make the url separate from my normal webpage so that normal port 80 requests go to www.mydomain.net. The simple jist of it is that I want the blog to resolve itself as www.mydomain.net/blog instead of www.mydomain.net:8085/blog...so the real question is, will the solution Mr. Halvorsen posted do this for me? Or will it conflict with my normal webpage?

Derrick Penner

Wednesday 21 April 2004 10:29:46 am

Well...I tried it and it doesn't conflict with my front web page on www.mydomain.net

Instead, it doesn't even run. Changed 8085 to 80 on my ezpublish.conf file and I now can't reach the page at all. So I switched it back. Still waiting on a fix for this.

eZ debug

Timing:	Jan 19 2025 10:00:04
Script start
Timing:	Jan 19 2025 10:00:04
Module start 'layout'
Timing:	Jan 19 2025 10:00:04
Module start 'content'
Timing:	Jan 19 2025 10:00:05
Module end 'content'
Timing:	Jan 19 2025 10:00:05
Script end

Main resources:

Total runtime	0.9782 sec
Peak memory usage	4,096.0000 KB
Database Queries	52

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0050	589.1719	152.6250
Module start 'layout'	0.0050	0.0032	741.7969	39.4453
Module start 'content'	0.0083	0.9683	781.2422	424.8594
Module end 'content'	0.9766	0.0016	1,206.1016	8.1641
Script end	0.9781		1,214.2656

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0033	0.3327	16	0.0002
Check MTime	0.0013	0.1358	16	0.0001
Mysql Total
Database connection	0.0007	0.0735	1	0.0007
Mysqli_queries	0.9373	95.8177	52	0.0180
Looping result	0.0005	0.0529	50	0.0000
Template Total	0.9444	96.5	2	0.4722
Template load	0.0024	0.2488	2	0.0012
Template processing	0.9419	96.2918	2	0.4710
Template load and register function	0.0002	0.0228	1	0.0002
states
state_id_array	0.0014	0.1456	1	0.0014
state_identifier_array	0.0026	0.2616	2	0.0013
Override
Cache load	0.0020	0.2030	11	0.0002
Sytem overhead
Fetch class attribute can translate value	0.0007	0.0762	1	0.0007
Fetch class attribute name	0.0013	0.1352	2	0.0007
XML
Image XML parsing	0.0001	0.0107	1	0.0001
class_abstraction
Instantiating content class attribute	0.0000	0.0012	2	0.0000
General
dbfile	0.0007	0.0675	10	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/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/literal.tpl	<No override>	extension/community/design/standard/templates/content/datatype/view/ezxmltags/literal.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 8 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs