We’ve just released Freeway 5.5.5! Details are as follows:
We recommend installing the latest version of Showcase (1.0.2) included with Freeway 5.5.5. Showcase now incorporates its own updating mechanism, and updates may be distributed outside of the normal Freeway release cycle.
CRASHES AND ERRORS
• Freeway doesn’t crash after importing an image whose file extension has been incorrectly changed from .jpg to .png
ACTIONS
• German, French and other European number formatting is now supported in the Scriptaculous Actions (Transition FX, Attention FX and Target/Show Hide Layer)
• The FLV Player Action now references files correctly when it’s in a subfolder
• Increased the CSS specificity of the Showcase Action’s image captions
• The Google Maps Marker Action no longer pushes content on a Relative Page Layout out of place
• The Modify Height Action no longer produces a JavaScript error when the item it’s applied to isn’t published
• Fixed a bug that caused Flash videos in the 4:3 aspect ratio to appear squashed
• Auto-hiding image information in the Showcase Action now displays the image number correctly in Thumbnail Galleries
• Fixed a layout problem in the Showcase Action when using the “Spacing and Columns” option in “Layout”
• Fixed a bug that caused some images with the Link to New Window Action applied to disappear
• The Target Show/Hide Layer Action now supports multiple fade durations on the same page
• The Amazon Affiliates Actions now include the Italian store
OTHER
• Multiple changes in the Alt Text dialog are saved correctly.
there’s a german update? where can i get this 5.5.5 (i’ve asked application systems heidelberg for update, but they didn’t answer - latest update on their site is 5.5.2)
Please note, we’ve found an issue with 5.5.5 that needs to be rectified. We’ve removed the version from our site and will be releasing an update as soon as possible. The problem is specifically related to the Create Email Action; if you’ve already updated to 5.5.5 and use that Action please download 5.5.4 until the new version is available: http://www.softpress.com/downloads/updates/
We apologise for any inconvenience.
Joe
On 13 Apr 2011, at 17:56, Thomas Kimmich wrote:
… follow Joe’s link, that’s what I usually do.
I recognized that ASH is still on 5.5.2 although I’m on 5.5.4 (or it’s just the text that isn’t updated yet?).
Should I publish this release on our Small German List?
Sometimes I feel just so in sync with this forum, someone answers the very question I have even as I’m stumbling around looking for the answer. Rarely unhappily, though perhaps this is why 4 hours last night produced confusing results with creating an html email.
Looking forward to the fix.
Frank
PS Anyone see my post regarding mobile phone root level codes?
Just a simple looks good or don’t do it would be appreciated. Thanks in advance and in retrospect!
On Apr 14, 2011, at 5:41 AM, Joe Billings wrote:
Freewaytalkers,
Please note, we’ve found an issue with 5.5.5 that needs to be rectified. We’ve removed the version from our site and will be releasing an update as soon as possible. The problem is specifically related to the Create Email Action; if you’ve already updated to 5.5.5 and use that Action please download 5.5.4 until the new version is available: http://www.softpress.com/downloads/updates/
We apologise for any inconvenience.
Joe
On 13 Apr 2011, at 17:56, Thomas Kimmich wrote:
… follow Joe’s link, that’s what I usually do.
I recognized that ASH is still on 5.5.2 although I’m on 5.5.4 (or it’s just the text that isn’t updated yet?).
Should I publish this release on our Small German List?
I have an issue in 555 with a Rollover not triggering a Target show/hide layer correctly in a 554 created doc. Reapplied the actions and now is showing the following Error
Target show/hide layer: theHead has no properties with the following underlined
var theJS = theHead.fwAddJavaScript();
And now my doc is showing a ton of JS errors on Target show/hide layers.
I have an issue in 555 with a Rollover not triggering a Target show/hide layer correctly in a 554 created doc. Reapplied the actions and now is showing the following Error
Target show/hide layer: theHead has no properties with the following underlined
var theJS = theHead.fwAddJavaScript();
And now my doc is showing a ton of JS errors on Target show/hide layers.
Currently having the same issue re: show/hide layer. Was anything ever determined to be the cause? Was working fine, then all of a sudden I started getting the JS error, not having touched the affected pages. It’s the kind of thing that saving and restarting Freeway seems to clear, but not this time. Any thoughts would be appreciated.
It turned out my conflict was with the “PHP make page insert” action, which I resolved by removing the show/hide action from the page. Of course, now I’m having a problem with the PHP action itself, but just on two out of five identical pages. I do have 5.6.1, so I guess I’m as up to date as can be. If need be, I’ll rebuild the pages from scratch. That often helps.
BTW, have you ever applied a CSS menu action and had only the left half of the trigger area respond to the cursor?
No, it’s not that. The link’s below, but here’s the scoop. Three identical links, and one of the three works fine, the other two only activate on the left half. In Safari and Firefox, that is. In Opera they all work fine. I’ve had this happen before, and I think I just have to rebuild the links from scratch. It’s like when I at one point made them wider, it’s still stuck on the original width. The other thing I can do is duplicate the one that’s working, then edit the content. That works, too. It’s just that gremlin wrangling is so time consuming with this program.
My real problem is the PHP Make Page Insert action has spontaneously started failing. I get a getBody has no properties error in the line if {getBody[“onLoad”]} Don’t know what that’s about, because it was working fine for a few days.
Also, why would two pages always publish, even if they’ve not been modified? Even if nothing’s been modified, for that matter.
That CSS is used for centring the menu items. I think the main part of the problem is that you’re using a separate Action for each item of your navigation menu. That’s not really how the Action is intended to be used. For best (and expected) results, use one Action for your menu (applied to one item) and use an indented list to make up the content for the menu.
you’re using a separate Action for each item of your navigation menu
I should have spotted that
When you look at the menu in Safaris developers tools it looks like there is a seperate element that lies across half of each of the adjacent menu headers - that is what mislead me - obviously a by product of using more than 1 action.