• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

Service plan changes

Chris1

Regular Pleskian
Hello,

I'd like to change the default PHP version in my service plans without affecting subscriptions already assigned to these service plans. How can I do this?

It only allows me to apply and sync the changes to all attached subscriptions.
 
Oh ok, that's quite unfortunate. I think it's a little strange, Plesk should consider adding this feature. It makes keeping up to date with default php versions difficult.

For example, lets say you have PHP 5.6 as the latest version on your server. Then PHP 7 comes out and becomes stable enough, you would want PHP 7 as the default PHP on new accounts. It would be bad business practice to change and sync everyone else that was already on PHP 5.6.
 
Last edited:
@Chris1 ,
If you check option "Hosting management permission" in service plan, than php version will not be synced to domains on future service plan's updates (the same for other hosting settings), but it will be propagated during domain creation.
A kind of "default settings", but not exactly.
 
@dash

Ahhh I think I understand. So you if you provide the "Hosting Management" permission in service plans, and if the client then alters any settings within the "Hosting Settings" page then it wont be considered to be "altered" and locked/not synced with the service plan.

This then means that if we were to change the default PHP version then all existing customers will retain their PHP version but all new accounts will have the new default PHP version?
 
In previous versions (10) we used to LOCK subscriptions against any changes made from there respective service plans modifications. ALL locked subscriptions were NOT updated or synced with the new changes ...(which is what he wants)
 
In previous versions (10) we used to LOCK subscriptions against any changes made from there respective service plans modifications. ALL locked subscriptions were NOT updated or synced with the new changes ...(which is what he wants)
On Plesk 12.5 you can click "Customize" for subscription and "Apply & Lock" without any modifications. Subscription will be locked. After that you can change something in corresponding Service Plan (PHP handler, for instance) and sync it. PHP handler will not be changed for subscription.
Looks like I was wrong previously and you can use this scenario. But you should check it for your goals first.
 
Yes, that's exactly what I thought and expected ...
However your response made me think that this feature was removed and my bad too, didn't bother verifying from my test server ...
 
Back
Top