I’m trying to do a simple fix to Webworker’s problem in the main list.
The following doesn’t work, and I don’t understand why not. Can anyone
shed some light on this?
ForceForm
2008 Walter Lee Davis
function fwAfterStartBody(){
this.fwRequiresForm = true;
}
I’ve tried moving this declaration to different parts of the publish
timeline, and nothing seems to do the trick. I’ve also tried alerting
the current value of this property both before and after I set it, and
it doesn’t change.
I think it’s a parameter of the action tag, 1 sec I’ll dig it out of
another Action.
Joe
On 2 Jan 2009, at 18:05, Walter Lee Davis wrote:
I’m trying to do a simple fix to Webworker’s problem in the main
list. The following doesn’t work, and I don’t understand why not.
Can anyone shed some light on this?
ForceForm
2008 Walter Lee Davis
function fwAfterStartBody(){
this.fwRequiresForm = true;
}
I’ve tried moving this declaration to different parts of the publish
timeline, and nothing seems to do the trick. I’ve also tried
alerting the current value of this property both before and after I
set it, and it doesn’t change.
I think it’s a parameter of the action tag, 1 sec I’ll dig it out of
another Action.
Joe
On 2 Jan 2009, at 18:05, Walter Lee Davis wrote:
I’m trying to do a simple fix to Webworker’s problem in the main
list. The following doesn’t work, and I don’t understand why not.
Can anyone shed some light on this?
ForceForm
2008 Walter Lee Davis
function fwAfterStartBody(){
this.fwRequiresForm = true;
}
I’ve tried moving this declaration to different parts of the
publish timeline, and nothing seems to do the trick. I’ve also
tried alerting the current value of this property both before and
after I set it, and it doesn’t change.
I saw that, trouble is I want to do the opposite. I want the action to signal that Freeway should generate a form, regardless of whether or not it believes it needs to. Adding this parameter to the action declaration does not change the outcome.
I tried changing this to requires-form, but while that did get the alert(this.fwRequiresForm) to say true rather than false, that didn’t do anything in the way of actually creating the enclosing form. Any other ideas?
Yeah sorry I just read through the notes, require-form should be
what you’re after but it appears to not work (not in 4 either) unless
I’m doing something wrong. I think what you’ll need to do is use
generates-form (which tells Freeway not to generate a form because
your Action will, and then add your own.
Does the page you apply it to have any form fields drawn anywhere?
What we’re trying to do here is get Freeway to add an enclosing FORM
tag to a page that it does not believe contains any form fields at
all. The underlying issue is that if you make a “box model” page by
double-clicking into the PageDiv, any form elements that are contained
within that element or any of its children will not cause Freeway to
generate a form. If you draw an element off-screen somewhere, then all
is well, but that raises additional issues which are hard to sort
through without lots of tweaky extended elements.
Walter
On Jan 2, 2009, at 1:55 PM, Mike B wrote:
Unless I misunderstand… I use this in an action and it seems to
work for both FW4 and 5!
On Jan 2, 2009, at 7:43 PM, Walter Lee Davis wrote:
Tried that, it didn’t do anything. Joe has confirmed that this
problem extends back to FW4 as well.
Ah… ok, I understand, then yes I find it does not set the form tag
without form fields being drawn.
On Jan 2, 2009, at 8:04 PM, Walter Lee Davis wrote:
Does the page you apply it to have any form fields drawn anywhere?
What we’re trying to do here is get Freeway to add an enclosing FORM
tag to a page that it does not believe contains any form fields at
all. The underlying issue is that if you make a “box model” page by
double-clicking into the PageDiv, any form elements that are
contained within that element or any of its children will not cause
Freeway to generate a form. If you draw an element off-screen
somewhere, then all is well, but that raises additional issues which
are hard to sort through without lots of tweaky extended elements.
Walter
On Jan 2, 2009, at 1:55 PM, Mike B wrote:
Unless I misunderstand… I use this in an action and it seems to
work for both FW4 and 5!
On Jan 2, 2009, at 7:43 PM, Walter Lee Davis wrote:
Tried that, it didn’t do anything. Joe has confirmed that this
problem extends back to FW4 as well.
It seems to ignore any form elements that are inline children of the PageDiv. I tried a couple of different ways, and the only way I could get it to work is if the elements were drawn on the page, rather than inserted inline.