mmm...
I just had an idea: instead of having an email field, a notes field.
If you want, put email in it, or anything.
But if you want to have MORE fields, you can.
Just use as syntax
field1=value1
field2=value2
email=my@address.com
hair-color=brown
So, in the template you can
{.set|notes|%user-notes%.}
{.from table|notes|email.}
Very GOOOD IDEA!!!
A "note" field would be very useful to store additional details about a user (e.g. department, phone number, etc.) and makes HFS very flexible!
About the sending of email, i prefer it to be demanded to an external utility through {.exec.}
Folder subscription is a problem: how to know when there's a new file in a real folder?
May idea was to sync it with the "Flag" event, but I of course it works only if someone uploads the files using HFS. New files added directly into the real folder would not be seen by HFS
What about having it in the "events script"?
Something like:
- associate a group to it
- each time a new file is uploaded, get the list of members of this group and send an email to them
To use an external utility to send emails it's ok ;-)
memberof macro is coming
Many thanks !
Question: is there a way to know if the client (e.g. the browser) is running on Windows? Because in this case, can be a good idea to call outlook to send an email (please don't kill me: my users will like it).