• Archived  

By seGAP - April 1, 2007

Hi,

We want to try a variation of the method described in the following two posts that describe how to hide or show a particular field in the Article Editor depending on the value of...

(1) Current User (http://www.interactivetools.com/iforum/Products_C2/Article_Manager_2_F31/gforum.cgi?post=50484)

or

(2) Category
(http://www.interactivetools.com/iforum/Products_C2/Article_Manager_2_F31/gforum.cgi?post=53004)


...our variation being that we want the value to be tested to be one of our Custom Article fields. Can this be done.

We did try using a Placeholder of $article.customfieldname$, but just got an "Unknown Placeholder" error.

Any ideas?

Thanks
seGAP

Re: [seGAP] using placeholder for a Custom field in the _defaultEditFields Admin template

  • Archived  

By ross - April 1, 2007

Hi there

Thanks for posting!

I am not quite sure which part of the first thread you were looking at, but Theo post here:


http://www.interactivetools.com/forum/gforum.cgi?post=50470#50470


goes over the code you need to put in your custom HTML field to get the field to only appear for certain user levels.

Was that what you had tried? I am pretty sure this is what you'll need to use so give this one a shot and let me know how you make out [:)].
-----------------------------------------------------------
Cheers,
Ross Fairbairn - Consulting
consulting@interactivetools.com

Hire me! Save time by getting our experts to help with your project.
Template changes, advanced features, full integration, whatever you
need. Whether you need one hour or fifty, get it done fast with
Priority Consulting: http://www.interactivetools.com/consulting/

Re: [ross] using placeholder for a Custom field in the _defaultEditFields Admin template

  • Archived  

By seGAP - April 1, 2007

Thanks Ross,

Yes, it was Theo's solution that I read, but where his field is displayed conditional on User Levels, we want it conditional on the value of a Custom Field.

Theo has...

<!-- templateIf : $currentUser.accessLevel$ >= "4" -->

We want something like...

<!-- templateIf : $article.customfield$ eq "hardcoded-value" -->

We can handle the rest of the coding, but we don't know what placeholder to use for the customfield, as $article.customfield$ isn't working for us.

PS. We know you don't support templates changed in this way, its just the help with the actual placeholder name that we're asking for.

Thanks
seGAP

Re: [seGAP] using placeholder for a Custom field in the _defaultEditFields Admin template

  • Archived  

By ross - April 2, 2007

Hi there.


Thanks for clearing that up!

Could you try using just $customPlaceholder$ without the "article." part at the beginning?

Give that a shot and let me know how you make out [:)].
-----------------------------------------------------------
Cheers,
Ross Fairbairn - Consulting
consulting@interactivetools.com

Hire me! Save time by getting our experts to help with your project.
Template changes, advanced features, full integration, whatever you
need. Whether you need one hour or fifty, get it done fast with
Priority Consulting: http://www.interactivetools.com/consulting/

Re: [ross] using placeholder for a Custom field in the _defaultEditFields Admin template

  • Archived  

By seGAP - April 2, 2007

Thanks Ross,

so simple!

For the record, what is the rule for Placeholder naming?

Is it always...

$article.field$ for System fields
$field$ for Custom fields

Thanks
seGAP

Re: [seGAP] using placeholder for a Custom field in the _defaultEditFields Admin template

  • Archived  

By ross - April 3, 2007

Hi

I think that any field that is actually available to the article edit template interface is done with just $field$

The $article.field$ only comes into play when you are working on the publish templates.

Keep me up to date with how you are making out [:)].
-----------------------------------------------------------
Cheers,
Ross Fairbairn - Consulting
consulting@interactivetools.com

Hire me! Save time by getting our experts to help with your project.
Template changes, advanced features, full integration, whatever you
need. Whether you need one hour or fifty, get it done fast with
Priority Consulting: http://www.interactivetools.com/consulting/