I suspect that this should be easy to fix/avoid - it seems something is going wrong with symlinks in the installation process...

The current eZ Publish installation instructions contain a section "Setting up folder permissions". Following the chmod version of these commands seems to break the eZ installation process.

The instruction is in the documentation here:
https://confluence.ez.no/pages/viewpage.action?pageId=7438581
(Installing eZ Publish on a Linux/Unix based system)

WHAT DOES NOT WORK / WHAT DOES
Basically, the result is this:
[follow instructions] => CAN NOT access www.example.com/web/index.php/ezsetup
(but can access setup at www.example.com/ezpublish_legacy/index.php/ezsetup)

What does work:
[follow instructions - minus the chmod command] => CAN access www.example.com/web/index.php/ezsetup and complete setup.

I've tested this several times now. Method follows.

REPLICATION OF ISSUE - (1) Process that fails
: Get & unpack eZ
wget http://share.ez.no/content/download/150669/890221/version/1/file/ezpublish5_community_project-2013.05-gpl-full.tar.bz2
bunzip2 ezpublish_community_project-2013.5-gpl.tar.bz2
tar –xf ezpublish_community_project-2013.5-gpl.tar

: Move eZ to current working directory
mv ezpublish_community_project-2013.5-gpl-full/* .

: Chmod command
chmod -R a+rwx ezpublish/

{cache,logs,config}

ezpublish_legacy/

{design,extension,settings,var}

web

: Link Asset Commands
php ezpublish/console assets:install –symlink web
php ezpublish/console ezpublish:legacy:assets_install –symlink web
php ezpublish/console assetic:dump –env=prod web

: Rename/ammend htaccess rewrite rule for .htaccess:
: CHANGE RewriteRule .* index.php
: TO:
: RewriteRule !(\.(gif|jpe?g|png|css|js|html?)|var(.)storage.pdf(.)\.pdf)$ index.php

REPLICATION OF ISSUE - (2) Process that works
[complete the above commands, leaving out the chmod command]

ANALYSIS & IMPLICATIONS:

• that setup can be accessed via the ezpublish_legacy directory indicates that eZ does actually work - seems there's something about the symlinks being affected.
• It's not (yet) clear how leaving out the chmod command affects the install in other ways. So I'm not sure whether this is an instruction that should be left out, or a code issue.

Hope this helps.
-Paul