Hi Debs
You can apply a webyep action to a freeway item even with text in it, as you have done it, but on publish the webyep action will swop the contents with webyep code ready for population.
The easy thing to do is unlock the page, then copy the text from freeway document and paste it into the webyep popup. from that point on webyep will be populating the contents of that item.
All proper cms systems have to have control of the content otherwise if your client adds some text and then you make an adjustment to the freeway artwork and publish the result would be you wipe out the client amendments, hence why webyep elements are populated via a browser. You done everything correct as I can see but if you have a problem please email me directly and I can respond to your query quicker
ps sorry for the poor grammar but I was rushing about trying to type and make lunch for the family
with the result that I didn’t check what I had written
:o)
cheers max
That’s why I prefer a non-wysiwyg editor like Coda, no extra code is generated and it ends up being much cleaner.
I know you are only defending your product here, but this statement is meaningless for most of those who use Freeway to avoid having to know, or do not have the time to learn how to create websites using code only. Freeway requires zero knowledge of HTML to produce a reasonable site. That does create challenges when confronted with trying to incoporate a product such as yours within the confines of Freeway, but as Walt pointed out there is a way around it.
That does create challenges when confronted with trying to incoporate a product such as yours within the confines of Freeway, but as Walt pointed out there is a way around it.
I think what MarkF was getting at was that the problem is not with Pulse but with Freeway and other wysiwyg programs for adding potentially non validating components in certain circumstances. Yes there is an easy workaround in this instance but only through the action (sic) of a third party.
There’s one possible problem awaiting you if your Pulse content is more than one line of text. If you use the Markup Item, and the resulting code from Pulse generates a block-level wrapper like
or
around its content, you will invalidate your page. (It will probably look fine in most browsers, but it will fail W3C validation, and having an invalid page can contribute to nearly-impossible-to- debug problems in other areas, especially if you use JavaScript effects elsewhere on the same page.)
I have taken note of this and used Crowbar to insert a Pulse block into an HTML item. It worked fine, clean code as predicted by Walter but the body text, (not H1 H2 etc) come out tiny and I mean really tiny. However if I put a space into the html item before the crow bar action all is as it should be, and valid. Is this right?
Without Crowbar I get the look as wanted but as Walt says - duff validation
The 1px thing is a feature, not a bug. Any empty cell/div (and Freeway
doesn’t consider the inclusion of an Action-item to be text content)
gets this style so that any images placed all by themselves in the
cell snug up nice and tight to their container. Otherwise, you would
have some spacing around the images that would throw off the rest of
your layout.
I would not consider a page-level Action to be much use, because the
result would be chaos, layout-wise.
Walter
On Jul 12, 2011, at 8:00 PM, DeltaDave wrote:
Why stick to the Crowbar action - why not a page action?
But seriously - what is the logic behind the 1px style thing and is
it likely that we will see its demise in 5.6?