[pmapper-users] Fatal error: Call to protected method Init_map::initJSReference()

2009-11-12 Thread Alexander Bonatti
I get this error when launching start.phtlml: Fatal error: Call to protected method Init_map::initJSReference() Software: ms4w_3.0_beta7 pmapper-4.0-beta3 Any help would be appreciated... -- Le

Re: [pmapper-users] display element colors

2009-11-12 Thread Armin Burger
http://svn.pmapper.net/trac/wiki/FaqCustomizations#CustomizationsofCSSandJavaScript -> Firebug On 12/11/2009 22:55, Kevin Edmundson wrote: > I am using pmapper v4 beta 3 and I am trying to get the footer section > (the part with the coordinates and the 3 links over on the right) to > display a spe

Re: [pmapper-users] Measure units

2009-11-12 Thread Armin Burger
On 13/10/2009 16:00, Kevin Edmundson wrote: > No matter what I use in the js_config.php > > /** > > * Units for measurement (distance, area) > > */ > > PM.MeasureUnits = {distance:" [ft]", area:" [ft²]", factor:1}; > > //PM.MeasureUnits = {distance:" [m]", area:" [m²]", factor:1}; > > //PM

[pmapper-users] measurement units and display

2009-11-12 Thread Kevin Edmundson
I ma trying to get the measurement tool to display measurements in feet and I only seem to see the settings in 'm' regardless of what I set where. Can anyone tell me what places I would need to alter to get it to display correct units (feet)? Kevin Edmundson CIO WTH Technology, Inc 567 W We

[pmapper-users] display element colors

2009-11-12 Thread Kevin Edmundson
I am using pmapper v4 beta 3 and I am trying to get the footer section (the part with the coordinates and the 3 links over on the right) to display a specific color. I can only find a way in the layout.css to change the background where the 3 links are on the right and I cant seem to find where th

Re: [pmapper-users] pmapper 4.0beta3 queryeditor

2009-11-12 Thread Siki Zoltan
Dear Thomas, Unfortunatelly neither 1, nor 2 helped me. Downloading the code from the trunk is working :) I suppose the error is not in the queryeditor's sources, there is only one difference, comparing to beta3, in queryeditor.php line 76-77. So I'll use rev 886 from trunk. Thank you and Arm

Re: [pmapper-users] pmapper 4.0beta3 queryeditor

2009-11-12 Thread Thomas Raffin
Maybe the beta3 is not working. The trunk version should works (I've just added a file right now !). I've got 3 solutions: 1) if pmapper/plugins/queryeditor/x_queryeditor.php contains those lines: "if (!isset($_SESSION['queryeditor_activated']) || !$_SESSION['queryeditor_activated']) { exit(

Re: [pmapper-users] pmapper 4.0beta3 queryeditor

2009-11-12 Thread Siki Zoltan
Hi, display_error is off and log_errors is on and error_log is set to the file I mentioned you. Zoltan On Thu, 12 Nov 2009, Thomas Raffin wrote: Have you got "display_errors = On" in your php.ini to show errors in Firefox ? Do not do that in a production server (or just a short time during

Re: [pmapper-users] pmapper 4.0beta3 queryeditor

2009-11-12 Thread Thomas Raffin
Have you got "display_errors = On" in your php.ini to show errors in Firefox ? Do not do that in a production server (or just a short time during tests ;-) ) Armin Burger a écrit : > On 12/11/2009 17:23, Siki Zoltan wrote: > >> Dear Thomas, >> >> I've tested beta3 on Fedora 10 and I get the

Re: [pmapper-users] pmapper 4.0beta3 queryeditor

2009-11-12 Thread Siki Zoltan
Dear Armin, In Firebug on the net tab I see a POST related to queryeditor with the PHPSESSID, the response is empty. In the Header hte content length is zero. With beta2 I got back a whole html page with the fields of the queryeditor (layer, field, etc.) Thanks, Zoltan On Thu, 12 Nov 2009, Arm

Re: [pmapper-users] pmapper 4.0beta3 queryeditor

2009-11-12 Thread Armin Burger
On 12/11/2009 17:23, Siki Zoltan wrote: > Dear Thomas, > > I've tested beta3 on Fedora 10 and I get the same empty window for the > query editor. > Zoltan are you sure that you don't get any Javascript error (using Firebug for instance)? With FB you can also check the requests sent to the serv

Re: [pmapper-users] pmapper 4.0beta3 queryeditor

2009-11-12 Thread Siki Zoltan
Dear Thomas, I've tested beta3 on Fedora 10 and I get the same empty window for the query editor. Regards, Zoltan On Thu, 12 Nov 2009, Siki Zoltan wrote: Dear Thomas, Yes, error reporting & debug level are set. Regards, Zoltan On Thu, 12 Nov 2009, Thomas Raffin wrote: Are you sure to log

[pmapper-users] static legend

2009-11-12 Thread Leonardo Olivieri
Hello, for quality reason, I prefer to have static legend instead of dynamic legend. Is it possible to configure pmapper for this? Thank in advance leonardo -- Let Crystal Reports handle the reporting - Free Crysta

Re: [pmapper-users] pmapper 4.0beta3 queryeditor

2009-11-12 Thread Siki Zoltan
Dear Thomas, Yes, error reporting & debug level are set. Regards, Zoltan On Thu, 12 Nov 2009, Thomas Raffin wrote: Are you sure to log enough messages (p.mapper debug level, PHP "error_reporting" value) ? I mean in your config_xxx.xml : 3 and in php.ini : error_reporting = E_ALL & ~E_NOTI

Re: [pmapper-users] pmapper 4.0beta3 queryeditor

2009-11-12 Thread Siki Zoltan
Hi Thomas, I tested it with ms4w. Using FF i get no error, neither pm_debug, nor php.log, nor apache error.log. In access.log I see a POST to queryeditordlg.phtml. Using IE6 I get an error in apache error.log winnt_accept: Asynchronous AcceptEx failed in front of it I have a Hungarian message,

Re: [pmapper-users] pmapper 4.0beta3 queryeditor

2009-11-12 Thread Thomas Raffin
Are you sure to log enough messages (p.mapper debug level, PHP "error_reporting" value) ? I mean in your config_xxx.xml : 3 and in php.ini : error_reporting = E_ALL & ~E_NOTICE Siki Zoltan a écrit : > Hi Thomas, > > I tested it with ms4w. Using FF i get no error, neither pm_debug, > nor php.lo

Re: [pmapper-users] pmapper 4.0beta3 queryeditor

2009-11-12 Thread Thomas Raffin
Hi, Have you got errors in your logs files ? Siki Zoltan a écrit : > Hi List, > > Upgrading from 4.0beta2 to 4.0beta3 I lost the queryeditor. > I get only an empty window when starting queryeditor. > The same config has worked in beta2. > Does anybody detect similar problem? > Any workaround? > >