[wp-trac] [WordPress Trac] #63771: Access denied issue with wp-includes/css/dist folder in WordPress 6.8.1

WordPress Trac noreply at wordpress.org
Thu Nov 13 06:44:35 UTC 2025


#63771: Access denied issue with wp-includes/css/dist folder in WordPress 6.8.1
-------------------------------------------------+-------------------------
 Reporter:  369work                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Administration                       |     Version:  6.8.1
 Severity:  normal                               |  Resolution:
 Keywords:  css dist file-permissions windows    |     Focuses:
  access-denied                                  |
-------------------------------------------------+-------------------------

Comment (by 369work):

 In my environment, this issue always occurs when creating a new original
 block theme.
 The permissions (ownership) of the contents of the (wp-includes/css/dist)
 folder change, making them inaccessible.

 However, the exact timing is unknown.
 It seems to occur unnoticed while duplicating, deleting, or editing a
 pattern in the theme editor, and I notice it when an error message appears
 on the site.
 file_get_contents(D:\xampp\htdocs\wordpress//wp-includes/css/dist/block-
 library/common.min.css): Failed to open stream: Permission denied

 You do not have ownership of "D:\xampp\htdocs\wordpress\wp-
 includes\css\dist".

 [What I can't do]
 Overwrite and copy only the wp-includes folder
 Delete and re-create the dist folder
 Force ownership
 Delete the entire parent folder
 Delete in safe mode

 Only formatting the D disk was successful.

 [Reproducible environment]
 WordPress version is 6.8
 Windows 11 24H2
 MAMP
 xampp
 System is on C disk
 xampp and MAMP environment are on D disk
 Since xampp and MAMP are not in the system user folder, I suspect this is
 due to an administrator change.
 Apache execution permissions may also be a factor.

 [Current situation]
 AI recommended that this issue would not occur if I used Local by
 Flywheel, so I switched to it.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/63771#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list