[wp-trac] [WordPress Trac] #14435: Network Admin

[WordPress Trac]

#14435: Network Admin
----------------------------+-----------------------------------------------
 Reporter:  ryan            |       Owner:                 
     Type:  task (blessed)  |      Status:  new            
 Priority:  normal          |   Milestone:  3.1            
Component:  Multisite       |     Version:  3.0            
 Severity:  normal          |    Keywords:  ongoing-project
----------------------------+-----------------------------------------------

Comment(by caesarsgrunt):

 > Links for js and css are hardcoded as well.
 That doesn't really matter, because these URLs aren't user-visible.

 > We don't support relocating wp-admin
 I realise that. But surely a simple thing like this, which has no affect
 on the standard setup and makes it easier for those who do want to use a
 different path (even if not 'supported') to access the admin, makes sense?

 Incidentally, why not support use of a different path to access wp-admin?
 (I'm not talking about renaming the directory, just using htaccess or an
 alias.) For some clients it is required, and for all users it makes life
 easier. {{{wp-admin}}} isn't as logical/intuitive (to the end user) or as
 easy to remember as {{{admin}}}.
 A constant in wp-config to set the path to be used in admin links would be
 trivial to implement, assuming relative links couldn't be used throughout.

 Ignoring my arguments above and assuming you don't want to officially
 'support' the use of a different url to access the admin, is there any
 reason ''not'' to use relative links anyhow? Even if only for consistency
 with most other links within the admin?

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/14435#comment:61>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software