Testing and using standard fields so the values show up

[Tony Chung]

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

[shanson]

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 

--
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-c...@googlegroups.com.
To unsubscribe from this group, send email to reddot-cms-use...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.

[Tony Chung]

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

[shanson]

That will be nice, check first if you see both stf values in Preview mode. I got it what you are looking for. Let me know if it still doesn't publish.

 

Thanks,

Shankar

[Tony Chung]

Hi Shankar,

I added both stf to the content body and only the one set up by the
implementers displays in preview. The new one I created does not.

I even tried bypassing the preprocess routines by wrapping the code as
an output. But I guess if there isn't a value in the stf then it
wouldn't work anyway.

<p>stf_thatWorks: <%stf_thatWorks%></p>

<p>stf_doesntWork: <%stf_doesntWork%></p>

<h2>Attempt to bypass preprocessing</h2>
<p>stf_doesntWork: <%= "<" & "%" & """ & <%stf_doesntWork%> & """ & "%" & ">" %>

Thanks,

-Tony

[shanson]

Hi Tony,

 

In your code below where does the stf which does not work is not showing in the second line or in your bypassing process?

<p>stf_thatWorks: <%stf_thatWorks%></p>

< p>stf_doesntWork: <%stf_doesntWork%></p>

< h2>Attempt to bypass preprocessing</h2>
< p>stf_doesntWork: <%= "<" & "%" & """ & <%stf_doesntWork%> & """ & "%" & ">" %>

I am not clear you said that you dont have any value in stf? Check if there is content via edit form for the stf whcih is not working. Also check the stf which is working has any default value set to your URL.

 

Thanks,

Shankar

[Tony Chung]

Hi Shankar,

The field that doesn't work doesn't work in all instances (pre process and bypass pre process)

As far as I can see both fields are set up identically.

Both fields are set up as references to existing fields in the same location at the root of the project.

There is no default value in either field.

-Tony

On Friday, September 21, 2012, shanson wrote:

Hi Tony,

 

[Jian Huang]

Please clear project page cache and try again.

Sent from my iPhone

[Tony Chung]

Hi Jian,

You know our environment well. I cleared the page cache but nothing changed.

What I failed to realize was that OT doesn't automatically update standard field references in existing page instances. Had I created a new page instance, the referenced standard field would have appeared. You wrote us a plugin to retroactively apply reference values to existing elements, and that worked fine.

Thanks so much!

-Tony