Affects Version/s: 2013.4
Fix Version/s: None
PHP 5.3.24, MySQL 5.1.68 [Note: Using eZ 2013.5; APC 3.1.9 (required) not installed - though forums suggest this is not actually required; also, using htaccess setup rather than virtual host]
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:
(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
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/
: 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
: RewriteRule !(\.(gif|jpe?g|png|css|js|html?)|var(.)\.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.