Provide ability to encode extensions before vertification and publishing
Starting from Plesk Onyx 17.8, support of the extensions protected by ionCube was stopped and now it's possible to get extension encoded only on Plesk RnD side and only when publishing it.
This way Plesk reseller cannot test it on clients' servers without exposing a source code.
1
vote
Plesk Tech Support
shared this idea
