"" is added to any php files I edit - is anyone else seeing thi (Jay) - 6/16/2007 1:03 AM PST
-
jeudi 6 mars 2008 15:33ModérateurBy: Jay
Expression Web is adding "" at the beginning of any/all php files I edit with it. This is causing problems with session_start(); since those characters are interpreted as html thus starting the session. Is this a know problem? Is anyone else seeing this?
Toutes les réponses
-
mercredi 25 juin 2008 13:33
I'm getting this too! Have you ever had a solution to this?
Thanks...- Proposé comme réponse Eddster mercredi 25 juin 2008 13:41
- Marqué comme réponse Lori DirksMicrosoft Employee, Moderator dimanche 23 novembre 2008 01:22
-
mercredi 25 juin 2008 13:42
- Proposé comme réponse Eddster mercredi 25 juin 2008 13:42
- Marqué comme réponse Lori DirksMicrosoft Employee, Moderator dimanche 23 novembre 2008 01:22
-
mercredi 25 juin 2008 13:45
This is the 'Byte Order Mark' or BOM.
To remove from a page in EW V2 right click the page and select encoding and then uncheck the 'Include a byte order mark (BOM' checkbox.
To set the editor option for EW itself, go to Tools - Page Editor Options - Authoring' and uncheck the BOM options in the list of file extensions.
For EW V1 see http://by-expression.com/content/bom.aspx
HTH
Ian
http://www.ew-resource.co.uk
http://www.fp-resource.co.uk
Ian Haynes- Proposé comme réponse fcphdJim mardi 21 juin 2011 18:01
-
mercredi 25 juin 2008 13:54
It appear when you use the charset utf-8 in your content-type meta
You have to use the iso-8859-1
replace this :<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
by this :<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-
mercredi 9 juillet 2008 05:00I am still having trouble with the  string showing up. I didn't have the trouble until I edited some of my PHP files with Expressions WEB 1.0 so then I read this thread and spent the $100 to upgrade to 2.0. I've done all of the stuff that has been recomended on this thread and I've opened all my PHP files, made a trivial changes and saved them again. Most of the  stuff has gone away but on one stuborn page I'm still getting it. I've been chasing this bug for days now and my hair has all been pulled out and is laying on the floor. I guess I need to search my files with a hex editor.
The trouble comes from a PHP RSS reader script and  only shows up if the file it is supposed to read is valid. Otherwise the error message is garbage free. So maybe the RSS feed has it embedded. Trouble is it is screwing up a Javascript document.write() call that will not digest the . Do you suppose the author of the RSS feed was using Expressions WEB? But then, why was it working a month ago?- Modifié t22harris mercredi 9 juillet 2008 05:02 typo
-
mercredi 9 juillet 2008 08:26What's the URL of the feed? BOMs are not exclusive to xWeb, and since RSS is XML, it is perfectly valid to contain a BOM. Your PHP script is broken if it can't deal with this.
-
lundi 12 octobre 2009 08:38do this:
Stage 1:
<!-- Meta setup -->
<!-- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> -->
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
Stage 2:
<?php
// WRONG:
echo utf8_encode("Geïnspireerd News ....");
// WRONG:
echo htmlentities("Geïnspireerd News ....");
// CORRECT: simple text as it is
echo ("Geïnspireerd News ....");
?>
Reg
ShaMun
Belgium, Leuven. -
mardi 3 novembre 2009 22:24Use Vim 7.2 (gVim Diff is a part of the installation) Right click on gVim Diff (properties) and change "C:\Program Files\Vim\vim72\gvim.exe" -d into "C:\Program Files\Vim\vim72\gvim.exe" -b.
Open your html/php site and you'll probably see those strange signs. Delete it, save and voila... -
mardi 3 novembre 2009 23:17ShaMunBd: Do you realize that this thread had been dead for a year and a half!!!??? And the question had long ago been answered. There is NO reason to dig this up after all this time.
However, now that it has been dug up, before we put it to rest, I should point out that Axel Peter's answer was wrong. There's nothing wrong with UTF-8, in fact, it's preferred. Just to clarify, if someone searches for this information.
Ian has the correct answer...
This is the 'Byte Order Mark' or BOM.
To remove from a page in EW V2 right click the page and select encoding and then uncheck the 'Include a byte order mark (BOM' checkbox.
To set the editor option for EW itself, go to Tools - Page Editor Options - Authoring' and uncheck the BOM options in the list of file extensions.
And, Fred...This forum is about editing in EW, not some oddball text editor that few people use.
Now, let's let this thing die. The OP got his answer a year and a half ago. There is no point in adding to this. -
lundi 5 avril 2010 21:14
Is this an issue with web expression 3
-
lundi 5 avril 2010 21:20
Notice the date and the version number in the origianl post?
This is a three year old thread on a 2 version back program. No, it isn't an issue anymore and hasn't been since v2.
MS MVP Expression Tutorials & Help http://by-expression.com -
mardi 7 juin 2011 15:03
You are incorrect. I'm running version 4 and it IS still a problem... found this thread and it fixed my problem... but damn Microsoft always has to throw a problem into something. Normally I use Dreamweaver and NEVER have this problem....
But YES it STILL IS a problem!!!
And I don't care how old this thread it, it still serves a purpose and helps others. -
dimanche 19 juin 2011 21:59Is still an issue, I'm running V4
-
lundi 20 juin 2011 01:29No it isn't unless you are opening a page with the BOM aleady on it since EW 4 won't remove it from existing pages. It will not put a BOM on new pages if you tell it not to.
Free Expression Web Tutorials
For an Expression Web forum with without the posting issues try expressionwebforum.com -
mardi 21 juin 2011 11:24
I'm getting this too! Have you ever had a solution to this?
Thanks..Reg
annat jain
Aloe vera import export -
mardi 21 juin 2011 16:27
Good lord! Do you people have a brain cell between you, or have you simply joined the bloody "Me, too!" chorus without bothering to read the entire thread? This was a problem in earlier versions. It is not a problem in EW4. EW4 no longer adds a BOM to new documents unless that document type is checked in Page Editor Options|Authoring, where it says explicitly, "Add a byte order mark (&BOM) when creating or renaming UTF-8 documents with these file extensions."
EW4 has no way to know your intention, so it will not clear a BOM which already exists when it saves a document. You have to do that. But, if you clear the checkboxes in PEO|Authoring, it will not create a BOM against your wishes when creating a new page.Moderators, could we please get this thread locked?
Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later. -
mardi 21 juin 2011 18:00
I'm getting this too! Have you ever had a solution to this?
Yep, Ian answered it three years ago, although for some inexplicable reason Lori marked other responses as the answer. Then, nearly two years ago Bill repeated it, with bold for emphasis. The only thing is, since the thread is so old and applies to EW2, the method of removing the BOM from existing pages is a little different in EW4. In EW4, right-click in the page, select Page Properties, go to the Language tab, and uncheck the box at the bottom.
The part about Tools>Page Editor Options... remains unchanged since 2008 when Ian answered it. I don't see it as some elusive issue that defies solution.
Jim

