• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question How to control when a created Event Handler is called?

FreeUserName

New Pleskian
It seems that created event handlers are called after the event occurs.

Coming from:

https://docs.plesk.com/en-US/12.5/a...t-tracking/adding-event-handlers-linux.59206/

E.g. when I use the example 'customer account creation' event the bash script test-handler.sh is called after the client has been created what makes perfect sense here. But let's say I would like to perform a task before the 'Physical hosting deleted' event actually does its task? E.g. unmount a folder pointing to an NFS in the users httpdocs/.

In addition is there an overview of when events are called and in which order? E.g. Domain created > Physical hosting created > Event N.
 
Last edited:
The current behaviour is following - event handlers are started in selected priority order only after the event occurs.
 
Thanks Igor. I expected that. In that case; I searched the Plesk Administrator's Guide about Event Tracking / Handlers but I couldn't find the order of steps taken. Is there such an overview?

Let's say I like to unmount a directory mounted in httpdocs when I delete a domain. I found out that this is at least associated in the end with the event 'Physical hosting deleted'. What is the order of steps taken by Plesk? Is it for instance a sequence of different events? E.g.:

This is an assumption for illustration:
1) Domain status updated (e.g. to first suspend the domain before delete)
2) {Some process in between}
3) Domain deleted
4) {Some other process in between}
5) Physical hosting deleted

In this particuar case I'm trying to find the event just before Plesk will delete the domain directory (/var/www/vhosts/domain.ext/) where I can hook my unmout action on.

Any ideas or know where I can find the order of steps taken by Plesk for domain create / delete?
 
Back
Top