bret at pectopah
Dec 8, 2010, 1:13 PM
Post #3 of 4
I second David's suggestion about the second OC, and just using the same
Re: Fixed story type to use non-fixed URI???
[In reply to]
element type and the same template as for the stories with dated URIs.
If the new section with the fixed URIs is in its own category, you could
make a category template that checks the OCs and reassigns them if
necessary, which would cut down on the user hassles too.
Hope this helps,
On Wed, 2010-12-08 at 12:27 -0800, David E. Wheeler wrote:
> On Dec 8, 2010, at 11:07 AM, Schults, Chris wrote:
> > Unless I'm missing something, I'm left with creating a new story type
> > that is a duplicate of "Story" in all ways except that it is non-fixed,
> > or refactor my templates to somehow utilize utility templates. As I'd
> > rather not do either of these, is there a way to make a fixed story type
> > use the non-fixed URI syntax via a template?
> Create a new output channel with its "Fixed URL" template including the date, and make it include templates from your main output channel. Then add it as an option to your Story element type. Then all that has to happen in the new section is users would create a Story, then add the new OC and remove the old OC.
> That's more of a PITA for your users, though. What I've done in the past is to create a duplicate story as you described, but instead of utility templates, you just make the template call the original template. So if your new story type is called dated_story, then dated_story.mc would be something like this one-liner:
> % $m->comp('/story.mc', %ARGS);
Pectopah Productions Inc.
bret [at] pectopah