Answered TV Naming Convention

Revo 2.5.2
getUrlParam
TagLister
NewsPub
TinymceWrapper

I'm using NewsPub and TinymceWrapper (specifically TinyMagicPublisher) for front-end editing and TagLister for filtering. Everything works fine.

The NP forms use several TVs, all of which have a single-word name except for two TVs which use 2 words with a space between. One is a text field [ [*field text] ] and the other a picker [ [*field picker] ].

"field text" is optional and works as expected. Meaning if given a value the form is saved, the resource is created and the TV value appears on the front-end. All good.

However, "field picker" is required but its value is not being saved, and the resource is not created. The exception is if it is not an optional field in which case everything works perfectly.

I also tried a different naming convention: "fieldPicker", and of course it worked perfectly so clearly something about a name with two separate words is causing a problem, but only if the field is required.

But I need the field to be required and I need to use "field picker" (2 words) when displaying tagLister results. The two-word naming scheme makes more sense when displaying front-end results.

Is there any way around this using regex or some other PHP sleight-of-hand, or am I stuck with a single word TV name? [ed. note: todd.b last edited this post 9 years, 9 months ago.]

The exception is if it is not an optional field in which case everything works perfectly.

Erm ... "not an optional field" == "required". I assume you mean that it's fine when the field is not required.

That said, I can't see any reason why having a space should cause a problem as long as the &required property has back-ticks around the full value and the name is spelled exactly the same in the &required property as it is in the &show property, and in the name attribute of the form.

TVs have both a name and a caption field so you can use a name with no space but still display the TV's caption (with a space) when displaying the TV in the front end.

It's a policy for some of us to have the 'name' field space-free just to avoid the problem you're having. The problem should never happen, but when you're using a bunch of code from other developers it could.

[Laughs] Yes, that's what I meant.

Ok, so it shouldn't be a problem. That's good to know. Normally I would avoid the space when naming elements but in this case it would be useful.

Out of curiosity, in the call is there a way to display the TV "Caption" in the filter results instead of the TV "Name"?

Reason being, I could stick with a single-word TV name which means I avoid any problems creating new resources, but I could still display a multi-word phrase (i.e. 'Caption') when using `getUrlParam` which, when all is said and done, is the desired end-result. [ed. note: todd.b last edited this post 9 years, 9 months ago.]

If you're using NewsPublisher, you can use the &captions property to show a custom caption for any field.

For displaying the caption, it would depend on what you're using to aggregate them. For example, I'm not sure if getResources sets all TV fields or just the value field when processing the Tpl chunk.

You could just try this in your inner Tpl chunk and see if it works:



Worst case, you could write a simple snippet to get the captions using the TV ID as a property.

Well, here's the specific code used to filter tag results:

Then on the results page I'm using [[!getUrlParam? &name=`key`]] to display the TV name time in [[+resultsMessage]].

But instead of showing the TV name time I want to show the caption completion time in [[+resultsMessage]].

I've been experimenting with
[[+caption]]
but so far I've been unable to get the desired result.

You're putting that caption tag in the Specs Link Tpl chunk, right?

If it doesn't work, I think you could make it work by hacking the toLinks code, but I'm not sure.

This might work as an alternative (in that same Tpl chunk). Put this where you want the caption to appear:




Then create this snippet.





As a last resort, you could do it with lexicon strings, like this (mn. is just a prefix to avoid collisions):



This uses the name as a lexicon key for the caption.

To do it this way, you'd have to:

1. Create the mynamespace namespace.
2. Go to Lexicons on the System Menu (gear icon) in the Manager.
3. Select the mynamespace namespace, the default topic, and the language.
3. Click on the Create Entry button.
4. Put mn.name (where name is the name of the TV) in the name field.
5. Put the caption in the value field.
6. Save
7. Repeat for each name => caption pair.

Try it with one or two first to make sure it's working.

Well, the first two suggestions didn't work for me. By the way, here's the default 'Specs Link' Chunk (tpl) mentioned above,

It looks like I will need to try your Lexicon suggestion. Hopefully I'll have better luck.

Thank you.

If you put a [[+name]] placeholder in the 'Specs Link' Chunk (tpl), does it show the TV name?

If so, you might try this with the ShowCaption snippet above:



The exclamation point will delay the processing of the snippet until (hopefully) the name placeholder is populated.

This really should work unless I've made a mistake in the code.

When placed in the 'Specs Link' Chunk the [[+name]] placeholder does not show the TV name.