• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

access to event handlers within modules?

R

revolution

Guest
i'm interested in creating plesk modules. i've looked through the plesk sdk and module documentation and can't find the answer to this, but i'm assuming it's possible because i imagine software such as the 4psa software does this.

does anybody know if there's a way to "register" event handlers with one's module that don't show in the event handlers area of the server administration page? things could go very wrong if an admin removed or modified an event handler that the module had put there. the idea is the admin shouldn't be able to see the event handlers there. they should be forced to either remove the entire module or not mess the parts of it, such as the event handlers.

or maybe there's some other method within modules? some form of hooks one can use?

thanks.
 
Back
Top