It’s working perfectly here. Did you change anything? BTW, the
filename of the page is case-sensitive. So your URL only works if you
correct the Showroom to showroom.
Walter
On May 14, 2008, at 9:04 PM, kitesurfer3 wrote:
Hi all,
Safari 3 (Mac or PC) not showing “Pic to Lightbox Image” properly.
Do you see a small map picture with a X to close on right bottom, and does it “Pulsate”?
I didn’t change anything and in my Mac all I see is the map in a page and no FX.
Thanks for your help Walter
Emilio
It’s working perfectly here. Did you change anything?
If you’re using Weaver Mootools suite then I believe there is an incompatibility at the moment with freeway 5.
I don’t actually have this suite of actions but understand that if you remove the button pulsate effect then Pic to lightbox will work in correctly firefox.
Pete
You are loading Prototype.js and scriptaculous.js twice. Once, by the
effects part of the Show Hide Target Action, and again for Lightbox.
You can simply leave the second one out, and only load the
lightbox.js script. It will have everything it needs already, because
both libraries are included all the way at the top of the page.
I don’t have any Show Hide Target Action on page “showroom”, why is that code there and how can I choose the code that FW5 inserts in the page, I am lost (newbie).
Thanks for all your help
Emilio
You are loading Prototype.js and scriptaculous.js twice. Once, by the
effects part of the Show Hide Target Action, and again for Lightbox.
You can simply leave the second one out, and only load the
lightbox.js script. It will have everything it needs already, because
both libraries are included all the way at the top of the page.
There’s your culprit. If you want to use Pic to Lightbox, you will
have to drop using this Action. One or the other, but not both,
unless Weaver updates his Action to work with the framework that Joe
Billings and I worked out a few months ago to only load these
libraries once.
Walter,
that’s what I said a few messages up, anyway when you comment it’s a good idea to listen!
Walter, just want to say that you are doing a darn good job!! helping people.
FreewayTalk or Freeway would not be the same without you! Don’t know how you get the time to fit it in?
Keep up the good work buddy.
Pete
Take a look at line 78 of the published code. See how that comment
happens in the same line as the close script tag? I am guessing that
your problem starts there. From JavaScript’s perspective, it’s as
though that entire line is missing.
Is that code you entered by hand, or is it something that the
lightbox action added?
Try (manually) adding a line break after the comment, so that line
(78) is just this:
//]]>
Then upload the edited file and see if it works.
If this was something that was written by the Action, then contact
the developer and see if there’s a newer version that doesn’t do this.
Walter
On May 15, 2008, at 11:39 AM, James Wilkinson wrote:
Walter:
What would account for the lightbox not working on this page:
I am aware of a couple of problems with the Proto version of the Lightbox Action, and am working towards a resolution.
As a quick note: there exists TWO versions of the this Action.
A - One utilizes mootools and is integral part of the Mootools Suite, named ‘moo: Slimbox’ (Slimbox = mootools)
B - The other is a stand-alone version (actually the predecessor to the mootools version) that uses prototype and Scriptaculous, named ‘Pic to Lightbox’ (lightbox = prototype)
I have a fix that should post to my Actions site shortly. Since there have been a couple threads like this so far, I will make an announcement here when the update happens. Expect a couple added options as well with the updated Action, like opacity and BG colors.
In short, the things I know about and have fixed so far:
duplication of prototype/scripty libraries - I will be relying on Walter’s or FW’s Actions to do the heavy lifting of adding the libraries to the page. No sense having a third player in this area.
Slightly outdated Lightbox library - This is not so much of a ‘problem’ but just a pet peeve of mine.
I will take a look at the CDATA comment issue noted above. Although, If that is a problem, I believe that might better lie in SP’s hands to fix, as any script would be vulnerable to this.
Expect an update in the next week or so. If you are antsy, contact me directly and get the pre-release.