Your page has a form on it as well, you need to remove that. There is
an Action called Multiple Forms which includes a No Form page Action.
You have to apply that to your page, and then the other forms you drew
will work correctly. The reason they do not is because your page looks
like this (to the browser):
form action="" //this is the blank empty form drawn by Freeway
form action="your store url" //this is invalid, you can't nest
forms, so it’s ignored
/form //this actually closes the first form, not the second
form action=“your store url”
/form //closes the second form
form action=“your store url”
/form //closes the third form
/form //this is the closing form tag drawn by Freeway, closes the
fourth form
Each one of these forms is really being sent to the one previous
action, not the one specified in its action parameter, because you
cannot have two “open form” tags in a row, they must open and close in
order or else they are ignored.
Any time you draw any sort of form element on the page, Freeway adds a
form tag to the page, right inside the PageDiv (main content
division). If you set this page-level form (Page / Form Setup) to
point to a controller somewhere, then it will submit the form contents
to that controller. The only way to remove this page-level form is to
add the No Form Action to the page; simply setting it to “nothing”
will not fix this.
Walter
On Jun 2, 2010, at 12:19 PM, Malcolm wrote:
I’ve also checked it out in Firefox and looking at the source code,
the Form tag is there. Something’s really strange if Safari can’t
see it and everything else can. Suffice it to say, the same problem
occurs in FF.
M
On 02/06/2010 15:46, Walter Lee Davis wrote:
Your first button does not have a form tag around it, but the other
two do. Safari’s Web Inspector is your friend here. Whatever extra
step you took on the second two panes to create the Roman Cart form
tag, you need to do the same on the first one.
Walter
On Jun 2, 2010, at 10:37 AM, Malcolm wrote:
It would help if I typed the URL correctly:
I love Carousel and have found all sorts of uses for it,
particularly at the following site development location: www.salarpursuits.co.uk/test_run/watches.html
.
Here’s my problem; everything works fine using the thumbnails on
the right as Carousel tabs, which call up each watch in turn. Each
panel has a graphic-based ‘Add to basket’ button, suitably coded
as a ‘submit’ button and they all link to Roman Cart (no choice
here, client’s wishes). However, the watch tabs labelled PRG40B
and PRG80L both link nicely to Roman Cart, whereas the PRG40
button just takes the visitor back to the Intro panel (Carousel
base pane). What’s going wrong? Clearly there’s a heirarchical
aspect to this scenario. Might I solve the problem with the PRG40
pane by adding a ‘target’ value after the URL in the ….</
form> part of the HTML?
I’ve checked the HTML using TextWrangler and everything seems
fine. The
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options