[Portfolio] Form not rendering textarea correctly on one instance of Sakai 2.9
botimer at umich.edu
Thu May 23 05:49:06 PDT 2013
No caching changes that I'm aware of. There are locks on files explicitly referenced as renderers, but if you've verified the changes were applied to the file, they should be effective immediately.
On May 23, 2013, at 8:13 AM, Sean Keesler <sean.keesler at threecanoes.com> wrote:
> Output format is html for formCreate.xslt.
> Puzzling...has any cacheing been added for these files in the last release that would prevent changes from being seen without a restart?
> Sean Keesler
> 326 Stone Quarry Rd
> Ithaca, NY 14850
> sean.keesler at threecanoes.com
> On Thu, May 23, 2013 at 12:42 AM, Noah Botimer <botimer at umich.edu> wrote:
> There is some funny business with HTML via XSLT regarding self-closing tags. I'm certain I encountered this some time ago, but can't recall the exact solution. Double check the output format for the stylesheet vs. the stock formCreate.xslt. The creation renderer will take precedence over formFieldTemplate.xslt for the output settings.
> On May 22, 2013, at 10:27 PM, Sean Keesler <sean.keesler at threecanoes.com> wrote:
>> I am working with one school who has an issue with a pretty normal portfolio form. We developed the schema in 2.8 and tested it on another 2.9 instance (one of the qa server and it renders fine in both instances.
>> However, when imported to this particular 2.9 instance, it breaks.
>> The precise problem is that text fields that should render as text areas render the text area "wrong"...
>> Where our test instances render the text area with an opening and closing text area tag (e.g. <textarea> </textarea>) their instance renders it as a single self-closing tag (e.g. <textarea/>). The result of this is that the rest of the HTML after this <textarea/> tag appears in the text area in the browser. No submit other fields, no submit buttons....
>> It seems that their formFieldCreate.xslt was different than ours...so I asked them to replace their version of the file with ours, which they did...and we can verify that the file IS identical to our version of the file now. However, the form STILL renders wrong.
>> Is there anything needed after replacing the default renderers? Are they cached somewhere? Can anyone think of a reason why the transformer would kick out a single tag instead of two?
>> Sean Keesler
>> 326 Stone Quarry Rd
>> Ithaca, NY 14850
>> sean.keesler at threecanoes.com
>> portfolio mailing list
>> portfolio at collab.sakaiproject.org
>> TO UNSUBSCRIBE: send email to portfolio-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the portfolio