[wp-hackers] File names in WP base folder

[Boris Anthony]

Probably because it's just been added (and about time! thanks Mr  
Torrez!)

tangentially, I've enevr understood why we have all these files  
floating around. I guess ideally I'd run WP with the index.php file  
pulled out one level

/webroot
	index.php
	/wordpress

or for example

/webroot/myblahg/
	index.php
	/wordpress-bits

But that's just me. and maybe there's a clean way to do this already  
that I don't know about? :D

B.

On 15-Mar-07, at 7:44 PM, Alex Günsche wrote:

> Hi,
>
> I see that in the SVN, there is a file named "app.php" in the  
> WordPress
> base folder. I think it would better if this file was named "wp- 
> app.php"
> or similarily.
>
> The reason is the following: Especially when you install WordPress  
> into
> you DocumentRoot, it is likely that there are WP-independent files
> inside it, too. Now if you want to upgrade, you must remove all old WP
> files from the base folder, and having non-standardized names can  
> cause
> confusion. This problem is especially severe, when you use a solution
> which manages upgrades automatically. Such an application cannot just
> delete any file from the base folder, but it usually has a predefined
> list and/or pattern of files to delete and replace. Besides, using
> non-standardized patterns could lead to name collisions, e.g. I could
> already have a non-WP file named "app.php" in my WP base folder.
>
> Therefore I think it would be best, if all WordPress files in the WP
> base folder are prefixed with wp- (except index.php of course, and  
> maybe
> the legacy xmlrpc.php).
>
> What do you think?
>
>
> Regards
> Alex
>
> -- 
> Alex Günsche, Zirona OpenSource-Consulting
> work: http://www.zirona.com/ | leisure: http://www.roggenrohl.net
> PubKey for this address: http://www.zirona.com/misc/ag.ml2007.asc
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers