Re: [pmapper-users] PMapper5 "bugs"

[Raffaele M. <raf...@gm...>]

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 »