Advanced search  

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Pages: [1]   Go Down

Author Topic: XHTML validation problem  (Read 3607 times)

0 Members and 1 Guest are viewing this topic.

hell

  • Coppermine newbie
  • Offline Offline
  • Posts: 10
    • Your Hardware Madness
XHTML validation problem
« on: January 18, 2008, 06:35:54 pm »

« Last Edit: January 19, 2008, 01:32:23 pm by Joachim Müller »
Logged

Matt Carlson

  • Coppermine newbie
  • Offline Offline
  • Posts: 10
    • CarlsonPhotos
Re: XHTML validation problem
« Reply #1 on: January 18, 2008, 09:38:06 pm »

Click on the option for "Verbose Output" then validate. It lists out the items it takes issue with for you to correct (Google / search engine of choice is your friend for that.)
Logged

Nibbler

  • Guest
Re: XHTML validation problem
« Reply #2 on: January 18, 2008, 09:53:41 pm »

Most of that is caused by the image scroller mod and you can search the board for BOM for the warning message.
Logged

hell

  • Coppermine newbie
  • Offline Offline
  • Posts: 10
    • Your Hardware Madness
Re: XHTML validation problem
« Reply #3 on: January 18, 2008, 10:28:30 pm »

i referring to:

Byte-Order Mark found in UTF-8 File.

The Unicode Byte-Order Mark (BOM) in UTF-8 encoded files is known to cause problems for some text editors and older browsers. You may want to consider avoiding its use until it is better supported.

Thank you for replay
Logged

Joachim Müller

  • Dev Team member
  • Coppermine addict
  • ****
  • Offline Offline
  • Gender: Male
  • Posts: 47843
  • aka "GauGau"
    • gaugau.de
Re: XHTML validation problem
« Reply #4 on: January 19, 2008, 01:32:02 pm »

Re "BOM":
The weird symbols you encountered are byte order marks from utf-8. They usually come when using an editor like Notepad to edit utf-8 encoded file. Although WIndows doesn't display the BOM, it deliberately adds it to any UTF-8 encoded file. When uploading this file, your webserver/browser display what actually is there.
Recommendation: get the most recent language file from the stable branch and upload it to your server, replacing the one that exists there already. If you need to edit the file before uploading, use an editor that is capable to edit utf-8 files properly without adding the BOM, or remove the BOm manually after editing (but before downloading). This can be done with a tool like "Replace in Files", which is really a very handy tool not only for removing the BOM.
Logged

hell

  • Coppermine newbie
  • Offline Offline
  • Posts: 10
    • Your Hardware Madness
Re: XHTML validation problem
« Reply #5 on: January 19, 2008, 04:56:34 pm »

Solved


the problem was Microsoft Expression Web when copy/paste color code
Logged

Joachim Müller

  • Dev Team member
  • Coppermine addict
  • ****
  • Offline Offline
  • Gender: Male
  • Posts: 47843
  • aka "GauGau"
    • gaugau.de
Re: XHTML validation problem
« Reply #6 on: January 20, 2008, 10:18:29 am »

Thanks for resolving. However, "MS Expression Web" aka "MS Frontpage" is in no way an application fit to be used to handle Coppermine code, as it tends to "beautify" coded that it should not touch. Don't use a crappy WYSIWYG editor to edit coppermine files.
Logged
Pages: [1]   Go Up
 

Page created in 0.019 seconds with 20 queries.