Remove 'wp-' from files and directories

[discobot]

---

Read-only archive: GitHub · Where software is built

Author: Yannick

Vote count: 7

Status: Declined

Tags:

• difficulty-hard

---

Comments

This can break compatibility with a lot of plugins/themes that have hardcoded path so for me actually until the project grow a lot is too soon.

~ posted by Daniele Scasciafratte

I agree with Daniele.

~ posted by KTS915

great plugins don’t but i m agree with you

~ posted by Yannick

Also agree with Daniel. Too soon.

~ posted by John

Oops… sorry for the name typo, Daniele.

~ posted by John

Agree, too early (if at all) to remove ‘wp-’.

~ posted by a ClassicPress Supporter

This is a huge breaking change without much benefit. For example, it is not possible to move wp-admin to a different path, because it is hardcoded in many places in the WordPress code. Plugins then come to depend on this for URLs, assets, path checks, etc.

~ posted by James Nylen

Just asking… Why isn’t it possible to do a find-replace search in a code editor to find all instances of “wp-admin” in the core and replace them with a variable which is defined elsewhere and can be updated? Why does this *have to be hard? Am I missing something?

~ posted by ALS

@ALS, yes you are missing something. Plugins and themes maintained by hundreds of devs target those paths. So it’s not enough to change core. You will have to change all repos of plugins and themes all over the world.
This is why for now CP is waiting. For now we still rely on the fact we can use WP themes and plugins safely.
That is why CP’s roadmap includes a plugin directory (directory, not a repo) so early on in v2. We need to grow an ecosystem before changing this. We need to attract devs and make this revolution smoothly.
We are going there step by step, and your enthusiasm is the same we share. It’s so good to see people understand the direction CP could evolve towards and are so eager to help!

~ posted by Elisabetta Carrara (Emc2)

AFAIK no framework, CMS uses a prefix.

~ posted by Viktor Szépe

This should not happen for a very, very long time. It’s beyond just branding, but keep in mind the thousands of web hosts, firewalls, scripts, and everything else in the internet that is configured to use wp- … to succeed, ClassicPress needs to first demonstrate code stability, as well as compatibility with WordPress as much as possible. Changing the prefixes (etc) could only happen after CP has achieved a significant market share, which is very far into the future, if ever…

~ posted by Jesse

[jssmith]

Hmmm!

And I thought the “wisdom of WordPress development” as far as themes and plugins were concerned, was to NOT use hard-coded paths to those folders, but to use the provided functions for referencing those folders?

Seems to me that IF those plugins and themes were developed, using hard-coded paths instead of the provided functions to return those path-values, then perhaps they weren’t really very-well thought out after all?

• Just my .02.

[joyously]

@jssmith

IF those plugins and themes were developed, using hard-coded paths instead of the provided functions to return those path-values, then perhaps they weren’t really very-well thought out after all?

That’s the problem. Themes and plugins can be written by anyone, and are often not well thought out. Some values don’t have a corresponding function, such as wp-config.php or wp-load.php and lots of files in wp-admin that plugins might load themselves to get some functionality (one case is media upload from front end).

[jssmith]

I also tried the provided/suggested constants for changing location/names of the wp-contents folder (and related), but apparently,

This also stopped any of the plugins and themes from being shown on the admin control panel. - Guess these constants weren’t even completely integrated in the WP core - as far as administration panel, etc?

It wouldn’t take much to replace all instances of hard-coded areas to the original folders - which are called AFTER wp-config.php is loaded - with the defined constants. There again, I have not taken the opportunity to fully explore all of the codebase. Time being the limiting factor.

[viktor]

At this stage with re-forking, it’s highly unlikely we’ll be modifying file/folder names to remove wp. If we ever decide to leave WP behind and we have a large team of core contributors, we will consider this. For now, the petition will be closed.