• 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!
  • 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.

Plesk 11 API backward compatibility?

JP Kelly

Regular Pleskian
I have created event actions which work in Plesk 10 For example when a new client is created the following command is run:
/usr/sbin/clientcreated ${NEW_LOGIN_NAME}

Will this still work in Plesk 11? Specifically will the parameter ${NEW_LOGIN_NAME} still work/be available?

Since the documentation for Plesk 11 new features states "Software Development Kit for writing extensions. Adding new functionality to Panel has never been so clear. Use the new SDK (the replacement of former Modules API) to learn how to extend Panel to meet your unique needs."

If this is a "replacement of former Modules API" does that mean the former Modules API will not work in Plesk 11?
 
This handler is described in Administrator's Guide for Plesk 11 at least.
 
Back
Top