Has anyone noticed apostrophes causing strange characters like this
to be generated in Long Text items?
’t use “cannedâ€
I’m also noticing that the WY actions seem to be causing FW to
republish the entire site every time. Anyone else seen this happen?
Todd
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
These characters are happening because of a mis-match between the Web page and the database about character encodings. Try specifying another character set for the page that hosts the WY form. See if you can find one that works with your database. Also look at the page where you are displaying the final text (to the public) and see if changing character encoding on that page makes a difference.
I haven’t tried WY at all, so I don’t know how much of this is under your control on that end. But you can change the character set of the pages in Freeway, and hopefully you can find something that works.
Walter
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Thanks Walter. After my original post it dawned on me that it was
probably an encoding issue so I double-checked FW and the WY config
file and found the discrepancy. FW 4.4.2 was set to UTF-8 encoding
and I had set the WY file accordingly but it seems that FW won’t
publish (for me at least) as UTF-8 because after numerous forced
publishes the source still showed ISO-8859-1, hence the problem. So
instead of fighting it I changed WY to ISO and it seems to have
worked. This isn’t the first time I’ve had problems setting FW 4 to
UTF-8 but I’m glad that FW 5 seems fine with it, too bad I’m not
using it on this site.
Todd
On Jul 24, 2008, at 6:33 PM, waltd wrote:
These characters are happening because of a mis-match between the
Web page and the database about character encodings. Try specifying
another character set for the page that hosts the WY form. See if
you can find one that works with your database. Also look at the
page where you are displaying the final text (to the public) and
see if changing character encoding on that page makes a difference.I haven’t tried WY at all, so I don’t know how much of this is
under your control on that end. But you can change the character
set of the pages in Freeway, and hopefully you can find something
that works.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
HI Tod I have noticed this too
and I find it normally comes from copy and pasting text from another programme … word being the worst of them all.
if I do get an unusual character, then I have normally deleted it an then typed it in again… it usually works for me.
max
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
The short text action has a permanent Dirty action applied to it. It’s not great cos as you noted anything with short text publishes again even if it hasn’t changed.
This was due to styling issues and how you can use short as inlines and still have them styled differently. In then end to guarantee that these elements styled correctly I dumped in a dirty command which worked.
Max
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
On 25 Jul 2008, 12:38 am, Todd wrote:
Thanks Walter. After my original post it dawned on me that it was
probably an encoding issue so I double-checked FW and the WY config
file and found the discrepancy. FW 4.4.2 was set to UTF-8 encoding
and I had set the WY file accordingly but it seems that FW won’t
publish (for me at least) as UTF-8 because after numerous forced
publishes the source still showed ISO-8859-1, hence the problem. So
instead of fighting it I changed WY to ISO and it seems to have
worked. This isn’t the first time I’ve had problems setting FW 4 to
UTF-8 but I’m glad that FW 5 seems fine with it, too bad I’m not
using it on this site.Todd
I’ve had the problem in 4 with Automatic coming out as ISO (when it should default to UTF-8) but never had a problem with 4 publishing ISO when I explicitly told it to use UTF-8. Can you check to be sure that it’s not on Automatic?
Walter
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
I have a question… Say I publish a website for a client using the webyep action which will allow them to fill in areas of text etc. If I then want to change a design feature or alter the look of the website and I upload the site again from freeway will the clients text have disappeared …?
Thanks,
Fergus
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
HI Fergus as long as the webyep items are still called the same then all the client content will still be there
in fact you can change the whole look with new positioning new css even new extra webyep items… just about everything can change it should still be ok the only thing that tends to muck it up is changing the site structure though even that can if your careful be changed.
max
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
one thing I would add though
I would personally download the complete site and work locally on my mac using MAMP, so I can be doubly sure all is well before I swop swop old for new.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Okay thanks for all the help! Much appreciated .
Fergus
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Originally FW was explicitly set to utf-8, not Automatic, and still it published as iso. When I gave up on utf I switched it to Automatic and it published as iso, same as before when using utf. Very irritating.
Todd
On Jul 25, 2008, at 9:33 AM, waltd wrote:
I’ve had the problem in 4 with Automatic coming out as ISO (when it should default to UTF-8) but never had a problem with 4 publishing ISO when I explicitly told it to use UTF-8. Can you check to be sure that it’s not on Automatic?
Thanks for explaining that Max. I wasn’t sure if it was something
that I was causing.
Thanks,
Todd
On Jul 25, 2008, at 1:29 AM, max wrote:
The short text action has a permanent Dirty action applied to it.
It’s not great cos as you noted anything with short text publishes
again even if it hasn’t changed.
This was due to styling issues and how you can use short as inlines
and still have them styled differently. In then end to guarantee
that these elements styled correctly I dumped in a dirty command
which worked.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options