Plugin dev documentation needed

[lucas-net-pl]

No I develop custom plugin to change passwords.
Due to my system requrements, i need meake two functions:

1. I need to be able display custom messages if new password not valid
2. And most importatnt! After succesfuly password change, i need to logout user and display some additional informations

Now after two days of serachin in code and google, i decide to write to You for help, because i cant found any documentation to plugin development.

THX

[raphaelh]

Thanks for your commit! Could you add some documentation on how to write a plugin to let the user change his/her password?

[lucas-net-pl]

Hello. I cant write full doc, because, i wrote plugin based on example stored in:
https://github.com/RainLoop/rainloop-webmail/tree/master/plugins/change-password-example

I'll search more on code and google to add functionality described in topic, but not found any. so i wrote this topic.
Some plugin write without this function are simply based on example code.

To change password i simply exec system bash script to do the rest.

Due to specification of mail mail system, the password change are little delayed, so after change, rainloop cant access mailbox, so simplest solution is to logout this user for few seconds.
Ant this fuction i cant find in any place. Rest are simple.

[IDoProgramming]

Hello,

any hope for documentation?

I see that there is still no documentation at https://www.rainloop.net/docs/plugins/

I run into several questions about the process of displaying error messages in a proper way that would be portable between current and future new versions. As I'm trying to integrate rainloop webmail interface with custom server infrastructure and the way it handles error messaging (which somewhat differs from examples from rainloop repository and above example by @lucas-net-pl ). So far I have no reasons to believe that any results of code analysis that would be performed on existing codebase may be used to develop such plugin. So is the lack of documentation caused by just a lack of time and volunteers? Or the topic of plugin development may be the subject of rapid changes between branches/versions making the whole process of writing such documentation not worth the whole effort due to possible changes in code architecture? If it's the only matter of lack of manpower - what would be the proper way of doing so?