Thanks Shankar,
One of the stf values set up by our implementer appears in the web page
HTML but the new stf I set up prints empty.
I'll set up a test to display the content of both stf in preview mode
tomorrow.
Essentially I am trying to get the URL of the HOST_NAME server value. Our
server is set up weirdly where only a few Request.ServerVariables are
available, and HOST_NAME is set to "localhost". So I have to resort to
using the field we set up te published URL instead.
-Tony
On Thursday, September 20, 2012, shanson wrote:
> Hi Tony,
>
> Its not clear what you mean by gets publish to the DS pages, do you mean
> that you see this on web pages or to one of the page attribute on DS
> server? If it is page attribute then can you check if your current standard
> field is set within the import dynaments inside your templates, If it is
> not as a attribute then can you check if the content appears if you publish
> this on IIS server. Do you see this standard field content in Preview mode?
>
> Thanks,
> Shankar Sonawane
>
> On Thu, Sep 20, 2012 at 6:43 PM, Tony Chung
> <to...@tonychung.ca<javascript:_e({}, 'cvml', 'to...@tonychung.ca');>
> > wrote:
>
>> Hi all,
>>
>> I'm modifying several templates and experienced an odd problem with
>> standard fields. These standard fields are presently set in the project
>> root, and are used to set the server parameters once. Standard fields are
>> used our templates as references to the root elements.
>>
>> One standard field was set up by our implementer, and it works fine to
>> publish the text value to the delivery server pages.
>>
>> I created a new standard field based on the settings of the working
>> standard field and referenced the new element value. This standard field
>> does not output to the delivery server pages.
>>
>> Both Standard fields are of type Standard Field, and the Text option is
>> selected.
>>
>> What do I need to know to get standard fields working?
>>
>> Thanks,
>> -Tony
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "RedDot CMS Users" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/reddot-cms-users/-/_poCW1bXDIsJ.
>> To post to this group, send email to
>> reddot-cms-users@googlegroups.com<javascript:_e({}, 'cvml',
>> 'reddot-cms-users@googlegroups.com');>
>> .
>> To unsubscribe from this group, send email to
>> reddot-cms-users+unsubscr...@googlegroups.com <javascript:_e({}, 'cvml',
>> 'reddot-cms-users%2bunsubscr...@googlegroups.com');>.
>> For more options, visit this group at
>> http://groups.google.com/group/reddot-cms-users?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "RedDot CMS Users" group.
> To post to this group, send email to
> reddot-cms-users@googlegroups.com<javascript:_e({}, 'cvml',
> 'reddot-cms-users@googlegroups.com');>
> .
> To unsubscribe from this group, send email to
> reddot-cms-users+unsubscr...@googlegroups.com <javascript:_e({}, 'cvml',
> 'reddot-cms-users%2bunsubscr...@googlegroups.com');>.
> For more options, visit this group at
> http://groups.google.com/group/reddot-cms-users?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"RedDot CMS Users" group.
To post to this group, send email to reddot-cms-users@googlegroups.com.
To unsubscribe from this group, send email to
reddot-cms-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/reddot-cms-users?hl=en.
