Make WordPress Core

Opened 10 years ago

Closed 10 years ago

#8089 closed enhancement (wontfix)

Move most root files to wp-includes and set an include internally

Reported by: sc0ttkclark Owned by:
Milestone: Priority: lowest
Severity: major Version:
Component: General Keywords:
Focuses: Cc:


This long list of wp-*.php files is a bit big. Isn't it time that we have those run through index.php too? Why do all of these files have to be in the root directory? If there's a reason, why not put all the files that are in the wp-includes there too?

So I say:

  1. Move files to wp-includes (if there's any conflict in naming, then of maybe have a subdir for these root files)
  1. WordPress internal linking should be set to include these files upon calling them (if permalinks turned on), otherwise all calls to them should be through index.php/wp-login/ etc and all page/post names with whese wp-* should be 'banned'
  1. Then we have 6 root files/folders in the installation: wp-admin,wp-content,wp-includes,index.php,license.txt,readme.html

So there's gotta be a way to do this, and I'm giving the 'go' person the preliminary idea. I'm going to make a plugin that does just this, but I'm sure my code won't be very useful since it's probably not the way you'll end up doing it.

Change History (5)

#1 @DD32
10 years ago

  • most of the files are entry-points for when you're not using rewrite permalinks
  • index.php/login/ doesnt work for all, its also "ugly" much more so than /wp-login.php
  • a number of files is never a bad thing, mind you, most do allready just load WP and kick the process off

overall.. a -1 to the idea from me,

#2 @jacobsantos
10 years ago

  • Priority changed from normal to lowest
  • Severity changed from normal to major

-1 from me too, for what it is worth.

wp-includes is the library files portion of WordPress and shouldn't be made dirty by adding miscellaneous files.

#3 @westi
10 years ago

  • Milestone changed from 2.8 to 2.9


A lot of work has been done to move duplicated code out of these files and into wp-includes but they still server a purpose when not using pretty permalinks.

It could be done by using index.php for everything but we still need to support old the old links to these files.

#4 @mrmist
10 years ago

-1 from me too, FWIW.

The concept of using index.php/wp-login/ for the sake of saving a few files in the root is counter-intuitive. It favours the site developer over the end-user, which is the wrong way around for a web app. Essentially in order to make things appear "neater" within the source directories, you're imposing a non-standard file referencing approach on the user. To me that's the wrong thing to do.

#5 @azaozz
10 years ago

  • Milestone 2.9 deleted
  • Resolution set to wontfix
  • Status changed from new to closed
  • Version 2.8 deleted

Seems like a wontfix...

Note: See TracTickets for help on using tickets.