WordPress 6.0-beta2-53224 not creating .htaccess

[campation]

on my development site (Plesk Obsidian, Centos 7.9) a fresh installed latest WP 6.0 beta2 does not create an .htaccess file at all.

Steps:

• wordpress-6.0-beta2.zip does not contain .htaccess
• unzipped and uploaded to site
• domain opened in browser
• run set up process until login
• no .htaccess created
• table wp_options 'permalink_structure' contains "/index.php/%year%/%monthnum%/%day%/%postname%/"
• login as admin
• selecting a permalink structure and saving on /wp-admin/options-permalink.php
• table wp_options 'permalink_structure' contains "/%postname%/" as expected
• no .htaccess created
• repeated saving of permalink structure does not help to create .htaccess
• no entry in debug.log
• as to be expected: permalinks not working in front end
• only solution: create a basic .htaccess manually

To me this seems a severe bug.

Found this while testing one of my plugins on WP 6.0 before updating it to plugin repository

Chris
PS: no answer required

[peterwilsoncc]

Hi @campation and welcome to trac!

I've done some testing (see below) and was unable to reproduce the error. Are you able to provide further information about your server's set up.

• is the root directory of your WordPress install writable by the server? If you need to manually create a wp-config.php file during the installation step, then it probably is not.
• does your web server use Nginx or Apache?
• Anything else you know about the set up of your web server that might be relevant?

I was discussing this with another WordPress contributor but they were unable to reproduce it either.

I've moved this on to the 6.0 milestone for visibility but it would be great to hear back with the extra details of your environment.

---

Testing notes

Environment

OS: macOS 11.6.5
Development environment: MAMP 6.6
PHP: 7.4.21
WP Version: 6.0-beta2-53241

Testing steps

1. Set MAMP path to WP Beta
2. Create database for use in PhpMyAdmin
3. Visit localhost:8888 and follow installation proceedure
4. Confirm htacess file created ☑️
5. Visit localhost:8888/2022/04/22/hello-world/ to ensure rewrite works ☑️

[campation]

Hi @peterwilsoncc,

I repeated everything this morning with a freshly downloaded WordPress 6.0-beta2-53240 (ticket was opened for 52324):

My environment

• Linux Server Centos 7.9 with Plesk Onyx latest version (updated yesterday), 256GB RAM, 16 core etc, no web hosting
• Nginx proxies requests to Apache
• on this server some 30 productive WordPress websites (5.9.3) are running, I'm a plugin developer, too, so I know what I'm doing
• subdomain ​https://beta.domain.com/ with SSL certificate
• I tested WordPress 6.0 with PHP 7.4.29, 8.0.18 and 8.1.5
• *FPM by Nginx*

Test procedure

• create empty database
• upload WP 5.9 by fpt
• open frontend ​https://beta.domain.com/ and configuration and login as admin
• .htaccess created as should be, everything working as usual

then the same with WP 6.0 beta

• delete all tables from database
• delete www root on server
• upload fresh unzipped WordPress 6.0-beta2-53240
• open ​https://beta.domain.com/ and configuration and login as admin
• no .htaccess created
• this repeated with all 3 above mentioned versions of PHP - same result, the problem does not depend on PHP

Strange to me after this test with WP 6.0:

• .htaccess is missing
• wp-config.php is left "writable by anybody" (rw-rw-rw 0666)
• initial permalinks are set to "/index.php/%year%/%monthnum%/%day%/%postname%/" (/index.php is a fault)
• setting other permalink structure is saved to db (without "/index.php")
• still no .htaccess created
• Apache error.log empty
• calling hello-dolly -> 404

I then tried the same with PHP 7.4.9 * Nginx switched OFF *

• same result
• no .htaccess
• wp-config.php writable by everybody
• permalink with "/index.php ...."

So the problem does not seem to depend from PHP version nor Apache/Nginx

Hope this helps!

Chris

[costdev]

@campation Can you verify what Tools > Site Health > Info tab > Filesystem Permissions shows?

N.B. The reason I'm specifically requesting this screen's data is so we can see what WordPress is seeing.

[campation]

of course!

Shows whether WordPress is able to write to the directories it needs access to.

The main WordPress directory Writable
The wp-content directory Writable
The uploads directory Writable
The plugins directory Writable
The themes directory Writable

[chaion07]

Thanks @campation for reporting this. We reviewed this ticket during a ​recent bug-scrub session for WP 6.0 and based on the feedback we're updating the ticket with the following changes:

1. Removing the 'reporter-feedback' keyword

Additionally, we'll reach out to Hosting Community Team before RC1 for a feedback on the ticket.

Props to @costdev

Cheers!

[costdev]

With 6.0 RC1 starting soon, I'm moving this to the Awaiting Review milestone so that we can continue to try to reproduce this issue.

[JeffPaul]

@campation it seems this was originally reported on the 6.0 Beta 2 release. Have you been able to replicate all the way up to RC 4 as well?