#45988 closed feature request (wontfix)
Suport for vendor/oem integration code loading
Reported by: | calin | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | General | Keywords: | |
Focuses: | Cc: |
Description
Currently there are 3 main ways to load code into WordPress: plugins/themes, mu-plugins and drop-ins. All live under wp-content
folder. As integrator/hoster it's best to not touch user code living under wp-content
.
As a result I'm proposing adding a new folder wp-oem
at the same level as wp-content
, which allows loading drop-ins (object-cache.php
, advanced-cache.php
, db.php
, sunrise.php
, etc.) and also a mu-plugin.php
file with integrator's custom code.
Change History (2)
#1
@
6 years ago
- Milestone Awaiting Review deleted
- Resolution set to wontfix
- Status changed from new to closed
#2
@
6 years ago
Hi @pento,
I am disappointed by such an abrupt dismiss of the issue and let me explain why: closing the issue without further discussion, or at least allowing it more time to settle down, does not leave the impression of an open community looking forward to receiving meaningful contributions and a healthy evolution.
It's really odd for me to bring up the discussion regarding a closed and wontfix issue to a Slack channel if that was your suggested course of action.
Thank you for the suggestion, @calin!
Unfortunately, changing WordPress' folder structure isn't really possible. Many hosts have a variety of strict security rules in place, only allowing PHP to be executed from the folders that are currently defined.
I noticed you're already in the hosting community Slack channel, I'd recommend bringing it up there for discussion of hosting best practices.