Maps are working fine in my custom skin at www.wikiwhereis.com, but not on the mobile version with the WPTouch skin. Only error I see in chrome's inspect element feature is "Uncaught ReferenceError: mw is not defined" in ";mw.loader.state({"site":"ready"});" on load.php. Not sure if this is causing the problem or if there is another issue with the skin. Any help is appreciated. You can see a map at http://www.wikiwhereis.com/index.php?title=Texas/San_Antonio/Post_Offices/Thousand_Oaks_Post_Office&useskin=wptouch Thanks!
Topic on Extension talk:Maps
Are you sure this mobile skin is properly compatible with MediaWiki 1.17 and later?
You can try using Maps 2.0 which I just released.
Sorry for the reposts. Just tried to upgrade to Maps/SemanticMaps 2.0, and wasn't able to. Installed both updates, and got a 500 error on every page. Thought it was maybe because I was running v4.13 of Validator, so I upgraded to 5, and that caused an error on all my pages with the Semantic Mediawiki ask category function. I have some modifications done to that function's query printer, but I'd be surprised if they were breaking it?
Skin is supposed to be good for 1.18+, but I'm sure it's by no means perfect. My guess is some javascript is breaking before the map loads, and I know very little about javascript. Site for the skin is here - http://www.memorydeleted.com/?p=396 . I assumed it was a popular mobile skin, and that maybe someone else running the maps extension had run into the problem before.
Thanks for the reply, and the update...despite the troubles and all, lol.
Hi, I have same problem and would like to upgrade to Maps 2.0 but I see that PHP5.3 is a requirement and my wiki's run on php 5.2.17. Are there alternatives for migrating to a provider with php 5.3?
I saw the requirements said 5.3 too, and my hosting provider is still on 5.2.x as well. I should be getting my new server in any day now, so I'll be hosting myself then. Anyone got it working on 5.2.x in the mean time?
If you are running PHP 5.2.x, stick with Maps 1.0.x or upgrade your PHP to a recent version first. There is no easy workaround.
For others that might run into this problem with other skins, it ended up being a problem with the static header the skin used. I copied the dynamic header from another skin, and it added the necessary javascript that the map was looking for.