I have not tested either Action in the presence of RPL. I cannot begin to guess what might be happening, as that Action does some serious heavy lifting. You don’t mention if your second issue has anything to do with RPL, so I need clarification on that point.
In general, Actions also do not operate in a strict order, there seems to be some “black box” behavior to do with the order that Actions are added to objects, page vs. item Actions, the filename of the Action, where it was installed… all this beyond the normal parts of Action interaction which the developer CAN control – namely which callback they invoke their magic from within.
TagWrap does one simple thing. It places a user-specified string of text before and after the element it is applied to. It does not (and I can certainly understand any confusion, given the name) wrap an element with a full-blown tag as Freeway understands that term. It also does not do anything that might signal to Freeway that the bit of text should be considered part of the element it wraps, such that they would be moved together rather than separately.
RPL takes apart the entire page, re-assigns hierarchy, creates new tags (real tags – that’s the important part here) to wrap the parts of the page you have drawn in Freeway, and otherwise does so many things at once that it’s a serious miracle unto itself. I cannot imagine that TagWrap would survive this process at all, since it is injecting plain text into the output stream.
Your solution is just kicking the problem down the processing stream a bit. Any other Action that was looking for the wrapper code during the output process will miss it, because that code won’t be there yet. I can certainly make this change, but it may have unintended consequences.
Crowbar assumes (when you are applying it in an inline context) that the Action is either the first or the last or the only “character” on a line of text. It looks up one level to its surrounding container element, renders that element to HTML, counts characters, and then moves itself outside of the either the first or last character of that rendered HTML (or, in the case of being the only thing on the line, removes the entire container tag). If you can post an example, made like this: one DIV with the Action not used at all, and an inline image box where the Action would be, and one DIV that is an exact duplicate of the first, but with the addition of the Action (replacing the inline image), I may be able to help further. I need to see where you started, and what you’re expecting to happen, before I can begin to diagnose this.
Walter
On Jul 16, 2013, at 2:21 PM, TeamSDA wrote:
Hello Freeway Actions Builders
We have come across an issue where two actions we have been using are breaking, Tag Wrap and Crowbar. I believe we see where the issue is in regards to the TagWrap action, but thought it better to share our findings so everyone could benefit. As for CrowBar not sure what is going on under the hood of it’s action.
__________TagWrap ______________________________________________
ISSUE: Tag Breaks Away From Item
When an absolute item with the TagWrap Action is on a page using RPL, the form tag that is entered through the action is breaking away from the item and getting randomly placed elsewhere.
POSSIBLE ACTION FIX: By changing line 15 from “fwBeforeEndBody” to “fwAfterEndHTML” in the action we seem to have been able to fix the issue. Hope this is helpful. Look forward to an update on the Forge.
CrowBar (Item & page actions affected only)___
ISSUE: When applying the actions, Item or Page, the code entered in the End setting is out of order in the final output if all its child items are not inline. Can this be fixed or is it a limitation of the action?
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