3.1 beta release / Call for registering how much time it took to install

Next topic

Author	Message
jim caprioli	Wednesday 28 May 2003 7:22:46 am Just finished with 3.0-2... they smack me right in the face with 3.1. Wel... Packages for Linux and Window$ are downloading. I can't wait to see if all these bugs have been fixed. If they were hiring a QA manager I would be the first to apply, this CMS has serious >potential<... I wonder if I should bother to check if they support Apache 2 now. To the point... Click the stopwatch when you start unzipping your download.
Ole Morten Halvorsen	Wednesday 28 May 2003 7:36:38 am eZ publish was worked with apache 2 for a long time now. Just remeber to enable AcceptPathInfo which is disabled as default in apache 2. See: http://ez.no/developer/ez_publish_3/documentation/ez_publish_3/typical_problems_and_solutions/ez_publish_3_and_apache_2 Senior Software Engineer - Vision with Technology http://www.visionwt.com http://www.omh.cc http://www.twitter.com/omh eZ Certified Developer http://ez.no/certification/verify/358441 http://ez.no/certification/verify/272578
jim caprioli	Wednesday 28 May 2003 2:32:43 pm thanks i will try. but on unix / production it is Apache anyway. ;-) i installed 3.1 beta 1 in a zip, less than 5 mins, i quickly checked my known bugs. (on windows / test i have no virtual host confiigured) when i do http://localhost/ezsystems/index.php/admin/sdk/ i enter the sdk docs alright. 1) the [tab manual] points to a wrong URL http://localhost/manual, that was the same in the 3.0.2 2) i see no difference in the docs, "beta" does not mean "unfinished" in my book. it is a completely finished product including all docs which is released to customer test sites only. no production installs are guaranteed. anyway, it seems to be a very necessary bug-fix release. it looks as though testing has to be done by early adapters like us. i come from the Neths. i checked the websites of their two partners overhere. Both pre 3.0 sites. Average websites you can make with any tool. I am mainly (if not only) interested in ez as an application framework layer. unix is for tomorrow. i expect the same good results there.

Author

Message

Wednesday 28 May 2003 7:22:46 am

Just finished with 3.0-2... they smack me right in the face with 3.1. Wel... Packages for Linux and Window$ are downloading. I can't wait to see if all these bugs have been fixed.

If they were hiring a QA manager I would be the first to apply, this CMS has serious >potential<...

I wonder if I should bother to check if they support Apache 2 now.

To the point...

Click the stopwatch when you start unzipping your download.

Ole Morten Halvorsen

Wednesday 28 May 2003 7:36:38 am

eZ publish was worked with apache 2 for a long time now. Just remeber to enable AcceptPathInfo which is disabled as default in apache 2.

See:
http://ez.no/developer/ez_publish_3/documentation/ez_publish_3/typical_problems_and_solutions/ez_publish_3_and_apache_2

Senior Software Engineer - Vision with Technology

http://www.visionwt.com
http://www.omh.cc
http://www.twitter.com/omh

eZ Certified Developer
http://ez.no/certification/verify/358441
http://ez.no/certification/verify/272578

jim caprioli

Wednesday 28 May 2003 2:32:43 pm

thanks i will try. but on unix / production it is Apache anyway. ;-)

i installed 3.1 beta 1 in a zip, less than 5 mins, i quickly checked my *known* bugs. (on windows / test i have no virtual host confiigured) when i do http://localhost/ezsystems/index.php/admin/sdk/ i enter the sdk docs alright.
1) the [tab manual] points to a wrong URL http://localhost/manual, that was the same in the 3.0.2
2) i see no difference in the docs, "beta" does not mean "unfinished" in my book. it is a completely finished product including all docs which is released to customer *test* sites only. no production installs are guaranteed.

anyway, it seems to be a very necessary bug-fix release. it looks as though testing has to be done by early adapters like us.
i come from the Neths. i checked the websites of their two partners overhere. Both pre 3.0 sites. Average websites you can make with any tool.
I am mainly (if not only) interested in ez as an application framework layer.

unix is for tomorrow. i expect the same good results there.