Facebook
Twitter-
Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring. We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design. If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
-
Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations. -
The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
Service plan changes
- Thread starter Chris1
- Start date
Chris1
Regular Pleskian
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.
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
Regular Pleskian
@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?
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?
abdi
Platinum Pleskian
You guys removed the subscription lock feature ...This where it used to come in handy ...
https://kb.odin.com/en/9141
What do you mean exactly? Could you please clarify?
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.
Similar threads
