Viewing EverWeb 1.3.1 Final Candidate 1

EverWeb 1.3.1 Final Candidate 1



User: Paul-RAGESW 6 years ago
EverWeb 1.3.1 Final Candidate is now available. This version focuses on fixing important issues from version 1.3. This is not yet an official release and is posted here for testing purposes. Please let us know if you have any issues with it;

EverWeb 1.3 Final Candidate 1

CHANGES;
[FIX] You can now select a text object and just start typing to replace the current text. You don't have to double click a text object anymore to edit the text
[FIX] Paypal widget now accepts prices with decimals
[FIX] Deleting projects in Projects Window with Delete key works again
[FIX] Fixed possible crash when right clicking within projects window
[FIX] Double clicking the site name in the web page list to rename it won't collapse it
[FIX] Dialogs have proper title on title bar instead of Document #
[FIX] Contact form now properly sends emails again after sending the first email
[FIX] Paypal widget item id can use letters now
[FIX] Widgets now check to make sure they are compatible with the version of EverWeb they are used in
[FIX] Support for light, heavy, Condensed, etc... fonts
[FIX] Fixed an issue with using 404 Page Not Found and 301 redirects causing Internal Server errors
[FIX] 301 redirects now work even without publishing your entire site

-------------------------------
Paul
EverWeb Developer

Macworld.com ranks EverWeb as the top choice for Mac users wanting to build a website!
User: Paul-RAGESW 6 years ago
A new Final Candidate version of 1.3.1 is now available.

This version fixes some issues with Undo and changes the way text is exported. It provides better support for fonts and styles as well as Google Fonts.

Please let us know if your fonts or styles don't export properly

EverWeb 1.3.1 Final Candidate 2

Last edit 6 years ago

-------------------------------
Paul
EverWeb Developer

Macworld.com ranks EverWeb as the top choice for Mac users wanting to build a website!
User: Jonas B. 6 years ago
Paul,

Sorry, still problems.

I don't think it's the export itself.

Exporting an untuched projectfile built in an older version than the sharp 1.3 build out the googlefonts as it should do.

If making any changes to this projectfile like changing fontsize, this will kill the googlefont at that place. Untuched boxes still work in the same export.

Opening this changed projectfile in the last beta before the sharp 1.3, exporting it as is (modificated in anything after the sharp one) will ALSO export it with broken googlefonts in the modificated boxes. Exacly the same as the latest one now.

Ok, readjust the fontbox in the old beta, export directly from that one will now correct the googlefont and it's not broken anymore. Back on scratch again like an untuched.

Anything that get tuched/adjusted by anything later than the last beta before the sharp 1.3 screwes up googlefonts in the 'projectfile'.
User: Jonas B. 6 years ago
doublepost

Last edit 6 years ago
User: Paul-RAGESW 6 years ago
Hi Jonas,

I'm really sorry but I don't quite understand your comment.

Can you show me your website exported with this version of EverWeb?

What do you mean by "sharp 1.3 build"?

Can you please clarify what the problem is that you are having?

-------------------------------
Paul
EverWeb Developer

Macworld.com ranks EverWeb as the top choice for Mac users wanting to build a website!
User: Jonas B. 6 years ago
Ok, I'm baking to much into the sentences :) I Know.

I'm making a difference between betaversions and the official 1.3 (sharp release in my own language). You're naming the betas like "candidates", right?

Using any Everweb version released 'after' the official 1.3 in order to export/publish from a projectfile that was built with an Everweb version released 'before' the official 1.3, will do fine if nothing is changed in the projectfile regarding textboxes/fonts. Just publish as it opens. The googlefonts works when published.

However, if making changes in a textbox like stepping up/down in fontsize…. then shit will happen. Meaning that one will get a websafe font like Times on the published page instead of the google font which was ment to be there. This happens if making the changes using any version released after the official 1.3.

Ok?

If I open that changed project once again in an older version of Everweb (a version released 'before' the official 1.3), then publish with the changes that were done in a later version than the official 1.3 release…. then it will publish the same problem -- no googlefont will work, the local websafe substute font will sit there in the box. Any box that has not been changed will publish the google fonts correctly. Side by side.

If I change fontsize back again, using the old version released before the official 1.3, then publish from there google font will work again. This doesn't happen if doing so in a later version.

What I am trying to say is that a 'newer' version than the official 1.3 will put some problem into the 'projectfile itself'. Becouse the older version also gets googlefont-problems trying to export such a project.

Bottomlines: The problem with googlefonts not working on the published page doesn't seem to happen 'during" the publish/export" procedure. Instead it follow the projectfile and creates the same problem using older versions which did not have that problem from the beginning.

My problem now using your latest version is that the latest release still have problem with googlefonts. I get a local websafe substitute instead the googlefont when on a computer that doesn't have the googlefont installed locally.

This messy information was to tell you that if you're chasing the cause in the exportprocedure, it's probably the wrong place to look for it.

