pmapper-users Mailing List for p.mapper (Page 12)
Brought to you by:
arminburger
Menu
▾
▴
pmapper-users — p.mapper users mailing list
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(41) |
Nov
(124) |
Dec
(80) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(56) |
Feb
(51) |
Mar
(155) |
Apr
(58) |
May
(67) |
Jun
(83) |
Jul
(76) |
Aug
(32) |
Sep
(58) |
Oct
(113) |
Nov
(63) |
Dec
(83) |
| 2008 |
Jan
(31) |
Feb
(34) |
Mar
(69) |
Apr
(30) |
May
(87) |
Jun
(64) |
Jul
(47) |
Aug
(18) |
Sep
(35) |
Oct
(53) |
Nov
(37) |
Dec
(31) |
| 2009 |
Jan
(23) |
Feb
(40) |
Mar
(65) |
Apr
(54) |
May
(92) |
Jun
(55) |
Jul
(87) |
Aug
(27) |
Sep
(81) |
Oct
(32) |
Nov
(77) |
Dec
(51) |
| 2010 |
Jan
(44) |
Feb
(59) |
Mar
(77) |
Apr
(54) |
May
(36) |
Jun
(36) |
Jul
(52) |
Aug
(62) |
Sep
(68) |
Oct
(58) |
Nov
(72) |
Dec
(27) |
| 2011 |
Jan
(15) |
Feb
(42) |
Mar
(37) |
Apr
(55) |
May
(84) |
Jun
(27) |
Jul
(27) |
Aug
(42) |
Sep
(42) |
Oct
(18) |
Nov
(83) |
Dec
(71) |
| 2012 |
Jan
(50) |
Feb
(75) |
Mar
(79) |
Apr
(43) |
May
(18) |
Jun
(22) |
Jul
(20) |
Aug
(13) |
Sep
(26) |
Oct
(30) |
Nov
(21) |
Dec
(30) |
| 2013 |
Jan
(57) |
Feb
(63) |
Mar
(53) |
Apr
(40) |
May
(39) |
Jun
(16) |
Jul
(43) |
Aug
(16) |
Sep
(37) |
Oct
(64) |
Nov
(31) |
Dec
(7) |
| 2014 |
Jan
(14) |
Feb
(6) |
Mar
(2) |
Apr
(9) |
May
(1) |
Jun
(18) |
Jul
(95) |
Aug
(6) |
Sep
(25) |
Oct
(33) |
Nov
(29) |
Dec
(30) |
| 2015 |
Jan
(16) |
Feb
(3) |
Mar
(4) |
Apr
(9) |
May
(19) |
Jun
|
Jul
(11) |
Aug
(3) |
Sep
(9) |
Oct
(11) |
Nov
(4) |
Dec
(9) |
| 2016 |
Jan
(21) |
Feb
(9) |
Mar
(6) |
Apr
(13) |
May
(21) |
Jun
(4) |
Jul
(3) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2017 |
Jan
(1) |
Feb
(4) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
|
| 2018 |
Jan
(3) |
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
(3) |
May
(1) |
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Firdaus f. <ali...@gm...> - 2014-10-29 18:11:32
|
dear All, anyone has plugin in pmapper for displaying photo ? I saw a video in youtube http://www.youtube.com/watch?v=Ku3TsF9MOws where it is using pmapper. thanks for your help in advance |
|
From: Armin B. <arm...@gm...> - 2014-10-29 18:07:45
|
ok, I can change that, though I guess the the performance gain will be
likely quite small in real world situations. Lets just hope no field
names will be ever called "null" then... ;-)
armin
On 10/29/2014 12:26 PM, Thomas RAFFIN wrote:
> Hi,
>
> I think it should be better to use "isset($recIn[$fld])" instead of
> "array_key_exists($fld, $recIn)" by considering performance.
>
>
> Le 14/10/2014 19:10, Armin Burger a écrit :
>> On 10/14/2014 07:50 AM, Raffaele Morelli wrote:
>>> On 14/10/14 at 12:32am, Armin Burger wrote:
>>>> yes, I guess this was always the way how it worked aslo in older
>>>> versions. It's not just for Postgis but also shapefile layers etc.
>>>>
>>>> The change to make it behave as you expected is to modify the
>>>> lib/query/query.php file at line 229 replacing the 4 subsequent lines
>>>> with the following ones:
>>>> foreach ($resultFields as $fld) {
>>>> if (array_key_exists($fld, $recIn)) {
>>>> $rec[$fld] = $recIn[$fld];
>>>> }
>>>> }
>>>>
>>>> Maybe a bit of testing would be needed but it could be changed in the
>>>> main code to always work like that, I agree that it seems more logic...
>>>>
>>>> armin
>>> Tested a little and works smoothly. IMHO it should be committed because when
>>> dealing with query results it's really useful to rearrange fields order and left
>>> db query untouched (even more with shapefile's dbf, I guess).
>> OK, committed to svn trunk
>>
>> ------------------------------------------------------------------------------
>> Comprehensive Server Monitoring with Site24x7.
>> Monitor 10 servers for $9/Month.
>> Get alerted through email, SMS, voice calls or mobile push notifications.
>> Take corrective actions from your mobile device.
>> http://p.sf.net/sfu/Zoho
>> _______________________________________________
>> pmapper-users mailing list
>> pma...@li...
>> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>>
>>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> pmapper-users mailing list
> pma...@li...
> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>
|
|
From: Thomas R. <tr...@si...> - 2014-10-29 11:45:18
|
Hi,
I think it should be better to use "isset($recIn[$fld])" instead of
"array_key_exists($fld, $recIn)" by considering performance.
Le 14/10/2014 19:10, Armin Burger a écrit :
> On 10/14/2014 07:50 AM, Raffaele Morelli wrote:
>> On 14/10/14 at 12:32am, Armin Burger wrote:
>>> yes, I guess this was always the way how it worked aslo in older
>>> versions. It's not just for Postgis but also shapefile layers etc.
>>>
>>> The change to make it behave as you expected is to modify the
>>> lib/query/query.php file at line 229 replacing the 4 subsequent lines
>>> with the following ones:
>>> foreach ($resultFields as $fld) {
>>> if (array_key_exists($fld, $recIn)) {
>>> $rec[$fld] = $recIn[$fld];
>>> }
>>> }
>>>
>>> Maybe a bit of testing would be needed but it could be changed in the
>>> main code to always work like that, I agree that it seems more logic...
>>>
>>> armin
>> Tested a little and works smoothly. IMHO it should be committed because when
>> dealing with query results it's really useful to rearrange fields order and left
>> db query untouched (even more with shapefile's dbf, I guess).
> OK, committed to svn trunk
>
> ------------------------------------------------------------------------------
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> pmapper-users mailing list
> pma...@li...
> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>
>
|
|
From: gioza <al...@al...> - 2014-10-29 11:00:11
|
I realised that some options/settings in js_config.php don't work. ex.: iquery, scale, table/tree results... Is it possible to set tool tips results like in pmapper4? -- View this message in context: http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/Pmapper5-do-all-options-in-js-config-php-work-tp4025643.html Sent from the pmapper-users -- p.mapper users mailing list mailing list archive at Nabble.com. |
|
From: gioza <al...@al...> - 2014-10-16 07:33:30
|
Very useful! -- View this message in context: http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/pmapper-users-PMapper5-PM-RESULT-FIELDS-order-not-observed-tp4025638p4025642.html Sent from the pmapper-users -- p.mapper users mailing list mailing list archive at Nabble.com. |
|
From: Armin B. <arm...@gm...> - 2014-10-14 17:10:53
|
On 10/14/2014 07:50 AM, Raffaele Morelli wrote:
> On 14/10/14 at 12:32am, Armin Burger wrote:
>> yes, I guess this was always the way how it worked aslo in older
>> versions. It's not just for Postgis but also shapefile layers etc.
>>
>> The change to make it behave as you expected is to modify the
>> lib/query/query.php file at line 229 replacing the 4 subsequent lines
>> with the following ones:
>> foreach ($resultFields as $fld) {
>> if (array_key_exists($fld, $recIn)) {
>> $rec[$fld] = $recIn[$fld];
>> }
>> }
>>
>> Maybe a bit of testing would be needed but it could be changed in the
>> main code to always work like that, I agree that it seems more logic...
>>
>> armin
>
> Tested a little and works smoothly. IMHO it should be committed because when
> dealing with query results it's really useful to rearrange fields order and left
> db query untouched (even more with shapefile's dbf, I guess).
OK, committed to svn trunk
|
|
From: Raffaele M. <raf...@gm...> - 2014-10-14 05:50:07
|
On 14/10/14 at 12:32am, Armin Burger wrote:
> yes, I guess this was always the way how it worked aslo in older
> versions. It's not just for Postgis but also shapefile layers etc.
>
> The change to make it behave as you expected is to modify the
> lib/query/query.php file at line 229 replacing the 4 subsequent lines
> with the following ones:
> foreach ($resultFields as $fld) {
> if (array_key_exists($fld, $recIn)) {
> $rec[$fld] = $recIn[$fld];
> }
> }
>
> Maybe a bit of testing would be needed but it could be changed in the
> main code to always work like that, I agree that it seems more logic...
>
> armin
Tested a little and works smoothly. IMHO it should be committed because when
dealing with query results it's really useful to rearrange fields order and left
db query untouched (even more with shapefile's dbf, I guess).
eg. I would prefer to put hyperlink stuff in the last columns
/raffaele
--
« Nunc est bibendum, nunc pede libero pulsanda tellus »
|
|
From: Armin B. <arm...@gm...> - 2014-10-13 22:33:00
|
yes, I guess this was always the way how it worked aslo in older
versions. It's not just for Postgis but also shapefile layers etc.
The change to make it behave as you expected is to modify the
lib/query/query.php file at line 229 replacing the 4 subsequent lines
with the following ones:
foreach ($resultFields as $fld) {
if (array_key_exists($fld, $recIn)) {
$rec[$fld] = $recIn[$fld];
}
}
Maybe a bit of testing would be needed but it could be changed in the
main code to always work like that, I agree that it seems more logic...
armin
On 10/13/2014 01:47 PM, Raffaele Morelli wrote:
> Hi,
>
> there's an issue with PM_RESULT_FIELDS and the specified order of fields.
>
> No matter what is specified in PM_RESULT_FIELDS, fields order follows postgis
> table fields order.
>
> Can you confirm this behaviour?
>
|
|
From: Raffaele M. <raf...@gm...> - 2014-10-13 11:47:31
|
Hi, there's an issue with PM_RESULT_FIELDS and the specified order of fields. No matter what is specified in PM_RESULT_FIELDS, fields order follows postgis table fields order. Can you confirm this behaviour? -- « Nunc est bibendum, nunc pede libero pulsanda tellus » |
|
From: gioza <al...@al...> - 2014-10-12 17:48:47
|
I khow but it doesn't work for "selected features" using the search tool -- View this message in context: http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/Pmapper5-zoom-to-selected-features-tp4025486p4025637.html Sent from the pmapper-users -- p.mapper users mailing list mailing list archive at Nabble.com. |
|
From: Armin B. <arm...@gm...> - 2014-10-10 21:22:05
|
an even better solution is to use the config parameters
<pointBuffer>
<shapeQueryBuffer>
and adapt them to the coordinate system used for your map and typical
scales used for tour application...
On 10/10/2014 09:06 PM, gioza wrote:
> a much better solution for my work is to modify pm.map.js in this way:
>
> line 162
>
> zoom2extent: function(layer, idx, extStr, zoomfull) {
> var ext = extStr.split(",");
>
> var minx = (ext[0]*0.9995);
> var miny = (ext[1]*0.9995);
> var maxx = (ext[2]*1.0005);
> var maxy = (ext[3]*1.0005);
>
> map.zoomToExtent( new OpenLayers.Bounds(minx, miny, maxx, maxy), true );
>
>
> },
>
> the previous solution gives problem with History Navigation...
>
>
>
> --
> View this message in context: http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/Pmapper5-zoom-to-selected-features-tp4025486p4025634.html
> Sent from the pmapper-users -- p.mapper users mailing list mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> pmapper-users mailing list
> pma...@li...
> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>
|
|
From: gioza <al...@al...> - 2014-10-10 19:19:16
|
according to your project extension you have to set the coefficent which adjust the extent of the selected features: var minx = (ext[0]**0.9999*); var miny = (ext[1]**0.9999*); var maxx = (ext[2]**1.000*1); var maxy = (ext[3]**1.0001*); -- View this message in context: http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/Pmapper5-zoom-to-selected-features-tp4025486p4025635.html Sent from the pmapper-users -- p.mapper users mailing list mailing list archive at Nabble.com. |
|
From: gioza <al...@al...> - 2014-10-10 19:06:44
|
a much better solution for my work is to modify pm.map.js in this way:
line 162
zoom2extent: function(layer, idx, extStr, zoomfull) {
var ext = extStr.split(",");
var minx = (ext[0]*0.9995);
var miny = (ext[1]*0.9995);
var maxx = (ext[2]*1.0005);
var maxy = (ext[3]*1.0005);
map.zoomToExtent( new OpenLayers.Bounds(minx, miny, maxx, maxy), true );
},
the previous solution gives problem with History Navigation...
--
View this message in context: http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/Pmapper5-zoom-to-selected-features-tp4025486p4025634.html
Sent from the pmapper-users -- p.mapper users mailing list mailing list archive at Nabble.com.
|
|
From: gioza <al...@al...> - 2014-10-10 13:39:51
|
for better performance add PM.Map.clearHighlight in pm.query.js in this way:
after line 81
execute: function(queryUrl, queryParams) {
PM.Map.clearHighlight();
var self = this;
...
--
View this message in context: http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/Pmapper5-zoom-to-selected-features-tp4025486p4025633.html
Sent from the pmapper-users -- p.mapper users mailing list mailing list archive at Nabble.com.
|
|
From: gioza <al...@al...> - 2014-10-10 09:38:53
|
I figured out with a change to pm.map.js:
add to line 162->166 the map.zoomOut() control in this way:
FROM
zoom2extent: function(layer, idx, extStr, zoomfull) {
var ext = extStr.split(",");
map.zoomToExtent( new OpenLayers.Bounds(ext[0], ext[1], ext[2], ext[3]),
true );
},
TO
zoom2extent: function(layer, idx, extStr, zoomfull) {
var ext = extStr.split(",");
map.zoomToExtent( new OpenLayers.Bounds(ext[0], ext[1], ext[2], ext[3]),
true );
map.zoomOut();
},
As you select a features by "search tools" the zoomToextent will zoom out so
that all the features you selected with the query are completely visible
--
View this message in context: http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/Pmapper5-zoom-to-selected-features-tp4025486p4025632.html
Sent from the pmapper-users -- p.mapper users mailing list mailing list archive at Nabble.com.
|
|
From: Raffaele M. <raf...@gm...> - 2014-10-10 04:43:25
|
On 09/10/14 at 09:21pm, Armin Burger wrote:
> On 10/09/2014 02:50 PM, Raffaele Morelli wrote:
> > On 09/10/14 at 02:16pm, Armin Burger wrote:
> >> regarding the domains issues, try the following:
> >>
> >> modify file
> >> "plugins/tocdomains/tocdomains.js"
> >> and add after line 60 the following
> >>
> >> if (typeof domCategories === 'string') {
> >> domCategories = [ domCategories ];
> >> }
> >
> > Yep, fixed.
>
> OK, committed to SVN
>
>
> >> Regarding the second issue, the configuration structure was not meant
> >> to have a deeper structure, like all the other PHP or JS files cannot
> >> just be placed in other folders or changing the tree depth etc. But the
> >> workaround is quite easy, just modify the require_once relative paths
> >> to match your file structure...
> >
> > I wrote that because with 4.3.* config files can be nested at least with depth
> > two, that meaning : config/dir1/config_location
> >
> > I am dealing with ~20 configurations and nesting results in a clearer directory
> > "look", anyway I've changed the require_once.
>
> I'm wondering why it should work in p.mapper 4.1+ since the default
> include statement there also just goes up 2 directories to reach "incphp":
> require_once("../../incphp/*.php");
Because of the use of $_SESSION variables, here's the code snippet on my
installation...
<?php
session_start();
require_once($_SESSION['PM_INCPHP'] . "/globals.php");
require_once($_SESSION['PM_INCPHP'] . "/common.php");
header("Content-Type: text/javascript; charset=$defCharset");
?>
>
>
>
> > PS is there any ongoing work on PMapper5 release?
>
> currently no work ongoing.
--
« Nunc est bibendum, nunc pede libero pulsanda tellus »
|
|
From: Armin B. <arm...@gm...> - 2014-10-09 19:21:35
|
On 10/09/2014 02:50 PM, Raffaele Morelli wrote:
> On 09/10/14 at 02:16pm, Armin Burger wrote:
>> regarding the domains issues, try the following:
>>
>> modify file
>> "plugins/tocdomains/tocdomains.js"
>> and add after line 60 the following
>>
>> if (typeof domCategories === 'string') {
>> domCategories = [ domCategories ];
>> }
>
> Yep, fixed.
OK, committed to SVN
>> Regarding the second issue, the configuration structure was not meant
>> to have a deeper structure, like all the other PHP or JS files cannot
>> just be placed in other folders or changing the tree depth etc. But the
>> workaround is quite easy, just modify the require_once relative paths
>> to match your file structure...
>
> I wrote that because with 4.3.* config files can be nested at least with depth
> two, that meaning : config/dir1/config_location
>
> I am dealing with ~20 configurations and nesting results in a clearer directory
> "look", anyway I've changed the require_once.
I'm wondering why it should work in p.mapper 4.1+ since the default
include statement there also just goes up 2 directories to reach "incphp":
require_once("../../incphp/*.php");
> PS is there any ongoing work on PMapper5 release?
currently no work ongoing.
|
|
From: Raffaele M. <raf...@gm...> - 2014-10-09 12:50:26
|
On 09/10/14 at 02:16pm, Armin Burger wrote:
> regarding the domains issues, try the following:
>
> modify file
> "plugins/tocdomains/tocdomains.js"
> and add after line 60 the following
>
> if (typeof domCategories === 'string') {
> domCategories = [ domCategories ];
> }
Yep, fixed.
>
> Regarding the second issue, the configuration structure was not meant
> to have a deeper structure, like all the other PHP or JS files cannot
> just be placed in other folders or changing the tree depth etc. But the
> workaround is quite easy, just modify the require_once relative paths
> to match your file structure...
I wrote that because with 4.3.* config files can be nested at least with depth
two, that meaning : config/dir1/config_location
I am dealing with ~20 configurations and nesting results in a clearer directory
"look", anyway I've changed the require_once.
Regards
/r
PS is there any ongoing work on PMapper5 release?
>
> Armin
>
>
> Gesendet: Donnerstag, 09. Oktober 2014 um 06:43 Uhr
> Von: "Raffaele Morelli" <raf...@gm...>
> An: pma...@li...
> Betreff: [pmapper-users] PMapper5 "bugs"
> Hi there,
> I am working on PMapper5 beta2 and got it up and running.
> As I dig into configuration I've found a couple of "bugs" (but maybe I
> am wrong)
> and if there's still interest in that here they are:
> - domains definition must contain at least two categories in order to
> show up,
> if it doesn't then domain is collapsed and no category is showed at
> all.
> Adding an empty category tag "fixes" that.
> - js_config.php: require_once in in line #3
> require_once("../../lib/pmsession.php");
> path is relative to config dir so if you have a deeper tree to your
> config
> require_once doesn't work anymore
> Hope this is useful
> Regards
> /r
> --
--
« Nunc est bibendum, nunc pede libero pulsanda tellus »
|
|
From: Armin B. <arm...@gm...> - 2014-10-09 12:16:43
|
regarding the domains issues, try the following:
modify file
"plugins/tocdomains/tocdomains.js"
and add after line 60 the following
if (typeof domCategories === 'string') {
domCategories = [ domCategories ];
}
Regarding the second issue, the configuration structure was not meant to
have a deeper structure, like all the other PHP or JS files cannot just be
placed in other folders or changing the tree depth etc. But the workaround
is quite easy, just modify the require_once relative paths to match your
file structure...
Armin
Gesendet: Donnerstag, 09. Oktober 2014 um 06:43 Uhr
Von: "Raffaele Morelli" <raf...@gm...>
An: pma...@li...
Betreff: [pmapper-users] PMapper5 "bugs"
Hi there,
I am working on PMapper5 beta2 and got it up and running.
As I dig into configuration I've found a couple of "bugs" (but maybe I am
wrong)
and if there's still interest in that here they are:
- domains definition must contain at least two categories in order to show
up,
if it doesn't then domain is collapsed and no category is showed at all.
Adding an empty category tag "fixes" that.
- js_config.php: require_once in in line #3
require_once("../../lib/pmsession.php");
path is relative to config dir so if you have a deeper tree to your config
require_once doesn't work anymore
Hope this is useful
Regards
/r
--
« Nunc est bibendum, nunc pede libero pulsanda tellus »
----------------------------------------------------------------------------
--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
[1]http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clk
trk
_______________________________________________
pmapper-users mailing list
pma...@li...
[2]https://lists.sourceforge.net/lists/listinfo/pmapper-users
References
1. http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
2. https://lists.sourceforge.net/lists/listinfo/pmapper-users
|
|
From: Raffaele M. <raf...@gm...> - 2014-10-09 04:43:06
|
Hi there,
I am working on PMapper5 beta2 and got it up and running.
As I dig into configuration I've found a couple of "bugs" (but maybe I am wrong)
and if there's still interest in that here they are:
- domains definition must contain at least two categories in order to show up,
if it doesn't then domain is collapsed and no category is showed at all.
Adding an empty category tag "fixes" that.
- js_config.php: require_once in in line #3
require_once("../../lib/pmsession.php");
path is relative to config dir so if you have a deeper tree to your config
require_once doesn't work anymore
Hope this is useful
Regards
/r
--
« Nunc est bibendum, nunc pede libero pulsanda tellus »
|
|
From: Raffaele M. <raf...@gm...> - 2014-09-24 09:10:30
|
Hi, I have a pmapper instance and would like to use drupal auth system in order to access several maps (pmapper configs). Target is to serve different pmapper configs according to users profile attributes: eg. if user A has xy attribute I serve config=xy, etc etc So I placed an include in index.phtml which loads drupal user data, parses the attributes, check if is logged and then redirects him to map_default.phtml?config=CONFIG Problem arise because the user can change the url and switch to other config which doesn't belog to him after the maps is loaded. How can I prevent this? is there any clever way to do this routing according to "who the user is"? /regards -- « Nunc est bibendum, nunc pede libero pulsanda tellus » |
|
From: Solly V. <sol...@gm...> - 2014-09-20 08:42:11
|
This is very interesting and I like it, I cant wait to work on it, I so wish you can add the basemap layers like Open source and Google background together with Print function Thank you On 20 Sep 2014 2:37 AM, "Yuswardy Fatah" <yus...@gm...> wrote: > It would be great to have such function in pmapper. I will be very happy to > have it and waiting for the time you release it. 😉 > > Thank you in advance. > On Sep 20, 2014 7:26 AM, "ntasoft" <nt...@gm...> wrote: > > > Base on your source code pmapper, I build interface Admin for pmapper. > > function for system: > > + Login admin: > > < > > > http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/file/n4025623/login.png > > > > > + Create plugin: > > - auto generate folder plugin, js, php, css, and developer continue write > > soucre code for plugin > > > > + Create layout (toolbar): > > - Defaut: your source code: open file js_config.php and cofig folow idea, > > but Now i build admin for user set plugin on 4 toolbar (Left, Right, Top, > > Bottom) > > + Layer group: > > - Default: your source code: open file config_{folder}.xml and write: > > <category name="cat_admin"> > > <group>countries</group> > > <group>cities10000eu</group> > > </category> > > > > <category name="cat_nature"> > > <group>rivers</group> > > </category> > > > > <category name="cat_raster"> > > <group>dem</group> > > > > <group>jpl_wms_global_mosaic</group> > > </category> > > > > But Now i Build admin for user create layergroup on interface, affter > user > > click button generate mapfile, my system auto generate: > > config_{foldername}.xml, and .map > > + Layer: > > interface config layer for map ( layer must on layer group) > > .. I attach image screeen admin for pmapper > > I hope i can realese this version for you! > > < > > > http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/file/n4025623/screenupdate-createplugin.png > > > > > < > > > http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/file/n4025623/screenlistplugin.png > > > > > < > > > http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/file/n4025623/screenlistmap.png > > > > > < > > > http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/file/n4025623/screeneditmap.png > > > > > < > > > http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/file/n4025623/screenlayout.png > > > > > < > > > http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/file/n4025623/screenaddplugintotoolbar.png > > > > > < > > > http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/file/n4025623/screenlayoutaffteraddplugin.png > > > > > < > > > http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/file/n4025623/layergroup.png > > > > > < > > > http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/file/n4025623/screenadd-editlayergroup.png > > > > > < > > > http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/file/n4025623/screenlayers.png > > > > > < > > > http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/file/n4025623/screenaddlayer.png > > > > > < > > > http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/file/n4025623/screeneditlayer_basedata.png > > > > > < > > > http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/file/n4025623/screenadd_edit_propertylayer.png > > > > > < > > > http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/file/n4025623/screenlistpropertylayer.png > > > > > < > > > http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/file/n4025623/screenlistclasslayer.png > > > > > < > > > http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/file/n4025623/screenupdate_classlayer.png > > > > > < > > > http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/file/n4025623/screen_edit_propertyclass.png > > > > > < > > > http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/file/n4025623/screenlistmap.png > > > > > < > > > http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/file/n4025623/screenresult_map.png > > > > > ................... > > I hope i can realese this version for anyone! > > > > > > > > -- > > View this message in context: > > > http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/Interface-Admin-for-Pmapper-tp4025623.html > > Sent from the pmapper-users -- p.mapper users mailing list mailing list > > archive at Nabble.com. > > > > > > > ------------------------------------------------------------------------------ > > Slashdot TV. Video for Nerds. Stuff that Matters. > > > > > http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk > > _______________________________________________ > > pmapper-users mailing list > > pma...@li... > > https://lists.sourceforge.net/lists/listinfo/pmapper-users > > > > ------------------------------------------------------------------------------ > Slashdot TV. Video for Nerds. Stuff that Matters. > > http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk > _______________________________________________ > pmapper-users mailing list > pma...@li... > https://lists.sourceforge.net/lists/listinfo/pmapper-users > |
|
From: gioza <al...@al...> - 2014-09-19 08:15:58
|
i'm testing in google chrome vers. 39.x canary and it seems to work fine! i let you khow -- View this message in context: http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/last-google-chrome-version-bugs-with-pmapper5-tp4025616p4025622.html Sent from the pmapper-users -- p.mapper users mailing list mailing list archive at Nabble.com. |
22 messages has been excluded from this view by a project administrator.
