WordPress.org
Get WordPress

Make WordPress Core

Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#35854 closed defect (bug) (invalid)

XML Parsing Error

Reported by: ingstra's profile ingstra Owned by:
Milestone: Priority: normal
Severity: normal Version: 4.4.2
Component: General Keywords:
Focuses: Cc:

Description

I don't remember which version it started at, but after this one upgrade, when trying to run upgrade.php, I got the error message

XML Parsing Error: undefined entity Location: ​https://www.ftek.se/main/wp-admin/

<title>WordPress &rsaquo; Uppdatera</title>"

I also get errors for &lsaquo.

For some reason the error disappeared when I removed the "xmlns" in <html xmlns="​http://www.w3.org/1999/xhtml"> in the source code. But now when trying to upgrade to 4.4.2 this little trick does not work anymore. When trying to go to the admin-page I get this XML parsing error, so I cannot access the admin-page.

My friend who is more well versed with these kinds of issues says that our server is configured correctly, and the fault is with Wordpress. I asked for help on the forum and did not get anything useful, I appreciate if you could help me with this.

Change History (8)

#1 @ingstra
9 years ago

  • Severity changed from normal to major

I just noticed another error also:

XML Parsing Error: not well-formed Location: ​https://www.ftek.se/main/wp-admin/update-core.php Line Number 52, Column 82:

!function(a,b,c){function d(a){var c=b.createElement("canvas"),d=c.getContext&&c.getContext("2d");return d&&d.fillText?(d.textBaseline="top",d.font="600 32px Arial","flag"===a?(d.fillText(String.fromCharCode(55356,56812,55356,56807),0,0),c.toDataURL().length>3e3):(d.fillText(String.fromCharCode(55357,56835),0,0),0!==d.getImageData(16,16,1,1).data[0])):!1}function e(a){var c=b.createElement("script");c.src=a,c.type="text/javascript",b.getElementsByTagName("head")[0].appendChild(c)}var f,g;c.supports={simple:d("simple"),flag:d("flag")},c.DOMReady=!1,c.readyCallback=function(){c.DOMReady=!0},c.supports.simple&&c.supports.flag
(g=function(){c.readyCallback()},b.addEventListener?(b.addEventListener("DOMContentLoaded",g,!1),a.addEventListener("load",g,!1)):(a.attachEvent("onload",g),b.attachEvent("onreadystatechange",function(){"complete"===b.readyState&&c.readyCallback()})),f=c.source{},f.concatemoji?e(f.concatemoji):f.wpemoji&&f.twemoji&&(e(f.twemoji),e(f.wpemoji)))}(window,document,window._wpemojiSettings);

#2 @ocean90
9 years ago

  • Component changed from Charset to General
  • Keywords reporter-feedback added
  • Severity changed from major to normal

Hello @ingstra, welcome to Trac!

Can you please provide some info about your server and your browser? It seems like something is serving the pages as XML rather than HTML.

#3 @ingstra
9 years ago

Thank you, and what a quick reply!

What do you need to know? Here is some information I can think of: The server is running Debian Wheezy, kernel 3.2.0-4-amd64, Apache/2.2.29, PHP 5.6.6. My current browser is Firefox 38.5.0. I tried Chrome on my cellphone as well, where I currently get the error "error on line 10 at column 27: Entity 'lsaquo' not defined"

#4 @dd32
9 years ago

This feels like the html_type option is potentially set to xhtml, common in the days where XHTML looked like the future of the web.

@ingstra Can you let us know what the value of html_type at ​https://www.ftek.se/main/wp-admin/options.php is?
Unless you're doing something special and particular, that should be set to text/html.

That option should probably be removed realistically.

#5 @ingstra
9 years ago

I'm not sure I looked at the right place, as I couldn't find the 'html_type' option at ​https://www.ftek.se/main/wp-admin/options.php. But I looked directly in the database:

mysql> select * from wp_options where option_name='html_type';
+-----------+-------------+--------------+----------+
| option_id | option_name | option_value | autoload |
+-----------+-------------+--------------+----------+
|        49 | html_type   | text/html    | yes      |
+-----------+-------------+--------------+----------+

#6 @ingstra
9 years ago

Hello.

Is there any progress on this matter? A friend who is more well versed in these areas than I am suggests the use of numerical entities instead.

Last edited 9 years ago by ingstra (previous) (diff)

#7 @ingstra
9 years ago

  • Resolution set to wontfix
  • Status changed from new to closed

Finally, after over a year of having trouble with this, I found that the problem disappeared when I set html_type to applicationxhtml+xml.

#8 @DrewAPicture
9 years ago

  • Keywords reporter-feedback removed
  • Milestone Awaiting Review deleted
  • Resolution changed from wontfix to invalid
Note: See TracTickets for help on using tickets.