mobiReady HTML pages, and results for other markup languages may not be meaningful. Markup language identified as WML.

Posted by quest2000 2 years 39 weeks ago

quest2000

mobiForge Newbie

Posts: 3

Joined: 2 years ago

[offline]

I'm a new user and
I keep getting the following in mobiRead:

Report did not complete successfully for http://www.theqereport.com/mobile/qe/default.aspx
Your markup is not supported by the ready.mobi report tool. Ready.mobi is designed to test (X)HTML pages, and results for other markup languages may not be meaningful. Markup language identified as WML

What is the problem.

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="mobile_qe_Default" %>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <html xmlns="http://www.w3.org/1999/xhtml" >
<head>
    <title>Hello Mobile World</title>
    <style type="text/css">
        h1 { background-color: #000000; color: #ffffff;}
    	li { list-style: none;}
    </style>
</head>
<body>
    <form id="form1" runat="server">
    <div>
         <asp:Label ID="lb_Image" runat="server" Text="Image"></asp:Label>
     <h1>Hello 
        <asp:Label ID="lb_vendor" runat="server" Text="New"></asp:Label> 
        user!
    </h1>
     <ul>
        <li><a href="index.php?page=1" accesskey="1">(1) Link 1</a></li>
        <li><a href="index.php?page=2" accesskey="2">(2) Link 2</a></li>
        <li><a href="index.php?page=3" accesskey="3">(3) Link 3</a></li>
    </ul>
    <p>Lorem ipsum dolor sit amet, consectetuer adipiscing elit. 
    In euismod mi a urna. In ultrices turpis vitae nibh.</p>
    <p>Sed sed ipsum id dolor nonummy dignissim. Nulla mi ante, 
    placerat nec, vestibulum sed, fringilla at, velit.</p>
    <p>Nulla nonummy purus sed nisl. Mauris tincidunt urna sit amet dui. 
    Cras sem justo, mollis et, tincidunt a, pellentesque eget, quam. 
    Vestibulum quis velit et erat dictum ultrices. 
    Praesent fermentum arcu nec sapien. Nunc eleifend.</p>
    </div>
    </form>
</body>
</html>

Posted by ruadhan 2 years ago

ruadhan

Mobile Champion

Posts: 710

Joined: 5 years ago

[offline]

Hmmm, certainly doesn't look like WML, might be a bug we'll check it out

Ruadhan O'Donoghue
dotMobi

Posted by quest2000 2 years ago

quest2000

mobiForge Newbie

Posts: 3

Joined: 2 years ago

[offline]

I noticed when I removed

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="mobile_qe_Default" %>

from my code it worked...

I need this <%%> for my code behide for C#
If I leave the line(code) in and refresh the page and view the source all you see is a blank line like its not there but readmobi still want read it.

FYI
You said this doesn't look like WML should it be and how would I do that in C#?

Posted by quest2000 2 years ago

quest2000

mobiForge Newbie

Posts: 3

Joined: 2 years ago

[offline]

The code

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="mobile_qe_Default" %>

Posted by ruadhan 2 years ago

ruadhan

Mobile Champion

Posts: 710

Joined: 5 years ago

[offline]

It looks like your site IS returning WML for certain User agents. If you use the advanced options on the home page of ready. mobi you can change the user agent that ready.mobi sends to see how your site behaves. The markup that ready.mobi is seeing is:

<?xml version='1.0'?>
<!DOCTYPE wml PUBLIC '-//WAPFORUM//DTD WML 1.1//EN' 'http://www.wapforum.org/DTD/wml_1.1.xml'><wml><head>
<meta http-equiv="Cache-Control" content="max-age=0" />
</head>
<card title="Server Error in /">
<p><b><big>image.Png is not of type integer</big></b><br/>
An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.<br/>
Exception Details: Mobi.Mtld.DA.Exception.IncorrectPropertyTypeException: image.Png is not of type integer</p></card>
</wml>

So it looks like an error is occurring in your device detection, and possibly that your server error page is defaulting to a WML page (this is probably configurable somewhere...)

Ruadhan O'Donoghue
dotMobi