1

I want to know whether I can/should make /sitecore redirect to sitecore.mysite.com, and if so, how would I go about doing this?

I've figured out how to set up sitecore.mysite.com, and even have the shell and admin as /shell and /admin respectively, without the preceding /sitecore part. What I can't figure out is how to make the old links redirect to the sub-domain.

I also realized that the login page only works if it is /sitecore/login, and there may very well be other links that don't work properly.

Is any of this possible in Sitecore 9?

Improve this question
3
  • 1
    Why are you thinking changing sitecore url to sitecore.mysite.com? Do you have any particular reason?
    – Peter Procházka
    Commented Jun 27, 2018 at 4:35
  • Just a way to separate the admin controls from the main site. It’s common practice in some other content management systems and I’ve done this before with Sitecore 6.5, but for some reason I can’t figure out Sitecore 9.
    – Xalor90
    Commented Jun 27, 2018 at 7:33
  • 1
    I don't recommend/advise doing this in any context.
    – Pete Navarra
    Commented Mar 14, 2019 at 23:17

1 Answer 1

Reset to default
0

I found a way to set up my projects to support the desired functionality, though in a roundabout way. Basically, in the install script, I just set it up to install cms.sitename, then I modified the web.config to point the cms.sitename to the preview mode and added a new entry for www.sitename which points to the published site. The Sitecore panel is now accessible only from cms.sitename.

Also, to further clarify, this is on a local environment. As to the original question and the ability to drop /sitecore from the url, this does not seem possible or advisable, but is also not a concern since I was able to successfully set up the CM on a subdomain.

Improve this answer
3
  • 2
    I would recommend adding screenshots and code snippets to create a more complete answer to your question.
    – Pete Navarra
    Commented Mar 14, 2019 at 23:13
  • For clarity, you are talking about LOCAL development, not a deployed environment?
    – Pete Navarra
    Commented Mar 14, 2019 at 23:14
  • 1
    For local environment, you only need to use the Standalone role. However, what you asking, is instead of XP0 on your local, running XP1 (where CM and CD IIS instances are separated.
    – Pete Navarra
    Commented Mar 14, 2019 at 23:16

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.