For a £100 I would expect something that is not glitched. Or at least saves my work!
First, after making 3 pages with individual resizing of all the pictures, (iPhone, iPhone landscape, iPad and Default) and when I start making the 4th page, ALL, absolutely all my previously resized pictures got black. I have re-build my site from beginning 3 times, thinking I do something wrong. Jesus, It drives me mad. Today I updated to the 7.0.1 but the problem remains, all the pictures are black.
Every 3-4 pics modifications I get a message as I cannot save the work, for some “error” number bla-bla. That means I have to save the site in progress after EVERY alteration!!! Incredible.
There is absolutely no way to get a correct pre-view in the Freeway or in the “preview” mode, I have to physically upload the site to take a look at the pictures. All the pictures are distorted, none corresponds to the size/scale that will be rendered in the browser. And the distortion is huge. I work with 1200-650 pics and the image frame shows about 20% of a real image. I have to upload every single time I modify some pic. Ridiculous.
For some reasons the CSS layout moves and I get (for example) 30pix white margin above all webpages in the browser. Master looks perfect, and I have modified only the text on one page. Absolutely disappointed.
Now, after spending days on my site (9 pages only), I have to:
save the site after EVERY MODIFICATION. If not, Freeway will may show some error and refuse to save the work.
I have to duplicate the site every half hour, just in case. I may make some minor modifications on a text and end up with all CSS layout moved in a unexpected way.
This is to say, I’m really disappointed with the Freeway 7. The idea of responsive sites is great, and the result is fine, when it works properly. But SOOO many glitches. Drives me nuts.
If you do upload a Freeway document don’t forget to remove the upload
details from the Upload dialog. We’re nice people and wouldn’t muck
about with your site, but it’s always good to be safe, eh?
This is very true. I recently had to ditch my MacBook Pro’s HD; it had
developed severe speed problems and occasional read/write glitches. (I
have everything backed up so it wasn’t a disaster.)
Make a backup.
Got one already? Make sure it’s current.
Check the volume using Disk Utility and/or Disk Warrior.
If there are significant problems you should seriously consider
replacing the drive rather than trying to patch it up.
my 2 cents…
I have learned that importing graphic image via pass-through, then you don’t have to adjust the breakpoints…
I have been successful with 7 and no glitches whatsoever, all is saved and preview is no problem
except my user error, but whats new…
still more to learn, but overall I love it
C
Thanks guys for trying to help me, but it drives me nut, this versions, really.
First, I will upload my website to a dropbox, thanks for help. Will send you PM.
The error message appears only when modifying the pics, especially with responsive layout. Nothing if I write text. I have re-build the site 6 times (really upset me…) but still the same issue.
I have a MacBook Pro 5 weeks old, I did not check the drive, but I think nothing wrong with partition. Will check just in case, as you suggest.
It happens already three time, I suddenly have a white band above the top of all pages. I mean all the pages suddenly have about 20-30px margin from the top of the browser. Absolutely surprising, I was editing some minor text stuff in the middle of one of the pages
If you can help me at least remove that white stuff, I will be really glad, folks.
Found the thing that makes the pages having white band above: my google analytics code. That’s it. Following the Google advice, this code should be placed before /head markup. Or anywhere within head. If place it there, a white band appears.
So, I placed it before /body tag.
There was no problems with Freeway 6, I don’t know how effective will be the tracking codes (analytics/demographic/re-marketing) if placed before /body tag.
PS. The images are still black, I have rebuild the site entirely using the updated version Freeway 7.0.1.
… it would be outermost interesting to have a chance seeing this project live. Could you do us a favor by sharing a link. Naturally Freeway is guilty, I know - but I suppose some user mistakes (>0.01%).
Fairly word of warning:
Assumed I detect a user mistake(s), be sure I write some lines how I define “disappointment”.
… it would be outermost interesting to have a chance seeing this project live. Could you do us a favor by sharing a link. Naturally Freeway is guilty, I know - but I suppose some user mistakes (>0.01%).
Fairly word of warning:
Assumed I detect a user mistake(s), be sure I write some lines how I define “disappointment”.
Cheers
Thomas
Why such a sarcasm and (almost) personal comments? I have used Freeway from version 4 and if I say “disappointed”, there are some websites I have built already with previous versions. Freeway was always very good for me and compared to previous experience (8 years of use? 10? don’t know, I used it on my PowerMac…), I find Freeway 7 much more unstable and less intuitive than previous versions.
For example, I don’t see why design the pass-through function using the “import” and absolutely through HTML frame? Why could not a user just copy-past to an image frame? Not really user friendly. The new version crashed a couple of times within one month, problems saving the work, black images etc. I understand there will be bug fixes, and I find the support is very friendly, really appreciate it.
So, if I say “disappointed”, I mean disappointed compared to previous 3 versions I have used, nothing more.
Following the Google advice, this code should be placed before /head markup.
Are you not using the Google Analytics action? That would avoid misplacement.
David
Thanks David for advice, I could try this, but it would solve half problem.
I have used Google analytics for while on previous versions of Freeway, and always was using in through Google Action. Google recommends to place it before /head and I tried it, it worked perfectly, I receive all datas daily.
I advertise on Google and I have a couple more tracking codes into my HTML before /head, always worked perfectly. There is a Google webmaster code, Google adwords code plus a re-marketing campaign code, so, I ended up with 3 Google codes in my page (previous version of website, on Freeway 6).
But thanks for advice, I will try the action for general code and will try the re-marketing/ad-words codes within the body and will check the stats results in a couple of weeks, it may be irrelevant where the code is, don’t know. Cheers
Sorry, I missed this thread and sorry to hear you’re disappointed.
We’d definitely like to see your file to try and diagnose the black images problem – it’s not something we’ve seen before.
Can you send the Dropbox link to support(a)softpress.com too please?
Joe
On 27 Sep 2014, at 22:36, Akira email@hidden wrote:
On 27 Sep 2014, 8:45 pm, DeltaDave wrote:
Following the Google advice, this code should be placed before /head markup.
Are you not using the Google Analytics action? That would avoid misplacement.
David
Thanks David for advice, I could try this, but it would solve half problem.
I have used Google analytics for while on previous versions of Freeway, and always was using in through Google Action. Google recommends to place it before /head and I tried it, it worked perfectly, I receive all datas daily.
I advertise on Google and I have a couple more tracking codes into my HTML before /head, always worked perfectly. There is a Google webmaster code, Google adwords code plus a re-marketing campaign code, so, I ended up with 3 Google codes in my page (previous version of website, on Freeway 6).
But thanks for advice, I will try the action for general code and will try the re-marketing/ad-words codes within the body and will check the stats results in a couple of weeks, it may be irrelevant where the code is, don’t know. Cheers
Note that Safari has a Zoom Text Only option in its View menu, as does Firefox (View>Zoom>Zoom Text Only) so you can’t write this need off as old fashioned quite yet.
If you are pulling data from a database, then your HTML text areas will need to grow/shrink with that content. So RPL helps to ensure that items change sizes as expected. However, responsive features do not work well in this situation, and the only solution is to use inline features.
Not good unless you are starting from scratch. Freeway’s inline way of working is not helpful if you want DTP like freedom to move content around at your, and your client’s whim.
On 8 Sep 2014, 3:15 pm, thatkeith wrote:
“it prevents the page from falling apart if a visitor uses text zoom within the browser” – This used to be very important, but does any modern browser now do anything other than zoom the whole page? (There are many other reasons to do inline layouts despite the relative quirkiness of production, but I think this one’s gone… isn’t it?)
Would you be able to send your file (or a cut down version of the file) to support(a)softpress.com so we can see if it’s the same as the problem that Thomas is having (and can be fixed in the same way)?
