Mailing List Archive

// Add your reply above here
==================================================
Ian Gibbs updated this ticket at June 20th, 2011 @ 07:57 PM
* Tag changed from "usability" to "usability userinterface"

--------------------------------------------------------------------------------

Assigned: Bugs (at bricolage)
State: new
View this ticket online: http://bricolage.lighthouseapp.com/projects/29601/tickets/270-file-name-setting-visible-but-ineffective

Stop being notified of this ticket's changes: http://bricolage.lighthouseapp.com/projects/29601/tickets/270-file-name-setting-visible-but-ineffective/watch
Update your Profile: http://bricolage.lighthouseapp.com/profile
Support: support@lighthouseapp.com or http://help.lighthouseapp.com

// Add your reply above here
==================================================
theory updated this ticket at June 21st, 2011 @ 03:03 AM
* State changed from "new" to "invalid"
This is not correct. Even if you don't have `STORY_URI_WITH_FILENAME` set, the specified value is used to write the file name to disk. It's just not included in URIs in the database.
--------------------------------------------------------------------------------

Assigned: Bugs (at bricolage)
State: invalid
View this ticket online: http://bricolage.lighthouseapp.com/projects/29601/tickets/270-file-name-setting-visible-but-ineffective

Stop being notified of this ticket's changes: http://bricolage.lighthouseapp.com/projects/29601/tickets/270-file-name-setting-visible-but-ineffective/watch
Update your Profile: http://bricolage.lighthouseapp.com/profile
Support: support@lighthouseapp.com or http://help.lighthouseapp.com

// Add your reply above here
==================================================
Ian Gibbs updated this ticket at June 21st, 2011 @ 10:06 AM

This ticket is based on the response I received on the users mailing list. Here's the mail I sent and the response I got. If it isn't correct, then it isn't working (see my experience below). David's response implies what I saw is expected behaviour. I solved the problem by using two different extensions as David suggested. Then, after republishing, the output from both channels appeared without any further changes.

Dear all,

I am attempting to publish a story in multiple formats - a full story, and extract of the story. My reading of the documents implies that I need to use multiple output channels going to the same destination. I have created multiple output channels, both of type HTML::Template, with different values for 'File Name'. One is set to 'extract', the other is set to 'index'. Both are set with the same URI format, so I think I should be expecting /%{categories}/%Y/%m/%d/%{slug}/index.html, and extract.html in the same folder. My story element is 'Post', and I have two post.tmpl and post.pl templates, one associated with each of the two output channels.

What I actually get is /%{categories}/%Y/%m/%d/%{slug}/{slug}.html, and nothing else. This file is from whichever of the two output channels is set as primary on the story. Even when there is only one output channel, I still get {slug}.html instead of the name I set in 'File Name'.

Why is the File Name value being ignored? Can I not see the two targets because they are both being written with the same name?

Thanks for the help.

Ian

On Jun 10, 2011, at 9:36 AM, Ian Gibbs wrote:

> > Why is the File Name value being ignored? Can I not see the two targets because they are both being written with the same name?
You will need to enable the `STORY_URI_WITH_FILENAME` `bricolage.conf` directive.

But I tend to recommend instead, unless you have an existing file naming convention to replicate, that you just use a different suffix for each Output Channel. That way, the URI ends directory name, and everything in that directory is the same story. You have one URI for all representations of a story.

Best,

David
--------------------------------------------------------------------------------

Assigned: Bugs (at bricolage)
State: invalid
View this ticket online: http://bricolage.lighthouseapp.com/projects/29601/tickets/270-file-name-setting-visible-but-ineffective

Stop being notified of this ticket's changes: http://bricolage.lighthouseapp.com/projects/29601/tickets/270-file-name-setting-visible-but-ineffective/watch
Update your Profile: http://bricolage.lighthouseapp.com/profile
Support: support@lighthouseapp.com or http://help.lighthouseapp.com

// Add your reply above here
==================================================
theory updated this ticket at June 21st, 2011 @ 04:44 PM

Ah, I see the confusion. You have the "Use slug for filename" (or similarly named) option checked in that output channel. Uncheck it.
--------------------------------------------------------------------------------

Assigned: Bugs (at bricolage)
State: invalid
View this ticket online: http://bricolage.lighthouseapp.com/projects/29601/tickets/270-file-name-setting-visible-but-ineffective

Stop being notified of this ticket's changes: http://bricolage.lighthouseapp.com/projects/29601/tickets/270-file-name-setting-visible-but-ineffective/watch
Update your Profile: http://bricolage.lighthouseapp.com/profile
Support: support@lighthouseapp.com or http://help.lighthouseapp.com

// Add your reply above here
==================================================
Ian Gibbs updated this ticket at June 23rd, 2011 @ 09:06 AM

OK that has fixed it, thank you. In that case, I'd like a ticket to make File Name and Use Slug for Filename mutually exclusive. Do that in this one, or open a new one?
--------------------------------------------------------------------------------

Assigned: Bugs (at bricolage)
State: invalid
View this ticket online: http://bricolage.lighthouseapp.com/projects/29601/tickets/270-file-name-setting-visible-but-ineffective

Stop being notified of this ticket's changes: http://bricolage.lighthouseapp.com/projects/29601/tickets/270-file-name-setting-visible-but-ineffective/watch
Update your Profile: http://bricolage.lighthouseapp.com/profile
Support: support@lighthouseapp.com or http://help.lighthouseapp.com

// Add your reply above here
==================================================
theory updated this ticket at June 23rd, 2011 @ 03:36 PM

No, you can't do that. Fixed story types are not required to have a slug, and therefore fall back on the specified file name. They are not mutually exclusive.
--------------------------------------------------------------------------------

Assigned: Bugs (at bricolage)
State: invalid
View this ticket online: http://bricolage.lighthouseapp.com/projects/29601/tickets/270-file-name-setting-visible-but-ineffective

Stop being notified of this ticket's changes: http://bricolage.lighthouseapp.com/projects/29601/tickets/270-file-name-setting-visible-but-ineffective/watch
Update your Profile: http://bricolage.lighthouseapp.com/profile
Support: support@lighthouseapp.com or http://help.lighthouseapp.com