[pmapper-users] PMapper5 "bugs"

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[pmapper-users] PMapper5 "bugs"

Raffaele Morelli

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
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
pmapper-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/pmapper-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [pmapper-users] PMapper5 "bugs"

Armin Burger-2

   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" <[hidden email]>
   An: [hidden email]
   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
   [hidden email]
   [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
------------------------------------------------------------------------------
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://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
pmapper-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/pmapper-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [pmapper-users] PMapper5 "bugs"

Raffaele Morelli
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" <[hidden email]>
>    An: [hidden email]
>    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
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
pmapper-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/pmapper-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [pmapper-users] PMapper5 "bugs"

Armin Burger
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.


------------------------------------------------------------------------------
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://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
pmapper-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/pmapper-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [pmapper-users] PMapper5 "bugs"

Raffaele Morelli
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 »

------------------------------------------------------------------------------
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://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
pmapper-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/pmapper-users
Loading...