<p>The way the demo templates are set up they are a series of included sub-templates.
So you would need to change the references to <code>shop/</code> for each of the <code>{% include %}</code> statements.</p>

<p>Try doing a find/replace on the templates within your <code>/store</code> directory. See what that does.</p>

<p>Craft/Commerce places no restriction on how you name things. You don't need to use the demo templates at all if you don't want to. You can name them and place them wherever you like.</p>

CC BY-SA 4.0
2019-11-22T12:31:29.477Z
I had already tried that but the frontend page I am seeing at the /store/ URL is being served from the /shop/ directory still (I made an edit to the _includes/nav.html in /store/ and it made no difference but did the same to the one in /shop/ and could see the edit in the frontend). It's as if there is some of setting that specifies where to serve the files from.
zigojacko
CC BY-SA 4.0
2019-11-22T14:42:38.800Z
You were right, I had to modify variables like this one `{% extends 'shop/_layouts/main' %}` to the 'store' path in order for the header, nav etc to be loaded from the correct place.
zigojacko
CC BY-SA 4.0
2019-11-22T17:22:46.017Z
Yep those are pulling in the partial templates. It's a path to the partial. As mentioned, the template can be set up however you like. Personally, I'm not a fan of the way the demo templates are done - it's far too complex for a newcomer. But it you work through them diligently then you'll pick things up soon enough.
foamcow
CC BY-SA 4.0
2019-11-22T12:23:18.307Z
2019-11-22T12:23:18.307Z
foamcow
<p>I am completely new to Craft and to be honest, really struggling to get my head around how it all works at the moment.</p>

<p>I've got loads of, what I feel, is quite basic questions that should be relatively straight forward but after searching numerous documentation and online posts, can't find out how to do any of it.</p>

<p>So figured asking here might be the quickest way of learning how to work with the platform.</p>

<p>So in a development environment, I've got Craft CMS set up with the Pro version of Commerce. By default, this comes set up at /shop/.</p>

<p>What do I have to do exactly in order to change the 'shop' URL to something else, for example /store/?</p>

<p>I tried duplicating the 'shop' directory as 'store' and whilst the pages seem to load at /store/<em>, the templates are still being served from /shop/</em> (tested by modifying them).</p>

<p>If someone could list step by step the correct process for changing this, that would be very helpful.</p>

<plugin-craftcommerce>
Set base 'shop' URL to something else in Commerce
# Set base 'shop' URL to something else in Commerce

(Asked by: username_0 on 2019-11-22)

I am completely new to Craft and to be honest, really struggling to get my head around how it all works at the moment.

I've got loads of, what I feel, is quite basic questions that should be relatively straight forward but after searching numerous documentation and online posts, can't find out how to do any of it.

So figured asking here might be the quickest way of learning how to work with the platform.

So in a development environment, I've got Craft CMS set up with the Pro version of Commerce. By default, this comes set up at /shop/.

What do I have to do exactly in order to change the 'shop' URL to something else, for example /store/?

I tried duplicating the 'shop' directory as 'store' and whilst the pages seem to load at /store/*, the templates are still being served from /shop/* (tested by modifying them).

If someone could list step by step the correct process for changing this, that would be very helpful.

**Tags:** plugin-craftcommerce

---

## 1 answers

### Answer by username_1 on 2019-11-22. Score: 1 | Accepted answer

The way the demo templates are set up they are a series of included sub-templates.
So you would need to change the references to `shop/` for each of the `{% include %}` statements.

Try doing a find/replace on the templates within your `/store` directory. See what that does.

Craft/Commerce places no restriction on how you name things. You don't need to use the demo templates at all if you don't want to. You can name them and place them wherever you like.

> **Comments:**
> **username_0**: I had already tried that but the frontend page I am seeing at the /store/ URL is being served from the /shop/ directory still (I made an edit to the _includes/nav.html in /store/ and it made no difference but did the same to the one in /shop/ and could see the edit in the frontend). It's as if there is some of setting that specifies where to serve the files from.  
> **username_0**: You were right, I had to modify variables like this one `{% extends 'shop/_layouts/main' %}` to the 'store' path in order for the header, nav etc to be loaded from the correct place.  
> **username_1**: Yep those are pulling in the partial templates. It's a path to the partial. As mentioned, the template can be set up however you like. Personally, I'm not a fan of the way the demo templates are done - it's far too complex for a newcomer. But it you work through them diligently then you'll pick things up soon enough.  

---

