I think it’s very painful to discover that pages made with FW do not pass the validation service.
Why is there not a build in feature in FW to check the locally published paged before we upload them?
Now it’s trial and error on line.
In this feature the folks from FW might also build in some understandable tips to “repair” the code.
Just a thought.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
On 18 Nov 2007, at 10:29, atelier wrote:
I think it’s very painful to discover that pages made with FW do
not pass the validation service.
When you say pages fail, what are the validation reports saying?
Freeway makes W3C compliant HTML and CSS code. Some of the validation
services are very fussy, and will pick up on things which in the real
world don’t really matter that much.
Some Actions also will add snippets of JavaScript to the code which
may cause a validation service to choke.
Cheers
Heather
“Freeway - Web Design for All”
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
How fast…
Like here:
http://www.vlindernaam.nl/index.php/vn/verhaal/mijn_oma/
I get these errors using http://validator.w3.org/:
Line 68, Column 26: end tag for element “SPAN” which is not open.
Line 68, Column 30: end tag for element “A” which is not open.
I must say that these pages are build with EE and FW. So it’s not right out of the box… (and my knowledge of these things is less than zero)
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Sometime around 18/11/07 (at 05:48 -0500) atelier said:
Line 68, Column 26: end tag for element “SPAN” which is not open.
Line 68, Column 30: end tag for element “A” which is not open.I must say that these pages are build with EE and FW. So it’s not
right out of the box…
In that case I would lay money that the problem is to do with the way
the Freeway code has been integrated with ExpressionEngine. Freeway
4’s output should validate well for the HTML output level you select.
I can’t imagine a situation in Freeway itself that would produce the
problems you’ve reported - but when you start to tinker with any
kind of code you have to accept that you may be mucking things up.
Sorry! But I think you’ll have to do one of two things; either
Learn more about code so you can figure out what’s gone wrong and where, or
Relax and accept that the problems here that have been produced by
the way Freeway and ExpressionEngine have been mixed are not at all
serious.
k
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Good advise. Thanks. I’m glad these "problems’ are not serious.
I’ve got the feeling that this particular problem has to do with the way EE outputs the content of the entrees in the weblogs. I can choose settings like:
Maybe “none” is best here? I’ll check it out and come back here.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
After some experiments and advise most of the validation problems did disappear with the following settings for the output of weblog fields in EE: auto
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options