Welcome, Guest
Username Password: Remember me

xmlParseEntityRef
(1 viewing) (1) Guest
  • Page:
  • 1
  • 2

TOPIC: xmlParseEntityRef

xmlParseEntityRef 13 years, 3 months ago #5179

  • Spubs
  • OFFLINE
  • Junior Boarder
  • Posts: 32
  • Karma: 0
We came across this error this morning. It's only on the mobile site, so I'm going to ask the developer as well (maybe it's a known issue), but I wanted to see if you had any knowledge of the function xmlParseEntityRef.

It's a difficult error to re-create. I've attached screenshots. The actual error text is only displayed on Adam's phone; my phone, the Android SDK, and iphones don't show it even though the page does not display properly. The error is "Line 131: xmlParseEntityRef: No Name"

A google search says it's a misplaced ampersand character.

Basically, it's preventing the photos from displaying, and making the actual page very long.

Page: www.theshorthorn.com/index.php/multimedia/photo-galleries/27596-welcome-week-2011

and: www.theshorthorn.com/index.php/multimedia/photo-galleries



Last Edit: 13 years, 3 months ago by Spubs.

Re: xmlParseEntityRef 13 years, 3 months ago #5181

  • Barnabas
  • OFFLINE
  • Moderator
  • Posts: 329
  • Karma: 6
I don't know what the cause of the problem is, but I viewed the site
Page: www.theshorthorn.com/index.php/multimedi...96-welcome-week-2011
using a user agent switcher in firefox.
The iphone was shown as you described but the xhtml/pda had 7 lines the same above the screen
Notice: Undefined offset: 1 in /opt/www/www.theshorthorn.com/plugins/system/jat3/core/libs/Browser.php on line 414
Hope that helps you pin down the cause.

Re: xmlParseEntityRef 13 years, 3 months ago #5183

  • Spubs
  • OFFLINE
  • Junior Boarder
  • Posts: 32
  • Karma: 0
Lines 411 to 421:

protected function checkBrowserBlackBerry() {
if( stripos($this->_agent,'blackberry') !== false ) {
$aresult = explode("/",stristr($this->_agent,"BlackBerry"));
$aversion = explode(' ',$aresult[1]);
$this->setVersion($aversion[0]);
$this->_browser_name = self::BROWSER_BLACKBERRY;
$this->setMobile(true);
return true;
}
return false;
}


I'm not familiar with the xmlParseEntityRef function nor is our server admin, so I was hoping somebody could explain what's broke....
Last Edit: 13 years, 3 months ago by Spubs.

Re: xmlParseEntityRef 13 years, 3 months ago #5184

  • Barnabas
  • OFFLINE
  • Moderator
  • Posts: 329
  • Karma: 6
Hi, The code shown above is from the JAT3 plugin.
I may have caused it to fail... My user agent for the xhtml/pda is the single word Blackberry. This is enough to persuade MJ to show the pda template but it may have given the JAT3 plugin a problem.

I could not find the xmlParseEntityRef in any code.

Back to the original question. The misplaced ampersand could be in text that you are showing to describe a photograph. I have looked through the photos on the web page but have not spotted it yet. Did the photos go up today/recently?
The kind of thing is... "photo of x ampersand y at a rock concert."

Sorry I can't look at this anymore tonight. Hope you find the cause.

Re: xmlParseEntityRef 13 years, 3 months ago #5185

  • Spubs
  • OFFLINE
  • Junior Boarder
  • Posts: 32
  • Karma: 0
It's broken for all photo galleries, so I have a feeling it's related to the image cycler, but hard to say.

Re: xmlParseEntityRef 13 years, 3 months ago #5190

  • dryabov
  • OFFLINE
  • Administrator
  • Denis Ryabov, Lead Developer
  • Posts: 4867
  • Karma: 105
The page source is valid, but there are some external files loaded from addthis.com, disqus.com, quantserve.com, scorecardresearch.com, facebook.net and facebook.com. It may be that one of them leads to such a type of error.

Re: xmlParseEntityRef 13 years, 3 months ago #5202

  • Spubs
  • OFFLINE
  • Junior Boarder
  • Posts: 32
  • Karma: 0
It works on every other page, so I can't see it being the commenting system....

Re: xmlParseEntityRef 13 years, 3 months ago #5204

  • Spubs
  • OFFLINE
  • Junior Boarder
  • Posts: 32
  • Karma: 0
I stand corrected, it is on every page, but only on articles. And the articles display, but the galleries do not.

www.theshorthorn.com/index.php/news/university/27612-new-science-professors-have-big-plans-at-uta

This page contains the following errors:
error on line 160 at column 155: xmlParseEntityRef: no name
Below is a rendering of the page up to the first error.

I found this topic. forum.joomla.org/viewtopic.php?p=2057351

The last entry here is also of note: validator.w3.org/check?uri=http%3A%2F%2Fwww.theshorthorn.com%2Findex.php%2Fnews%2Funiversity%2F27612-new-science-professors-have-big-plans-at-uta&charset=%28detect+automatically%29&doctype=Inline&group=0

Also found this, which would relate to the last entry of the W3C validator. forums.digitalpoint.com/showthread.php?t=1283229
Last Edit: 13 years, 3 months ago by Spubs.

Re: xmlParseEntityRef 13 years, 3 months ago #5205

  • Barnabas
  • OFFLINE
  • Moderator
  • Posts: 329
  • Karma: 6
Hi,
I'm trying to reproduce the error using firefox and user agent switching.
Could you tell me what the user agent is for Adam's phone?
Please ask him to visit www.mobilejoomla.com/uatest.php
and post the string in this thread.
Thanks.

Re: xmlParseEntityRef 13 years, 3 months ago #5206

  • Barnabas
  • OFFLINE
  • Moderator
  • Posts: 329
  • Karma: 6
Hi,
I set the user agent string to
SAMSUNG-GT-E2550/E2550DXXJH3 Profile/MIDP-2.0 Configuration/CLDC-1.1 UP.Browser/6.2.3.3.c.1.101(GUI) MMP/2.0
which is a Samsung E2550 Monte Slide.
I was basically trying user agents to see if I could reproduce the error.
I got a hard failure.
 
XML Parsing Error: not well-formed
Location: http://www.theshorthorn.com/index.php/multimedia/photo-galleries/27596-welcome-week-2011
Line Number 133, Column 14: if (holder && wapper) {
--------------------^

the carat points to the ampersand.
If you run the page through the W3C checker, which you mentioned in another thread, you get a warning.
 
# Warning Line 429, Column 13: character "&" is the first character of a delimiter but occurred as data

if (holder && wapper) {
 

 
This message may appear in several cases:
 
* You tried to include the "<" character in your page: you should escape it as "&lt;"
* You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
* Another possibility is that you forgot to close quotes in a previous tag.
 
 

setting the user agent switcher to an iphone and a smartphone (xhtml) did not give an error.
Not sure what to advise here.
  • Page:
  • 1
  • 2
Time to create page: 0.23 seconds

By continuing to use this site you consent to the use of cookies on your device as described in our cookie policy unless you have disabled them. This site will not function correctly without cookies.

I accept cookies from this site.