[wp-trac] [WordPress Trac] #63771: Access denied issue with wp-includes/css/dist folder in WordPress 6.8.1-6.8.3
WordPress Trac
noreply at wordpress.org
Sun May 17 20:48:00 UTC 2026
#63771: Access denied issue with wp-includes/css/dist folder in WordPress
6.8.1-6.8.3
-------------------------------------------------+-------------------------
Reporter: 369work | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting
| Review
Component: Administration | Version: 6.8.3
Severity: normal | Resolution:
Keywords: css dist file-permissions windows | Focuses:
access-denied |
-------------------------------------------------+-------------------------
Comment (by jdeep):
Hi @369work.
I took a look at the description and one thing caught my eye. You
mentioned that you got this error:
''file_get_contents(D:\xampp\htdocs\wordpresswp-includes/css/dist/block-
library/common.min.css): Failed to open stream: Permission denied
'' Interesting part about this is the missing separator between
`wordpress` and `wp-includes` along with the mixed use of forward and
backward slashes.
The error is most likely originating from [https://github.com/WordPress
/wordpress-develop/blob/31a8ce49797f926956b277e18686890136ab584a/src/wp-
includes/script-loader.php#L1821 this line in core].
Can you check your `wp-config.php` to see what your `ABSPATH` is set as
and if it contains a trailing slash like
[https://core.trac.wordpress.org/browser/tags/6.8/wp-config-
sample.php?marks=98#L98 here]?
If it does not, then that is most likely the issue since `ABSPATH` is
expected to have trailing slash.
Regarding not being able to edit core files using the Windows File
Explorer, I will have to investigate deeper into this through a Windows
machine and I will post here if I find anything.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/63771#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list