Xibo 1.8rc1 Installation Trouble

Developer Experience
1

Environment:
Windows Server
Apache 2.4 with vHosts
PHP7
Path to vHost:
<VirtualHost *> DocumentRoot "x:/.../xibo/web" ServerName xxx-xibo ErrorLog logs/xibo <Directory x:/.../xibo/web> Options Indexes FollowSymLinks AllowOverride All Require all granted </Directory> </VirtualHost>
Hello guys,
because of our environment we have to use (actually testing) Xibo 1.8.
I passed the prerequisits and can confirm the installation. Pressing after the installation the login butto ending in Error 500.
If I use the whole link e.g. http://xxx-xibo/web/index.php/login it shows me the theme but with error message “Page not found”.
I think its an problem with my htaccess and the routing of the correct files.
But i have absolutely no idea :frowning:

.htaccess
Options +FollowSymLinks
RewriteEngine On
#RewriteBase /xibo

        # fix authorization header
        RewriteCond %{HTTP:Authorization} .+
        RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

        # requests for api authorize
        RewriteCond %{REQUEST_FILENAME} !-f
        RewriteCond %{REQUEST_URI} ^.*/authorize/.*$
        RewriteRule ^ api/authorize/index.php [QSA,L]

        # requests that start with api go down to api/index.php
        RewriteCond %{REQUEST_FILENAME} !-f
        RewriteCond %{REQUEST_URI} ^.*/api/.*$
        RewriteRule ^ api/index.php [QSA,L]

        # install
        RewriteCond %{REQUEST_FILENAME} !-f
        RewriteCond %{REQUEST_URI} ^.*/install/.*$
        RewriteRule ^ install/index.php [QSA,L]

        # maintenance
        RewriteCond %{REQUEST_FILENAME} !-f
        RewriteCond %{REQUEST_URI} ^.*/maint/.*$
        RewriteRule ^ maint/index.php [QSA,L]

        # all others - i.e. web
        RewriteCond %{REQUEST_FILENAME} !-f
        RewriteRule ^ index.php [QSA,L]

Thanks and best regards!

Purdy

2

PHP 7 is not supported with Xibo 1.8 yet. It will be, but it isn’t at present.

The web folder should be the only folder served by your webserver, but you have web in your URL, which suggests the webserver is actually serving the folder above. You need to resolve both those issues before you can proceed.