[pmapper-users] (no subject)

2008-03-19 Thread stirner mathematic
Hi list I have work with pmapper 3.2 it work fine, but i have an problem with print map.. I don't know happenis this the messenger Fatal error: [MapServer Error]: msImageLoadGD(): (c:/ms4w/apache/htdocs/tesis/config/default/images/reference_d.png) in

[pmapper-users] Problems with firefox 2.0.0

2008-03-19 Thread Rony (PMPG)
Hi list, Sorry for ask again, but i need to solve this issue. Does anybody knows if there is a problem using pmapper under firefox 2.0.0.12? I can run pmapper 3.2 (final realease) under IE7. The south DIV goes to the north place and below that just display a blue screen. Any idea? Thanks, Rony

Re: [pmapper-users] Problems with firefox 2.0.0

2008-03-19 Thread Armin Burger
yes, it's mainly tested with FF (usually problems appear with IE...) Try emptying cache and cookies and reload again. armin On 19/03/2008 16:47, Rony (PMPG) wrote: Hi list, Sorry for ask again, but i need to solve this issue. Does anybody knows if there is a problem using pmapper under

Re: [pmapper-users] Problems with firefox 2.0.0

2008-03-19 Thread Rony (PMPG)
Hi Armin, It´s very strange because 3.1 works fine with IE and FF, but 3.2 (including the pmapper demodata) just works with IE in all the PC's of my intranet, not just in mine. Could you please test my application on your computer and report me what happens (IE and FF)?

Re: [pmapper-users] Problems with firefox 2.0.0

2008-03-19 Thread Armin Burger
you get a lot of JS errors. It should be mainly the 1st that causes all subsequent ones: illegal character [Break on this error] // ARRAY FOR ANNOTATIONS\n js_custom.php (line 4) Remove the 'illegal' character (you might need an editor that can work with UTF) and try again. and as usual:

Re: [pmapper-users] Problems with firefox 2.0.0

2008-03-19 Thread Ivan Mincik
You have to remove wrong characters // ARRAY FOR ANNOTATIONS\n as Armin wrote. I am always doing it on one server. On other machines it is working well also with these characters. Also You have some other javascript errors which are not appearing in my applications. (tested on Iceweasel