Kevin Thanks for the explanation. After reading the documentation more carefully I did understand the proper way to change context was using <form:project>. The example you gave is what I was trying, but it doesn't work. I also tried closing with </form:project>. But I don't get anything rendered.
Thank you for the update example, it works perfectly. I was testing with the view: with changing contexts and it was also working perfectly but I didn't think about trying the in place editor, it was in the documentation. I wasn't planning on using the in place editor. If I can't get the form working this may be a similar option. I can probably do it by doing some extra javascript, disabling the ability to click it and then having a separate button to do a submit. Because my functionality needs the ability to pull the submit a value from a video player. thank you for your assistance. I hope this is not a bigger problem with the form tag. I also tried reverting to 1.3 pre25 but it didn't work. Is there a way to enable more detailed debug logging so we can look at what happens when the form tag is trying to be rendered and why it shows up blank? thanks, Ankur On Feb 5, 7:57 pm, kevinpfromnm <[email protected]> wrote: > for is not an attribute for form IIRC. you probably want something simpler > (and maybe even simpler still) > > <form:project update="start_position_seconds"> > <field-list: fields="start_frame" /> > </form> > > You don't need a second context change with the field-list (you're within > the form tag so the changed context is already there). > > <editor:project.start_frame /> is an inplace editor in case that's all you > really need/want. -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/hobousers?hl=en.
