Plugin features in packages.

[jaapvstr]

Having an option to add plugin features to packages. By specifying this in a config file in the plugin fileset or something like that?

The advantage of this is that you don't need to modify alot in the core CMD template files to try to simulate this.

 

[hehachris]

By specifying this in a config file

I sceond this, which could save us a lot of work.

http://www.directadmin.com/features.php?id=479
with the feature in the above link, we still need to parse the user config file to check if the user is privileged.

 

[jaapvstr]

yeah, not having this promotes sloppy coding, such as the awstats plugin.


That plugin gives the admin a panel to decide what users to give access to the plugin, however, admins should not be the ones busy with this. They should give the resellers rights to resell those features, which then can give it to their users.

I do understand why it has been done that way though, since that saves alot of time programming-wise.

 

[jaapvstr]

http://www.directadmin.com/features.php?id=479
with the feature in the above link, we still need to parse the user config file to check if the user is privileged.

With the feature in the above link if i add

feature=type=checkbox&string=Awstats&desc=Werkt nog niet. Zie Admin Level om dit nu te regelen&checked=no

It gets shown in both the reseller package and in the user packages. I can't (easily) make it work the following way:

Show it in creating reseller packages, and only show it in user packages if reseller has has the rights to resell.

------------------------------------------------------

I tried to improve it already a bit by using

#!/bin/sh
DADIR = /usr/local/directadmin/

for dir in `find ${DADIR}/plugins -type d`
do
   echo `${dir}/custom_package_items.conf`
done

But its not a file that's executed, it's a file thats `cat`-ed