Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#2739 closed defect (bug) (wontfix)

Reduce number of files in the root

Reported by: mikaelstaldal Owned by: anonymous
Priority: normal Milestone:
Component: General Version: 2.0.2
Severity: minor Keywords: files
Cc:

Description

It would be nice if the number of files in WordPress installation root could be reduced. Sometimes you want to install WordPress in the root of a website, and have some other stuff there too.

I guess it would be quite easy to move most of the *.php files in the root to the wp-includes directory.

Ideally, only index.php, wp-config.php and .htaccess should be in the root.

Change History (5)

Take a closer look at what the rest of those root files do. Most are valid web resources and are not merely "includes" so they don't really belong there. It may be wise to consolidate and refactor some of those files as includes rather than web interfaces but simply moving them en masse doesn't make much sense.

If you could be more specific in your request, it might make more sense.

  • Resolution set to wontfix
  • Status changed from new to closed

That ship has sailed. We can't count on mod_rewrite, and the files in the WP root are web resources, so we can't move them.

At any rate, moving WordPress to its own directory takes all of 5 seconds and is a transparent action. There's no reason that you'd HAVE to install WordPress in the root of your blog.

OK, (most of) the files in WP root are web resources and should not be moved to wp-includes. So what about creating a new directory "wp-resources" and move them there?

And move wp-login.php to the wp-admin directory.

we can't move any files that are web resources. people have links to them. people expect them to be there.

the solution, for keeping things clean, is having WP in its own directory.

Note: See TracTickets for help on using tickets.