Hello,
I don’t use EE very much, so I’m hoping someone can help me. I had a channel that was set up for testing purposes and worked great. The channel was Resources and the structure worked like this:
For the listing page: /resources
For the single listings: /resources/single/<dynamic name of resource channel post>
This seemed to work great because the channel was at the root. However, now the channel needs to live somewhere else:
/the-journey/resources/
/the-journey/resources/single/<dynamic name of resource channel post>
I cannot get the single channel pages to resolve at that URL. I’ve tried updating the channel’s URL settings various ways. Is there a way to do this?
Thanks, Stefanos. Unfortunately, I already am using that. It seemed to work before. But once I moved the page one level down, it just gives a 404 page for any page that is:
/the-journey/resources/single/[entry-title]
My template for single is:
{embed="site/_header" prefix="resources" channel="resources"}
{exp:channel:entries url_title="{segment_4}"}
...all the code
{/exp:channel:entries}
But it seems like the problem is related to the routing of the channel.?
You might have a look at using a template route here. What you’re doing should be pretty straight-forward. The template route for the single-entry template would be something like:
/the-journey/resources/single/{resource:alpha_dash}
with ‘Require all variables’ enabled. Then, the channel entries tag would be something like:
{exp:channel:entries channel="resources" dynamic="no" url_title="{segment:resource}"}
{/exp:channel:entries}
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.