If we're talking about different problems, well, than you got a new bug report from this…. kind of longwinded one ;)

Keep up the good work. I have to move on here.
User: Willem L. 6 years ago
Hello Paul or colleague, I'm very happy with Everweb, only ... publishing takes ages. I don't see ant difference between "publish entire site" and "publish site changes". How to speed up this. My site is simple: mijnreisinfo.nl

regards,
Willem
User: Paul-RAGESW 6 years ago
We've published a new Final Candidate version.

This version fixes publishing problems where all pages are being published instead of just the changes. It also fixes issues with password protecting directories for add-on domain or for directories within directories. Lastly it fixes problems where some widgets would not preview properly (the would appear fully transparent with no content).

EverWeb 1.3.1 Final Candidate 3

-------------------------------
Paul
EverWeb Developer

Macworld.com ranks EverWeb as the top choice for Mac users wanting to build a website!
User: Paul-RAGESW 6 years ago
A new Final Candidate version is available and it fixes font styling issues when the first style in a paragraph is set to italic or bold. It also fixes a few other styling/formatting issues;

EverWeb 1.3.1 Final Candidate 4

Please note there is currently a bug with the line height feature which can make line spacing larger than what you see in EverWeb in your browser if it is set to anything larger than 1. We are working on this issue.

-------------------------------
Paul
EverWeb Developer

Macworld.com ranks EverWeb as the top choice for Mac users wanting to build a website!
User: Yelena 6 years ago
Works great! Thank you!

-------------------------------
Yelena
MacBook Pro OS X 10.10.3
IMac 21" OS X 10.10.3
User: Jonas B. 6 years ago
Paul,

just wanted you to know:

I've done a quick test using the latest candidate4 – those problem I pointed out earlier here about making changes in projectfiles (project originally created with anything before the 1.3.1 official on) using latest candidates, now seem to be completely gone. I've just done a few tests on the go, but so far this is a VERY nice progress. Even Explorer (il bastardo) behaves well ;)

I did not test candidate 3, since I was a bit fed up (….) with the fontbugs that never seemed to reach an end. Movements of locked textboxes like some other people here had problem with, also occured at my place too. It all simply took way to much time from me. I really love the software and your concept, but the bugs drove me almost nuts here. It's been pretty fundamental functions that have been problems with like fonts. Earlier I did a lot of attempts to be able to use @fontface and did follow all the information about linking abs/rel and the guidance into every corner. No Go. It didn't matter what I tried. I then accepted to go googlefonts even though the fonts I wanted didn't have any google substitute fonts. When google fonts screwed up now, there wasn't anything else than the websafe fonts to reach for. That can't be accepted today. So, I'm very happy to see that you seem to be back on the right track now. Also, my projectfile went down a lot in size after been working on it in this candidate4. A bit quicker preview and exporting as well, could be imagination, but it feels like it's faster.

I understand that you're working extremely hard with a bunch of different bugs. Greateful for that. I'm sure you're quite exhausted. I don't think it's a matter of normal workingdays/hours for you guys….. Hope that things will slow down and give you some well earned rest soon.

All the luck in the near future! And…. thanks. ;)

Last edit 6 years ago
User: Paul-RAGESW 6 years ago
@Yelena and @Jonas: Glad to hear everything is working better.

In regards to the Font problem in this version, what happened was what I thought was a quick fix turned out to introduce a much larger problem. It took some investigation but it all seems to be fixed now. The functionality is much better and we even fixed bugs from earlier versions and made more fonts available.

Fonts on the web are kind of complex. Google Fonts is right now your best bet but we will be introducing new features to make font management much easier.

-------------------------------
Paul
EverWeb Developer

Macworld.com ranks EverWeb as the top choice for Mac users wanting to build a website!
User: Yelena 6 years ago
Paul,

I am happy with fonts now but just FYI... If I choose to use the first letter of the paragraph as Bold and the rest Regular the problem appears again...( Not important for me but wanted you to know)

-------------------------------
Yelena
MacBook Pro OS X 10.10.3
IMac 21" OS X 10.10.3
User: Paul-RAGESW 6 years ago
A new final Candidate version is available. It fixes issues with widget previews within EverWeb and other minor issues;

EverWeb 1.3.1 Final Candidate 5

-------------------------------
Paul
EverWeb Developer

Macworld.com ranks EverWeb as the top choice for Mac users wanting to build a website!
User: Lars 6 years ago
Publishing Problems:

Using the Final Candidate 5

I open Everweb. Turn the Publish-Mode to FTP. Publish my whole site. The whole site is uploaded. And now when change something and hit "publish changes" it works. I save the project. Quit Everweb and reopen it. The Publish setting is back to folder. ( Why? ) I change it back to FTP. Now I change a small sentence and hit "publish changes" and EverWeb turns all pages to red and publishes to whole site again... :-(

-------------------------------
Impossible you say? Everything is possible when you work for the circus.


Post Reply
You must login or signup to post.