Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#132 closed defect (worksforme)

"Could not load mapbook" - new Install

Reported by: osjonathan Owned by: theduckylittle
Priority: minor Milestone: 2.6.1
Component: BuildTools Version: 2.6
Keywords: Cc:

Description

I've just installed GeoMoose and gotten it working properly for the first time. I've not configured it or anything.
If I access the site in Opera 12 or Chrome 18.0.10.25.142 I get this pop-up:

"Could not load a mapbook. If you are the system administrator, you should look into this, if you are not the system administrator you should tell them about this. Suggestions:
The mapbook may not be returning XML.
The mapbook may be returning malformed XML.
PHP may not be responding."

This is fine, and it'll probably mean something to me when I read more of the documentation.

The problem is that if I access the same page in IE8 or FireFox 11, I get nothing. Just the basic outline frame of the GeoMoose page, plus the OpenLayers zoomin/out bar. Nothing else.

Shouldn't all browsers should present the same error in the same way? If I just used IE or FF, I wouldn't have a clue what I needed to do next.

Change History (3)

comment:1 by theduckylittle, 12 years ago

Milestone: 2.6.1
Owner: set to theduckylittle
Status: newassigned

This ticket is missing some critia

comment:2 by theduckylittle, 12 years ago

Resolution: worksforme
Status: assignedclosed

This ticket is missing some critical information, specifically, the mapbook. This error message catches when no (or no valid) mapbook is returned from the "getmapbook.php" script. I was not able to recreate this in FF. Every time I did something silly with the mapbook, it would throw up this error message.

I'm "worksforme"ing this ticket and if something else comes up feel free to post up on the mailing list with the badly behaved mapbook.

comment:3 by osjonathan, 12 years ago

As the ticket states, I hadn't changed /anything/. The mapbook was the default one, untweaked. I don't remember what it was now that I did to get rid of the error, but the problem was, it only appeared in some browsers and not others.

Note: See TracTickets for help on using tickets.