Anyone have any ideas why the text entitled, “Form intro text goes here.” is not picking up my p tag. Also, why is my radio button text so small and so close to the buttons?
Because the text is not wrapped in a p tag (look at the source). You need to target the radio buttons with some CSS if you want something other than default positioning.
That text seems like a placeholder that comes with the default template, I’m not sure it needs to be there. Can you post the Perch template that’s being used to generate the text?
Ok, I copied your template code as-is and used it in my Perch install and the intro text is wrapped in a p tag with no tweaking from me so my guess is the Action your using is why the tag is being stripped which is why your text is not picking up your paragraph styling.
There’s one way to find out, disable any actions you’re using on that particular section. Since it works fine for me obviously it’s something you’re using that I’m not and since I’m not using FW then an Action is a good place to start looking.
I thought this was the idea behind the crowbar action!
Just add the code in a Markup item and see if that does what you want.
HTH
On May 7, 2013, at 11:2 PM, Todd wrote:
Ok, I copied your template code as-is and used it in my Perch install and the intro text is wrapped in a p tag with no tweaking from me so my guess is the Action your using is why the tag is being stripped which is why your text is not picking up your paragraph styling.
Click on the Crowbar and open up its editor. Copy the code out of it, and then close the editor and delete the Action. From the main menu, choose Insert / Markup Item in place of the Crowbar (i.e.: at a flashing text cursor). Paste in your code and okay the dialog. Markup Items always produce a parent P tag, which is why I wrote the Crowbar (to get rid of that if your template isn’t producing something valid to fit inside a P).
Because Crowbar removes surrounding tags, and sometimes you need that. For example, this would be invalid:
<p><div>Something</div></p>
Your code (in PHP) might create that DIV. An inline Markup item will always be surrounded by a P (or another block-level tag, like an LI, depending on the surrounding structure). If your code already generates a tag, then wrapping that tag in another might either be a nuisance or actually invalid HTML.
Using Crowbar allows you to either slip your code outside of the surrounding tag, at the beginning or end of the line, or to replace the surrounding tag entirely.
Walter
On May 7, 2013, at 5:38 PM, RavenManiac wrote:
Mike, that worked perfectly. Thank you.
One question though. If Markup does the same thing as Crowbar, why do I need Crowbar?
Markup items do not do the same as the Crowbar action, that is why you where having problems.
If you insert the Crowbar action the surrounding P tag will not be output, this is the advantage of using the Crowbar action.
Shame this was not just a checkbox option in the FW Markup item window.
On May 7, 2013, at 11:38 PM, RavenManiac wrote:
Mike, that worked perfectly. Thank you.
One question though. If Markup does the same thing as Crowbar, why do I need Crowbar?
I just tried this in FW6, and there was no issue adding a P tag inside a Crowbar. The Action picks up any surrounding tag and replaces it entirely when the Action is all alone inline in a block-level text container. If you place it at the beginning of a line of text or at the end, it moves your code outside of the surrounding tag, either before or after the tags depending on the position within the line.