is it right that webyep elements do not work on scripty fader options? i tried out, but i deleted the example. maybe someone has a final answer.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
You can use certain webyep items with scripty effects but you haven’t described what you re trying to achieve or which webyep / scripty elements you are combining and how you have constructed it, and without that I cant really tell if what you want is achievable… if you could show us a link with your example?
all the best max
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Hello Max,
I made a small example with one fader and three options which have different web yep-content.
The link to the page is:
The link to the file on DropBox:
https://www.dropbox.com/s/a09ws190ifbz4o4/Scripty_fader_example.freeway
I can see no web yep-content in the fader options…
yours, tom
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
aaaaahhhh I remember this scripty action
ok this is what the scripty action is doing
When you add a webyep item and its part of the scripty fader effect action then the effect action strips out the webyep php script. (Hence why there is no webyep items).
If you were to look at the code you will see that all the webyep script has been removed on the extra html pages that this scripty fader action creates.
So I added the webyep scripts via html mark up and this time the scripty fader effect action doesn’t remove the the webyep code, but unfortunately it still doesn’t work.
I think the scripty effects action is creating html pages and then inserting the generated html pages into your designated area, and it’s probably a combination of the pages being pulled in being html pages, and not php plus the pages being pulled in via javascript that is mucking it all up.
So in this scenario now the scripty fader effect action and the webyep actions are not compatible
sorry about that
max
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
This is precisely the case. When ScriptyFader processes a page, it takes the element you have applied it to and removes it completely from the page, saving it as a “fragment”. This fragment is always saved with the .html extension. (note to self, I should look at the extension of the parent page and use that instead – might be a root cause of some other issues) If there was anything outside of that element (in the page head) that was required in order to populate that fragment of HTML with its actual content, then the two would be separated. Now if your fragment was written such that it was self-contained – that it had the gear within it to request data from WebYep, then it would work just fine, exactly the way that any stand-alone page could be loaded into the browser with dynamic content in place.
Walter
On Jan 12, 2013, at 4:13 AM, max wrote:
So I added the webyep scripts via html mark up and this time the scripty fader effect action doesn’t remove the the webyep code, but unfortunately it still doesn’t work.
I think the scripty effects action is creating html pages and then inserting the generated html pages into your designated area, and it’s probably a combination of the pages being pulled in being html pages, and not php plus the pages being pulled in via javascript that is mucking it all up.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options