Hi,
I confirm Apache server is Okay to serve folder from /home/$user if correct ACL defined in the right folder.
As I precised I created a symbolic link from the /web folder in the /var/www/xibocms and correctly activated the rewrite rule in the .htaccess file without success.
Despite all of this, I decided to create a new directory in /var/www/ including the whole archive.
I dropped the files there and created a symbolic link and configured everything as instructed in the manual, step by step to the root web folder. This came to nothing since the behavior remains the same.
It is therefore not possible for me currently to run version 3 RC2 under apache environment.
I went further by going to take a look at the errors of the “slim” framework on stack overflow and realize that these operating problems affect a lot of people and that certain modifications must be made within the parameters to correct certain problems appeared between the 3rd and 4th releases of this framework.
There is one of the possible solutions to configure in the Slim framework :
adding $app->setBasePath("/the_right_folder/to_work_on"); solved the issue on some users.
For the 3rd version of this framework, there is some modifications to add in the “dependancies.php” file to activate routes in a subfolder :
// Activating routes in a subfolder
$container['environment'] = function () {
$scriptName = $_SERVER['SCRIPT_NAME'];
$_SERVER['SCRIPT_NAME'] = dirname(dirname($scriptName)) . '/' . basename($scriptName);
return new Slim\Http\Environment($_SERVER);
};
Due to specific needings here and big / deeper customization of the CMS frontend inside my company, we cannot use Docker solution.
Which brings me to my last question:
Does the installation via the Docker solution allow full interface customization from the login page to the dashboard, menu etc… and other features?
If you can confirm it to me, are these changes made via the skins / themes package as on previous versions? Are these solutions flexible as changing the entire appearance via .css and other files?
If it is possible to completely customize the appearance and certain behaviors of the CMS via personalized theme, in this case I will opt for the Docker solution which seems to me to be THE solution to consider from now on.
Thanks for feedback