BEWARE opening up older Freeway pro doc with 6 - none of mine open without big fails - particular the CSS menu - thats totally broke in all 3 docs I dared to open.
When upgrading it warns of Actions that need updating - the first on the list is WeYeb. The link supplied does not link to an update option. Where is this??? I need this!!
The Chirp Action (which I need) link download does not work despite the fact it says it should. I need this to work!!!
Come on - its great news but headachy too
No wonder it produces a back up doc that save an older version PHEW.
I’m delighted to see the new features and keen to upgrade and implement new areas for myself and clients and I’ve watched all the linked videos from Joe Billings’ email, but I’ve seen a few comments like this so maybe will hold on for a few days to get these bugs ironed out first.
Elizabeth
On 01/02/2013, at 9:44 AM, Justin Easthall wrote:
K - firstly great! At last something new.
BUT
BEWARE opening up older Freeway pro doc with 6 - none of mine open without big fails - particular the CSS menu - thats totally broke in all 3 docs I dared to open.
When upgrading it warns of Actions that need updating - the first on the list is WeYeb. The link supplied does not link to an update option. Where is this??? I need this!!
The Chirp Action (which I need) link download does not work despite the fact it says it should. I need this to work!!!
Come on - its great news but headachy too
No wonder it produces a back up doc that save an older version PHEW.
Had a few issues with css menus and transiton fx behaving oddly in chrome. Will revisit in the morning, but on my quick initial look-see, i can’t see a major reason to rush the upgrade. I’ll stick to 5.5 for ongoing sites and will start new sites in 6.
Can anyone tell me though, with all the new fluid layout settings, does this do away with box model building?
Hi everyone
The web-yep problem is down to me and nothing to do with FW6
unfortunately I was all geared up ready to launch at the same time and then my wife discovered I had missed something blooming imperative which I had completely forgotten to check and sort out…
the problem arrises with webyep loops which is a fairly fundamental part of webyep so please could everyone give me just a little time I have got the bare bones of the problem working so it now just a matter of wiring it in but I need to test it thoroughly before the launch of webyep 3.3… and it is quite massive upgrade to
I bought upgrade but I can not open with new documents nor any of my websites. error message alert. I have alerted softpress,
so nothing to look at today I suppose… more patience
Great wor Softpress. But got always an error message when saving. Message pops up in quirky german. Try to translate it: Could not save the file not found would not (filename) not save. (043:114:11398)
