These are related. When you place a page inside another page, all of the styles need to be present in the parent page in order to have them work in the sub-page element that your script inserts into that parent page. Usually, all you need to do to make this combination of effects work is to put the site into External Style Sheets mode. However, Actions such as FormElementStyler (all Actions, really) do not get the styles they create pushed to the master CSS stylesheet by Freeway. Any styles that the Action adds remain stubbornly in the page itself. Where they get stripped off.
Here’s a couple of things to try.
First, try the very latest PHP Make Insert Page Action on your form page. There’s an option in the latest version to “Preserve HEAD Content”. Check that on, and see if your form looks and works correctly. This may not work, owing to the order of Actions as they affect the output code. But it’s the easiest thing to try, so do it first.
If that doesn’t work, then you may need to try something more exotic. Copy your entire form into the pasteboard area of your parent page. You may need to adjust the pasteboard size in the preferences or document setup – not sure were that lives – to give yourself room to work. This means that you’ll need to set up the form in your parent page, or if there’s already a form there, use the Multiple Form Suite to set up multiple forms on the page. Make sure that your form is all contained in a single element. The easiest way to do this is to group all of its elements, but that can make editing later more difficult. The correct way to do this is to draw an HTML box over the entire form, then use the Site panel in Page view to re-nest the form elements so they are all “children” of your HTML box.
Once you have the form in place and properly nested into a single element, apply the TemplateHelper Action to it. Check the “Make Partial” checkbox, which will open up a whole load of options. Check “Move Form Into Partial” and “Remove Positioning”. Enter a meaningful name for your partial. Finally, publish the page, then go back to your trigger element (the thing that opens up the lightbox) and change the link.
To do this, use whichever method you chose initially (Graphic Link to File Action or the regular Hyperlink dialog) and click on the Browse button in the External side of the Hyperlink picker. Navigate in the resulting File dialog until you find the partial. It will be named ‘_WhateverNameYouGaveIt.html’ (underscore leading, the name you entered, then the extension you chose) and will be in the same folder inside your Site folder as the parent page. (Because it starts with an underscore, it will sort to the top of the list of files.)
Publish again, and test. Because the entire form is contained within the parent page at the moment of publishing, all of its styles and JavaScript will naturally be in the parent page as well, and won’t be removed by any of these Actions. When TemplateHelper runs, it will take all of the HTML that comprises your form unit and write it into a separate file, and then remove all of those elements from your published parent page. This is hard to wrap your head around the first time, but it’s actually the most elegant way to solve this problem, technically speaking.
Walter
On Nov 22, 2010, at 5:19 AM, atelier wrote:
Hi
I have a form on a page which shows up in a SLB window. Works well, except two things.
- The ‘extra field’ for the spamtrap shows, which is not good.
- I use FormElementStyler for my formfields. But the formatting is not picked up in the SLB window.
Any clue how to fix these?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
