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.