Should ez newsletter always be a separate installation?

Next topic

Author	Message
Greg McAvoy-Jensen	Thursday 02 August 2007 12:18:04 am I'm new to ez newsletter, and I want to learn about best practices for the install before I install it for two separate organizations. My sense from reading the forum is that it is preferable to install ez newsletter using the installer that's already coupled with ez publish 3.9.2. So let me ask more precisely: 1. If one has an existing website with users accounts already set up, and one wishes to avoid making those users re-register in a separate newsletter installation, should one add ez newsletter functionality to the existing site--or is there a better way? 2. If one has an existing website and wants to add newsletter functionality but there's no concern about existing users as in #1, is it still best to create an entirely separate installation of eZ Publish+ez newsletter? Many thanks! Granite Horizon, Certified Developer of eZ Publish Web Solutions Provider of the SaaS Solution Granite Horizon In The Cloud \| http://granitehorizon.com/cloud http://granitehorizon.com \| +1 916 647 6350 \| California USA \| @granitegreg Blog: http://granitehorizon.com/blog
Tobias Struckmeier	Thursday 02 August 2007 1:30:37 am We choose to make the setup as easy as possible. Often people have an existing site that is sometimes not eZ Publish but another system or static html. So this way you can use it whatever your level of eZ Publish knowledge is. So if you want a tight integration into an existing eZ Publish site it will depend on your environment, but mostly it will be best to have it in the same installation. For that you can use the setup wizard and use it as a reference. But anyway we are preparing a documentation, how to do add it to an existing site by end of the month.
Greg McAvoy-Jensen	Friday 03 August 2007 11:05:07 pm Thank you for the response! I look forward to seeing the document when it's ready. Granite Horizon, Certified Developer of eZ Publish Web Solutions Provider of the SaaS Solution Granite Horizon In The Cloud \| http://granitehorizon.com/cloud http://granitehorizon.com \| +1 916 647 6350 \| California USA \| @granitegreg Blog: http://granitehorizon.com/blog

Author

Message

Thursday 02 August 2007 12:18:04 am

I'm new to ez newsletter, and I want to learn about best practices for the install before I install it for two separate organizations. My sense from reading the forum is that it is preferable to install ez newsletter using the installer that's already coupled with ez publish 3.9.2. So let me ask more precisely:

1. If one has an existing website with users accounts already set up, and one wishes to avoid making those users re-register in a separate newsletter installation, should one add ez newsletter functionality to the existing site--or is there a better way?

2. If one has an existing website and wants to add newsletter functionality but there's no concern about existing users as in #1, is it still best to create an entirely separate installation of eZ Publish+ez newsletter?

Many thanks!

Granite Horizon, Certified Developer of eZ Publish Web Solutions
Provider of the SaaS Solution Granite Horizon In The Cloud | http://granitehorizon.com/cloud
http://granitehorizon.com | +1 916 647 6350 | California USA | @granitegreg
Blog: http://granitehorizon.com/blog

Tobias Struckmeier

Thursday 02 August 2007 1:30:37 am

We choose to make the setup as easy as possible.
Often people have an existing site that is sometimes not eZ Publish but another system or static html. So this way you can use it whatever your level of eZ Publish knowledge is.

So if you want a tight integration into an existing eZ Publish site it will depend on your environment, but mostly it will be best to have it in the same installation. For that you can use the setup wizard and use it as a reference.

But anyway we are preparing a documentation, how to do add it to an existing site by end of the month.

Greg McAvoy-Jensen

Friday 03 August 2007 11:05:07 pm

Thank you for the response! I look forward to seeing the document when it's ready.

eZ debug

Timing:	Jan 18 2025 05:03:30
Script start
Timing:	Jan 18 2025 05:03:30
Module start 'layout'
Timing:	Jan 18 2025 05:03:30
Module start 'content'
Timing:	Jan 18 2025 05:03:30
Module end 'content'
Timing:	Jan 18 2025 05:03:30
Script end

Main resources:

Total runtime	0.0234 sec
Peak memory usage	4,096.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0073	589.5000	152.6563
Module start 'layout'	0.0073	0.0064	742.1563	39.4922
Module start 'content'	0.0137	0.0071	781.6484	94.4609
Module end 'content'	0.0208	0.0025	876.1094	34.3047
Script end	0.0234		910.4141

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0030	12.7649	14	0.0002
Check MTime	0.0012	4.9679	14	0.0001
Mysql Total
Database connection	0.0007	2.9339	1	0.0007
Mysqli_queries	0.0070	29.8819	3	0.0023
Looping result	0.0000	0.1751	1	0.0000
Template Total	0.0020	8.4	1	0.0020
Template load	0.0011	4.5821	1	0.0011
Template processing	0.0009	3.8216	1	0.0009
Override
Cache load	0.0008	3.2281	1	0.0008
General
dbfile	0.0005	2.1144	8	0.0001
String conversion	0.0000	0.0652	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