Custom admin url

[colymba]

Hi!

Coming from this question on SO, http://stackoverflow.com/questions/24125655/how-can-i-change-the-admin-path-in-silverstripe-3-1-x

Currently there isn't any proper way to change the default admin URL (correct me if am wrong), so I had a quick look around and at a first glance this shouldn't be too hard to implement.

For the framework, 99% can be done via YML config already, it just is not very centralised.

But then there is the matter of the CMS and other modules, where the admin url seem be be hard-coded a lot more.

The is an old issue on Github about it https://github.com/silverstripe/silverstripe-cms/issues/712

I would imagine this can be solved with things like:

• Global yml config for all
  
• then adminURL() with TemplateGlobalProvider for templates
  
• and adminURL key in ss namesapce for JS
  

So what is the consensus on this?

And can anyone see major problem that would be encountered if implemented?

Thierry

[Ingo Schommer]

Hello Thierry, that sounds like a good approach - looking forward to your pull request :) 

[Patrick Nelson]

Has this been implemented yet? I followed the maze, too. Started with the StackOverflow question, searched through github issues, then got directed to "ss-dev" and ultimate found it here after a quick search. 

Anyway -- I'm thinking this is a pretty important feature as well. I'd love to see this. On the other hand, if this *has* already been implemented, it should be documented or easier to find!

- Patrick

[Thierry Francois (colymba)]

I've implemented it in this pull request last year:

https://github.com/silverstripe/silverstripe-framework/pull/3274

But there hasn't been any movement or feedback ever since.....

[Patrick Nelson]

Well then, let me recommend a few things:

1. Rebase your current code on the latest version of the branch that your code was originally branched from (didn't clone down your copy so not sure). Then push your branch again (overwriting known changes) so that it will re-trigger the automated tests on the CI server (Travis, Behat, etc) since I think that got forgotten when I think the tests were still a bit broken? Not sure what was going on there (just what I gathered).
   
   
2. I'll chime in there to "bump" the thread a bit.

I know they say that "security through obscurity is not security," but security is also very much like an onion and the more layers and problems you can throw at potential wannabe hackers, the better. I'm all for this!

--
You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to silverstripe-d...@googlegroups.com.
To post to this group, send email to silverst...@googlegroups.com.
Visit this group at http://groups.google.com/group/silverstripe-dev.
For more options, visit https://groups.google.com/d/optout.