Opened 6 years ago
Last modified 6 years ago
#51287 new defect (bug)
Administrators & Editors can't create localfile links in a multisite installation
| Reported by: | peikgabriel | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Awaiting Review |
| Component: | Formatting | Version: | |
| Severity: | major | Keywords: | |
| Cc: | Focuses: | multisite |
Description
Steps to reproduce:
Clean WordPress Multisite installation.
Create a user with Administrator (or Editor) capabilities, not Super Admin.
Login as the new user.
Create a new page, and create a local file link in the visual editor.
Enter a local file URL, e.g. localfile:E:\foobar\
Publish and refresh the page.
The link has now been stripped into a \foobar\.
Note, if you try this with a Super Admin user it works as expected, and the link is correctly created.
Why does WP strip the localfile:E: part of the link if the user is not an admin?
Change History (1)
Note:
See TracTickets
for help on using tickets.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Hi there, welcome to WordPress Trac! Thanks for the report.
Just noting that this is likely an issue with the KSES library stripping out a part of the link due to
localfile:not being in the list of allowed protocols.