Re: [pmapper-users] PMapper5 "bugs"

[Armin B. <arm...@gm...>]

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.