Contao Manager skips installation step

I'm trying to install Conatao 4.4 LTS using Contao Manager. All appears to have gone allright (see attached console output and composer-install.out.log) but the manager ends offering database update instead of Installtool:
Console task complete!
The background task was completed successfully. Check the console protocol for the details.
Datenbank aktualisieren (green) Bestätigen u Schließen (grey)

This though I've not yet provided any database information. Trying database update has no visible effect, so I'm stuck. Any help to locate and fix the issue would be appreciated. Thank you!

Did you set the DocumentRoot properly? Can you open the Contao Installtool via https://example.com/contao/install?

there is neither a directory example.com/contao nor a file https://example.com/contao/install.php

I understand (from provider hotline) that "document root" is the landing directory of the domain. In my webspace (/) I created directories /Contao44/web/, set the domain to point to /Contao44/web/, placed contao-manager as /Contao44/web/contao-manager.phar.php and called it as https://example.com/contao-manager.phar.php . So that should have been the right document root. Correct?

The manager placed many directories into /Contao44/ (among others: app, system, vendor) . In /Contao44/web/ landed directories assets, bundles, share, system and files app-php and app-dev.php

Quote:

---

Originally Posted by NBaxl

there is neither a directory example.com/contao nor a file https://example.com/contao/install?

---

That's correct. There's no install.php file anymore. contao/install isn't a physical directory/file but a so called route. Just open https://example.com/contao/install to run the Contao install tool. If that doesn't work, try https://example.com/app.php/contao/install. If the latter works, you have a problem with the .htaccess file. Is there a .htaccess in the web/ folder at all?

Quote:

---

Originally Posted by NBaxl

I understand (from provider hotline) that "document root" is the landing directory of the domain. In my webspace (/) I created directories /Contao44/web/, set the domain to point to /Contao44/web/, placed contao-manager as /Contao44/web/contao-manager.phar.php and called it as https://example.com/contao-manager.phar.php . So that should have been the right document root. Correct?

---

Yes.

Quote:

---

Originally Posted by NBaxl

The manager placed many directories into /Contao44/ (among others: app, system, vendor) . In /Contao44/web/ landed directories assets, bundles, share, system and files app-php and app-dev.php

---

Correct.

Quote:

---

Originally Posted by xchs

Just open https://example.com/contao/install to run the Contao install tool. If that doesn't work, try https://example.com/app.php/contao/install. If the latter works, you have a problem with the .htaccess file. Is there a .htaccess in the web/ folder at all?

---

While helping to overcame php troubles, the provider had replaced my .htaccess (in /Contao44/web) with his favourite one. Now I disabled both before trying your advice.
Nevertheless https://example.com/contao/install yielded: The requested URL /contao/install was not found on this server.
But https://example.com/app.php/contao/install ran the installtool succesfully (so it claims)

Many thanks for your help!!

Try to add a new web/.htaccess file with this content:

Code:

---

<IfModule mod_headers.c>
    # Allow access from all domains for webfonts (see contao/core-bundle#528)
    <FilesMatch "\.(ttf|ttc|otf|eot|woff2?|font\.css)$">
        Header set Access-Control-Allow-Origin "*"
    </FilesMatch>
</IfModule>

<IfModule mod_rewrite.c>
    RewriteEngine On

    # Determine the RewriteBase automatically and set it as environment variable.
    # If you are using Apache aliases to do mass virtual hosting or installed the
    # project in a subdirectory, the base path will be prepended to allow proper
    # resolution of the app.php file and to redirect to the correct URI. It will
    # work in environments without path prefix as well, providing a safe, one-size
    # fits all solution. But as you do not need it in this case, you can comment
    # the following 2 lines to eliminate the overhead.
    RewriteCond %{REQUEST_URI}::$1 ^(/.+)/(.*)::\2$
    RewriteRule ^(.*) - [E=BASE:%1]

    # Sets the HTTP_AUTHORIZATION header removed by Apache
    RewriteCond %{HTTP:Authorization} .
    RewriteRule ^ - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

    # Redirect to URI without front controller to prevent duplicate content
    # (with and without `/app.php`). Only do this redirect on the initial
    # rewrite by Apache and not on subsequent cycles. Otherwise we would get an
    # endless redirect loop (request -> rewrite to front controller ->
    # redirect -> request -> ...).
    # So in case you get a "too many redirects" error or you always get redirected
    # to the start page because your Apache does not expose the REDIRECT_STATUS
    # environment variable, you have 2 choices:
    # - disable this feature by commenting the following 2 lines or
    # - use Apache >= 2.3.9 and replace all L flags by END flags and remove the
    #  following RewriteCond (best solution)
    RewriteCond %{ENV:REDIRECT_STATUS} ^$
    RewriteRule ^app\.php(?:/(.*)|$) %{ENV:BASE}/$1 [R=301,L]

    # If the requested filename exists, simply serve it.
    # We only want to let Apache serve files and not directories.
    RewriteCond %{REQUEST_FILENAME} -f
    RewriteRule ^ - [L]

    # Rewrite all other queries to the front controller.
    RewriteRule ^ %{ENV:BASE}/app.php [L]
</IfModule>

<IfModule !mod_rewrite.c>
    <IfModule mod_alias.c>
        # When mod_rewrite is not available, we instruct a temporary redirect of
        # the start page to the front controller explicitly so that the website
        # and the generated links can still be used.
        RedirectMatch 302 ^/$ /app.php/
        # RedirectTemp cannot be used instead
    </IfModule>
</IfModule>

---

Then you should be able to run the Contao install tool directly via https://example.com/contao/install (i.e. without the app.php entry point).

Quote:

---

Originally Posted by NBaxl

While helping to overcame php troubles, the provider had replaced my .htaccess (in /Contao44/web) with his favourite one. Now I disabled both before trying your advice.
Nevertheless https://example.com/contao/install yielded: The requested URL /contao/install was not found on this server.
But https://example.com/app.php/contao/install ran the installtool succesfully (so it claims)

Many thanks for your help!!

---

Delete the web/.htaccess and and run a "composer install".