Hello again!!
I've finally developed this plugin. You can find it at the RoundCube
plugins repository, http://trac.roundcube.net/wiki/Plugin_Repository ,
or directly on SourceForge,
http://sourceforge.net/projects/rolespermission/ . Read documentation
for installation instructions (as easy as normal for plugins).
There already are some feature request I have created. They are
questions and proposals for RoundCube core developers. One, the most
important (I think) is a inter-plugins communication solution other
than the JavaScript. For going everything OK, I think plugins may be
able to define other plugins default variables and/or functions. I
mean, this plugin needs other plugins variable "permissions", where
other plugins should define their own permissions. From now on, this
plugin defines a global variable to link to its instance, so other
plugins can register permissions with a public function inside their
__construct function. Nasty, I think.
So here is a plugin and an open debate.
Best regards,
emi
2010/4/14 till <till(a)php.net>:
> I think its a great idea!
>
> On Apr 14, 2010 11:48 AM, "emi" <emidaruma(a)gmail.com> wrote:
>
> Hi there!!
> I'm making a plugin which does nothing but add an API and a
> preferences section to let other plugins distinguish between different
> kinds of users, what normally is called "User roles". A user may
> belong to none, one or multiple roles. Roles may be, for example,
> "Administrator", "Boss", etc. After this, other plugins may use this
> relationships to give some special rights to some users, not all of
> them.
>
> This could be used, for example, to do what now is done via
> config.inc.php. Can be also used for an infinity of cases: "Can add
> contacts to global address", "Can do a webconference", "Can define new
> calendars", etc.
>
> My idea to do so is that other plugins may declare permissions (for
> example, "Can configure MyPlugin"). Then, the master of the
> installation or those who have "Change permissions" rights could
> assign this permission to some role(s). This idea is just copied from
> Drupal, but surely it is used in many more programs.
>
> Do anybody has contributions/ideas/wishes for this plugin? Do any
> plugin developer see this is a good idea?
>
> Best regards,
> emi
> _______________________________________________
> List info: http://lists.roundcube.net/dev/
>
_______________________________________________
List info: http://lists.roundcube.net/dev/
The nb_NO translation has been updated and is now complete with all
current strings.
--
Best regards,
Odd Henriksen
RoundCube user
--- 8< --- detachments --- 8< ---
The following attachments have been detached and are available for viewing.
http://detached.gigo.com/rc/Zr/jWfbngRu/labels.inchttp://detached.gigo.com/rc/Zr/jWfbngRu/messages.inc
Only click these links if you trust the sender, as well as this message.
--- 8< --- detachments --- 8< ---
_______________________________________________
List info: http://lists.roundcube.net/dev/
Here is the japanese updated translation.
---
Taka
--- 8< --- detachments --- 8< ---
The following attachments have been detached and are available for viewing.
http://detached.gigo.com/rc/XD/csjvKmhN/japanese.tar.gz
Only click these links if you trust the sender, as well as this message.
--- 8< --- detachments --- 8< ---
_______________________________________________
List info: http://lists.roundcube.net/dev/
Hi,
I would like to get involved with RoundCube development and thought I would
try to add this feature: http://trac.roundcube.net/ticket/1486636
Before I begin, I would like to check if this feature is actually desirable
to the dev team?
My initial thought on how to implement this would be:
Add three new config settings - ban_ip_enabled, ban_ip_threshold,
ban_ip_length
Add a new SQL table (banned_ips) with three fields - "ip",
"failed_login_count" and "expiry_time"
Make two modifications to program/include/rcmail.php:
~ line 613: after a failed login attempt failed_login_count is
incremented for this IP, and the expiry_time is set to (now + ban_ip_length)
~ line 551: before checking if the user/hostname is valid, check that
'SELECT count(banned_ip) FROM banned_ips where IP=$remote_ip and
failed_login_count > $ban_ip_threshold and expiry_time > NOW()' returns 0
ban_ip_enabled would be checked before performing either of the checks
above.
I would appreciate comments/suggestions on this approach. Also, I am not
quite sure of the best way to clear out the expired entries from the
banned_ips table. Is there some internal RC mechanism for performing tasks
(in this case, issuing a SQL query to delete old entries) at specified
intervals?
Cheers,
Mike
_______________________________________________
List info: http://lists.roundcube.net/dev/
Hi,
I’ve attached a revised Swedish localization of labels.inc and
messages.inc. We corrected some typos and implemented terminology
changes for the new features in roundcube based on user feed-back.
Regards,
Jonas Nasholm
Bitfuse Network
--- 8< --- detachments --- 8< ---
The following attachments have been detached and are available for viewing.
http://detached.gigo.com/rc/Ry/YmjZyGYg/sv_SE.zip
Only click these links if you trust the sender, as well as this message.
--- 8< --- detachments --- 8< ---
_______________________________________________
List info: http://lists.roundcube.net/dev/
Hello guys, here is Tiago from Red5 Project.
What you think about making a roundcube webconference module? I can
provide all the needed skills for you!
Regards,
Tiago
Red5 Team
_______________________________________________
List info: http://lists.roundcube.net/dev/