If you build a box model web site in FW5, but build it by clicking on the Freeway page to insert the first box/page container. Then the usual way of build forms for pages does not work.
Add URLs to Page > Form set up fails the publish the
<form action="URL" method=post>
Also the PHP Feedback from action fails to work also. In this page building senario.
You have to manually build the forms to enable them to work.
***This is when you click on the FW5 page to build your page.
Good find, thanks webworker. To fix the problem just add a form item
(such as a text field to the pasteboard above your page).
To clarify, if you enter your form items inline using a box model
layout the form tag that is usually automatically created by Freeway
isn’t created. To force it to be created draw a textfield above the
page in your pasteboard.
Joe
On 2 Jan 2009, at 15:51, WebWorker wrote:
If you build a box model web site in FW5, but build it by clicking
on the Freeway page to insert the first box/page container. Then
the usual way of build forms for pages does not work.
Add URLs to Page > Form set up fails the publish the
Also the PHP Feedback from action fails to work also. In this page
building senario.
You have to manually build the forms to enable them to work.
***This is when you click on the FW5 page to build your page.
If it’s off screen and NOT layered, then it won’t be published into
the code. If it is layered, then it will be part of the code, and
while it won’t be visible, it will be accessible through the tab key.
Walter
On Jan 2, 2009, at 11:24 AM, WebWorker wrote:
Excellent - through I has a load of from coding to do.
Grrr. I didn’t test that assertion before I answered. Okay, leave it
layered, but choose Item / Extended from the main menu. In the INPUT
tab of that dialog, add a new attribute:
name
value
disabled
disabled
And in the div style tab, add another attribute:
name
value
display
none
These properties will guarantee that this field cannot be tabbed to
and will never appear on screen. If you have to go through all this on
several pages, simply copy the finished input to the clipboard and
paste it onto all of the other pages where you have forms. All of
these extended attributes will come along for the ride, as will the X/
Y coordinates (off-page).
Yes, but this was the degree of fooling around we wanted to avoid with
the Action. The Form Setup stuff is all there, but Freeway won’t do
anything with it unless prodded into action. I have another idea how
we could shim it, but I haven’t had time to try it yet.
Walter
On Jan 2, 2009, at 5:17 PM, Keith Martin wrote:
Sometime around 2/1/09 (at 12:23 -0500) Walter Lee Davis said:
If you have to go through all this on several pages, simply copy
the finished input to the clipboard and paste it
How about using Page > HTML Markup and putting:
in the ‘after body’ section and:
in the ‘before /body’ part? Would this mimic Freeway’s page-level
form tag setup?
Sometime around 2/1/09 (at 20:53 -0500) Walter Lee Davis said:
Yes, but this was the degree of fooling around we wanted to avoid
Heh. It’ll be good in the end, I’m sure, but right now (looking at
the “Item / Extended” tip) it seems like we’re at a kind of parity in
the fooling around stakes!
True, true. But that’s one dialog, on one object which can then be
copied and pasted to every page that has a form. There’s pain, and
then there’s the Page / HTML Markup dialog. (But don’t get me started
on the Styles / New Style / Extended / New stack-o-dialogs.)
Walter
On Jan 3, 2009, at 9:40 AM, Keith Martin wrote:
Sometime around 2/1/09 (at 20:53 -0500) Walter Lee Davis said:
Yes, but this was the degree of fooling around we wanted to avoid
Heh. It’ll be good in the end, I’m sure, but right now (looking at
the “Item / Extended” tip) it seems like we’re at a kind of parity
in the fooling around stakes!