Root .haccess leads to non-existent index.php

[dantaeusb]

I'm sorry if I'm wrong, but I'm extremely confused about the installation process. I followed steps included in official guides, with basic configuration based on Docker and WSL2. I tried to follow every step carefully several times cause still don't believe that's not my fault. However, looking at the older versions of source code, I'm very confused that there are no adjustments in docs and .htaccess about removing index.php in the root directory (commit 640cad53009b291334234ccd61ab79f256b43da2). There were some links to #356 but it doesn't seem to cover the actual state.

TL;DR: index.php seem no longer exist in root folder, and both .htaccess and official docs assuming it does; the Apache configuration page does not cover this change however there seems to be an update that covers elasticsearch installation info.

Preconditions (*)

1. Try to install Magento 2.4.2
2. Get 403's or file not found after installation and creating vhosts to repo root.

Steps to reproduce (*)

1. Follow official documentation at https://devdocs.magento.com/guides/v2.4/install-gde/composer.html

Expected result (*)

Installation complete and site works assuming .htaccess in root actually forwards requests to index.php in root.

Actual result (*)

Line 7 of .htaccess states DirectoryIndex index.php which is basically non-existent in version 2.4. Adjusting default configuration to pub directory doesn't work and seems like requires some additional changes, which is not covered in guides mentioned above.

Additional info

Apache image used: https://github.com/bitnami/bitnami-docker-apache
PHP-FPM image used: https://github.com/bitnami/bitnami-docker-php-fpm + needed extensions for Magento 2
This page partially covers what seems to be necessary now: https://devdocs.magento.com/guides/v2.4/install-gde/tutorials/change-docroot-to-pub.html

[m2-assistant]

Hi @dantaeusb. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[dantaeusb]

My configuration is incorrect, I was trying to set up Apache + php-fpm because I haven't seen mod_php in requirements neither on this nor this page, but it seems to be assumed "by default" for Apache installations. I guess that's somewhat reasonable though, I was just confused with previous configuration I've had.

So the Issue could be irrelevant, though I still wonder about the purpose of .htaccess in root and whether it works if installed by following guide because mod_php/php-fpm shouldn't be a big deal and there's an entrypoint issue at the first place, not execution issue (I was able to launch Apache + php-fpm, but static content was broken).

[mrtuvn]

You should update description for what version of magento that you got issue
Since 2.4.2 magento changed root folder to pub (index.php file in there). This is not backward-compatible change. No longer file index.php in root like before (2.1, 2.2, 2.3)
If you have only one site magento at time run. Everything start at pub folder implicitly

https://github.com/magento/magento2/blob/2.4-develop/setup/src/Magento/Setup/Model/ConfigOptionsList/Directory.php
app/etc/env.php now default set to true
'directories' => [
'document_root_is_pub' => true
],

Both pub/.htaccess and root file .htaccess have changed
If you see file .htaccess in root that changed to below
current this file (2.4.2+)

RewriteEngine on
RewriteCond %{REQUEST_URI} !^/pub/
RewriteCond %{REQUEST_URI} !^/setup/
RewriteCond %{REQUEST_URI} !^/update/
RewriteCond %{REQUEST_URI} !^/dev/
RewriteRule .* /pub/$0 [L]
DirectoryIndex index.php

Note if you install 2 magento site (maybe 2 difference version) seperated at one folder. You may need double extra efforts to setup following new changes. I'm not sure this approach is default support by magento

Not sure other web hosting providers support this or not but default as i remember all they provider root web start from folder that created

[dantaeusb]

Hi Tu,

Sure thing, I was talking about Magento 2.4.2. Yes, practically I understood that "document_root_is_pub" is now a default behavior. From my point of view, the problem is:

a) This change is not covered by official guides at all;
b) It's meaningless and confusing because it's always overridden by similar rules pub/.htaccess. I was thinking that I have deployment issues because I was desperately looking for index.php in root folder, which this file refers to.

[mrtuvn]

Yes must be someone need to update docs soon. This critical may affected to a lot store when upgrade to new version
You should try to point to index.php file in pub instead. Maybe that will help

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!