22976 Posts in 11702 Topics by 2826 members
Page: 1 2
|Go to End|
11 September 2009 at 11:01pm
Yes, but this means if the user changes the Title... it breaks
11 September 2009 at 11:03pm Last edited: 11 September 2009 11:05pm
Refer to the id instead? Not so nice anymore...
12 September 2009 at 1:04am Last edited: 12 September 2009 1:06am
Martimiz, I think you're wrong: 'if' structures accept the != operator. What they don't accept is apostrophes or spaces or non-ASCII characters, so:
<% if MenuTitle != 'My Headline' %>
Does not work, but:
<% if URLSegment != my-headline %>
Hope it helps,
12 September 2009 at 2:29am
You're absolutely right - that was definitely mixed up - must have been the holydays. Sorry Pidgeon, I guess I'll go and hide for a while
12 September 2009 at 3:27am
Hey Martimiz, don't hide! Your contribution is useful.
If I know well this issue is because I'm using SS for multi-lingual sites. The actual 'if' parser is useless with Titles, MenuTitles and the such as long as it does not recognize spaces and special characters. Happily, with SS, it's easy to find workarounds.
14 September 2009 at 9:45pm
So many excellent suggestions, I can't thank you enough.
@Pigeon. Thanks for being so thorough with your explanation, it's helped my understanding of the SS framework a lot.
For anyone following this thread - I'm actually going to use the Martimez/Juanitou 'quick-n-dirty' solution (no offense intended). In my case I have a one-off requirement to move one item from the left-bar to the right-bar. So I think that hard-coding it is actually the 'safe' option in this case and it doesn't give the client any extra checkboxes to worry about. I've used <% if ID != 54 %> to identify the particular node, so the client can alter the page title if neccessary.
If the client's requirement changes in the future, I know I have the 'elegent' solution to fall back on.
Again, thanks all.
Page: 1 2
|Go to Top|