At line 1 changed one line |
This type of User Event allows triggering a specific event by multiple user accounts that share same VFS folder. Takes two different user Event type, a sender and a recipient. The sender will trigger the Event configured on the recipient account, in opposite to regular Events, that are triggered by the same user these are configured on.\\ |
!!!1. Reverse Event configurations\\ |
\\ |
This type of User Event allows triggering a specific event by multiple user accounts that share the same VFS folder. Takes two different user Event types, a __sender__ and a __recipient__. The sender will trigger the Event(configured on the recipient account), in opposite to regular Events, that are triggered by the same user |
these are configured on.\\ |
At line 3 changed one line |
[{Image src='general_settings_events.jpg' width='1920' height='..' align='left' style='..' class='..' }]\\ |
[{Image src='general_settings_events.jpg' width='1650' height='..' align='left' style='..' class='..' }]\\ |
At line 5 changed 2 lines |
Now, in the User Manager this takes two different types of events. You need an event to accept reverse notifications,\\ |
[{Image src='img.jpg' width='..' height='..' align='left|center|right' style='..' class='..' }] |
Then in the User Manager, this takes two different types of events. You need an event to accept reverse notifications,\\ |
[{Image src='recv_reverse_user.jpg' width='1650' height='..' align='left' style='..' class='..' }]\\ |
At line 10 changed one line |
[{Image src='img.jpg' width='..' height='..' align='left|center|right' style='..' class='..' }] |
[{Image src='send_recv_user.jpg' width='1650' height='..' align='left' style='..' class='..' }] |
At line 13 changed 3 lines |
Otherwise the send notifications has to go on all users who might cause a send to occur.... And the reverse needs to be on all users who you want to accept reverse notifications.\\ |
The send event notification is done via the Send Email event type like in screenshot #1.\\ |
[attachments|screenshot1.png]\\ |
Otherwise, the send notifications have to go to all users who might cause a send to occur.... The reverse needs to be on all users who you want to accept reverse notifications.\\ |
At line 17 changed 2 lines |
Make sure the from, to,cc,bcc are all empty. The receive event notifications is like screenshot #2.\\ |
[attachments|screenshot2.png]\\ |
Remember that reverse notifications take a bit more time and CPU power as all users have to be checked over to see if they have a VFS that matches. But if configured right, reverse notifications will then happen.\\ |
At line 20 changed 6 lines |
Keep in mind reverse notifications take a bit more time and CPU power as all users have to be checked over to see if they have a VFS that matches. But if configured right, reverse notifications will then happen.\\ |
|
Now, in the User Manager this takes two different types of events. You need an event to accept reverse notifications, and you need an event to send out reverse notifications. You can put both of these on your default user if you like and they then apply to everyone who has not overridden that config.\\ |
Otherwise the send notifications has to go on all users who might cause a send to occur.... And the reverse needs to be on all users who you want to accept reverse notifications.\\ |
The send event notification is done via the Send Email event type like in screenshot #1.\\ |
[attachments|screenshot1.png]\\ |
!!!2. User subscribe for reverse notifications\\ |
At line 27 changed 2 lines |
Make sure the from, to,cc,bcc are all empty. The receive event notifications is like screenshot #2.\\ |
[attachments|screenshot2.png]\\ |
__!!!Only for real users, it does not work for users authenticated through a plugin!!!__\\ |
It allows the CrushFTP user to subscribe for reverse notifications through the web interface.\\ |
At line 30 changed one line |
Keep in mind reverse notifications take a bit more time and CPU power as all users have to be checked over to see if they have a VFS that matches. But if configured right, reverse notifications will then happen.\\ |
[attachments|user_subscribe.png]\\ |
[attachments|user_subscribe_panel.png]\\ |
\\ |
!!__Required configurations:__\\ |
\\ |
__1.__ Enable reverse events on Preferences->General Settings page.\\ |
\\ |
[{Image src='general_settings_events.jpg' width='1650' height='..' align='left' style='..' class='..' }]\\ |
\\ |
__2.__ Create a "Send Reverse Notification" event type. Create an event in User Manage -> Selected User. Use the action: "__Send Reverse Notifications__."\\ |
[attachments|subscribe_send_reverse.png]\\ |
\\ |
Version __11.2.1 Build 21+__ allows you to send notifications exclusively to users within the groups selected.\\ |
\\ |
__3.__ Create a template event for the subscription. Create an event in User Manage -> Selected User. Then select the action: "__Subscribe reverse notification event template__".\\ |
\\ |
[attachments|subscribe_template_event.png]\\ |
\\ |
__4.__ Add the __"Subscribe To Events"__ WebInterface button. Ensure you enable the "__Context Menu__" as Manu Bar is not supported for this feature.\\ |
\\ |
[attachments|subscribe_webinterface_button.png]\\ |
\\ |
__5.__ Enable the subscribe for the user:\\ |
\\ |
[attachments|susbcribe_user_flag.png]\\ |
\\ |
!!__Manage Subscribed Events related configurations:__\\ |
\\ |
Version __11.2.1 Build 21+__ allows CrushFTP user to manage subscribed events.\\ |
\\ |
[attachments|ReverseEvents/manage_subscribe_events.png]\\ |
\\ |
__6.__ Add the __"Manage Subscribed Events"__ WebInterface button. Ensure you enable the "__Manu Bar__" and not the "Context Menu".\\ |
[attachments|manage_subscribed_events_button.png]\\ |
\\ |
__7.__ Enable the __"Show subscribed events icon in the file listing"__ web interface customization to see the subscribed event numbers next to the folder icon.\\ |
\\ |
[attachments|subscribed_events_icons.png]\\ |
\\ |
[attachments|subsribed_events_icons_customization.png]\\ |
\\ |
__8.__ Activate __"reverse_events_skip_sender"__ config on __"perfs.XML"__ file. When set to true, the reverse event will bypass the sender user(the individual who triggered the event)\\ |
Open the "prefs.XML" file (placed in the CrushFTP install folder) and change the "reverse_events_skip_sender" tag value to true.\\ |
{{{ |
<reverse_events_skip_sender>true</reverse_events_skip_sender> |
}}}\\ |
\\ |