Strict Standards: Non-static method Flyspray::absoluteURI() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/constants.inc.php on line 29 Strict Standards: Non-static method Flyspray::get_tmp_dir() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/constants.inc.php on line 78 Strict Standards: Non-static method Flyspray::base_version() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/header.php on line 29 Strict Standards: Non-static method Flyspray::base_version() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/header.php on line 29 Strict Standards: Non-static method Req::val() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/header.php on line 39 Strict Standards: Non-static method Req::has() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 26 Strict Standards: Non-static method Req::num() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/header.php on line 40 Strict Standards: Non-static method Req::val() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 32 Strict Standards: Non-static method Req::has() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 26 Strict Standards: Non-static method Filters::num() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 32 Strict Standards: Non-static method Req::num() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/header.php on line 42 Strict Standards: Non-static method Req::val() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 32 Strict Standards: Non-static method Req::has() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 26 Strict Standards: Non-static method Filters::num() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 32 Strict Standards: Non-static method Req::enum() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/index.php on line 15 Strict Standards: Non-static method Req::val() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 37 Strict Standards: Non-static method Req::has() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 26 Strict Standards: Non-static method Filters::enum() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 37 Strict Standards: Non-static method Req::has() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/index.php on line 21 Strict Standards: Non-static method Req::has() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/index.php on line 21 Strict Standards: Non-static method Cookie::has() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/index.php on line 28 Strict Standards: Non-static method Get::val() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/index.php on line 36 Strict Standards: Non-static method Get::has() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 100 Strict Standards: Non-static method Get::val() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/index.php on line 95 Strict Standards: Non-static method Get::has() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 100 Strict Standards: Non-static method Flyspray::requestDuplicated() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/index.php on line 104 Strict Standards: Non-static method Req::has() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/index.php on line 143 Strict Standards: Non-static method Req::num() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/scripts/details.php on line 15 Strict Standards: Non-static method Req::val() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 32 Strict Standards: Non-static method Req::has() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 26 Strict Standards: Non-static method Filters::num() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 32 Strict Standards: Non-static method Flyspray::GetTaskDetails() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/scripts/details.php on line 17 Strict Standards: Non-static method Flyspray::GetAssignees() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.flyspray.php on line 358 Strict Standards: Non-static method Get::val() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/scripts/details.php on line 34 Strict Standards: Non-static method Get::has() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 100 Strict Standards: Non-static method Post::has() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/scripts/details.php on line 34 Strict Standards: Non-static method TextFormatter::render() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/scripts/details.php on line 128 FS#163 : 1.2.0 - Separate core-configs and plugin-configs
homepage | forum | wiki | feature requests & bugs

MMS

Before posting a bug report please read: http://wiki.mymediasystem.org/wiki/index.php/Bug_reports
Tasklist

FS#163 - 1.2.0 - Separate core-configs and plugin-configs

Attached to Project: MMS
Opened by Strict Standards: array_map() expects parameter 1 to be a valid callback, non-static method Filters::noXSS() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.tpl.php on line 281 Roman (Uatschitchun) - Strict Standards: Non-static method Filters::noXSS() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.tpl.php on line 613 Sunday, 20 May 2007, 17:45 GMT+2
Last edited by Roman (Uatschitchun) - Strict Standards: Non-static method Filters::noXSS() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.tpl.php on line 613 Tuesday, 12 August 2008, 10:14 GMT+2
Task Type Feature Request
Category Backend / Core
Status Unconfirmed
Assigned To No-one
Operating System Linux
Severity Low
Priority Normal
Reported Version 1.1.0
Due in Version 1.2.0
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

We should have core-configs in /etc/mms/

For each plugin there should be a sub-directory /etc/mms/plugins/

Each plugin's config should the go into /etc/mms/plugins/plugin_name/config-files
This task depends upon

View Dependency Graph

This task blocks these from closing
Strict Standards: Non-static method Filters::noXSS() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.tpl.php on line 189 FS#276 - 1.2.0 - Make build-system more modular, plugin-example, plugin's
Comment by Strict Standards: array_map() expects parameter 1 to be a valid callback, non-static method Filters::noXSS() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.tpl.php on line 281 Anders Rune Jensen (arj) - Strict Standards: Non-static method Filters::noXSS() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.tpl.php on line 613 Sunday, 20 May 2007, 23:27 GMT+2
It each plugin has just one config file creating a folder for it seems unneeded?
Comment by Roman (Uatschitchun) - Strict Standards: Non-static method Filters::noXSS() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.tpl.php on line 613 Monday, 21 May 2007, 09:30 GMT+2
But if the plugin wants to have more than one file? Maybe dynamic .ops, etc. ...?
What if the number of possible plugins increases?
Having a folder for each plugin in first place look tidier. Second the plugin-author may do whatever he wants (nearly :) within his config-dir.

Example: The dir "scripts" is a dir coming from python-plugin ... for to make the user know that, it would be better placed in /etc/mms/plugins/python/, wouldn't it?

Loading...