Facebook
Twitter@TorbHo
This statement
I can fully agree with.
This statement
I feel ambivalent about.
Most loyal customers should be defined as "customers that stay with Plesk".
The "many users" that you talk about are "users" that - often - do not have a fair appreciation of the material and immaterial value of Plesk.
To be honest, I do not care that Plesk loses customers that feel better with an alternative - those should do what feels good.
To be honest, I do care about some customers that complain, switch panels, then complain about the new panel on the corresponding forum, then revert to Plesk and start complaining again and so on.
In essence, I feel ambivalent about those hosting panel users that are never satisfied.
One might not ask Plesk to do anything for that particular (small) set of "users" that will never be satisfied - it is simply impossible to keep them happy.
However, I do not feel ambivalent about those hosting panel users that only need a trip to another alternative to learn the value of Plesk.
They are welcome to make that trip and they are welcome when they return to Plesk.
Sure, Plesk might do something about the latter group of users - a bit of better communication would prevent a lot of customers making that trip.
So, yes, to some extent you are right ........ and I still feel ambivalent about it ;-)
This statement
I really do not understand.
If I am not mistaken, this is exactly the case
- specific updates are forced remotely as a quick patch, if and only if they are needed desperately, (and)
- minor version updates can be installed automatically or can be installed at the sole discretion of the Plesk admin, (and)
- major version updates can only be installed at the sole discreation of the Plesk admin
and that would imply that minor and major version updates, buggy or not, can be held back if desired.
Do you not have those options?!?
If that would be the case for you, then I would be really surprised.
UPDATE
One of the statements in one of your other posts clarifies that you are looking for a distinction between "delayed" and "stable" updates.
In essence, one can still achieve that by having minor and major updates only at the sole discretion of the Plesk admin - it is virtually the same or even better.
In addition, @learning_curve correctly states that you can use the CLI utility.
As a matter of fact, in most (but not all!) cases, one can even use the CLI utility to roll-back Plesk versions without issues.
In my humble opinion, you are focused too much on definitions that are barely relevant nowadays.
@TorbHo , remember that you - essentially - stated something of the nature that some or a lot of the micro-updates are buggy.
That makes the relevance of a distinction between "delayed" and "stable" updates almost obsolete - in a sense, there are no stable updates anymore!
The "old" development situation has been replaced by a development eco-environment that is dynamically changing.
Sure, changing with a lot of hickups.
Nevertheless, changing in such a way that update-upon-update will follow, it is inevitable.
Stated differently, no need anymore for the old toold in old Plesk, only need for (a) version control (via CLI) and (b) control over automated updates.
Kind regards....
This statement
I can fully agree with.
This statement
I feel ambivalent about.
Most loyal customers should be defined as "customers that stay with Plesk".
The "many users" that you talk about are "users" that - often - do not have a fair appreciation of the material and immaterial value of Plesk.
To be honest, I do not care that Plesk loses customers that feel better with an alternative - those should do what feels good.
To be honest, I do care about some customers that complain, switch panels, then complain about the new panel on the corresponding forum, then revert to Plesk and start complaining again and so on.
In essence, I feel ambivalent about those hosting panel users that are never satisfied.
One might not ask Plesk to do anything for that particular (small) set of "users" that will never be satisfied - it is simply impossible to keep them happy.
However, I do not feel ambivalent about those hosting panel users that only need a trip to another alternative to learn the value of Plesk.
They are welcome to make that trip and they are welcome when they return to Plesk.
Sure, Plesk might do something about the latter group of users - a bit of better communication would prevent a lot of customers making that trip.
So, yes, to some extent you are right ........ and I still feel ambivalent about it ;-)
This statement
I really do not understand.
If I am not mistaken, this is exactly the case
- specific updates are forced remotely as a quick patch, if and only if they are needed desperately, (and)
- minor version updates can be installed automatically or can be installed at the sole discretion of the Plesk admin, (and)
- major version updates can only be installed at the sole discreation of the Plesk admin
and that would imply that minor and major version updates, buggy or not, can be held back if desired.
Do you not have those options?!?
If that would be the case for you, then I would be really surprised.
UPDATE
One of the statements in one of your other posts clarifies that you are looking for a distinction between "delayed" and "stable" updates.
In essence, one can still achieve that by having minor and major updates only at the sole discretion of the Plesk admin - it is virtually the same or even better.
In addition, @learning_curve correctly states that you can use the CLI utility.
As a matter of fact, in most (but not all!) cases, one can even use the CLI utility to roll-back Plesk versions without issues.
In my humble opinion, you are focused too much on definitions that are barely relevant nowadays.
@TorbHo , remember that you - essentially - stated something of the nature that some or a lot of the micro-updates are buggy.
That makes the relevance of a distinction between "delayed" and "stable" updates almost obsolete - in a sense, there are no stable updates anymore!
The "old" development situation has been replaced by a development eco-environment that is dynamically changing.
Sure, changing with a lot of hickups.
Nevertheless, changing in such a way that update-upon-update will follow, it is inevitable.
Stated differently, no need anymore for the old toold in old Plesk, only need for (a) version control (via CLI) and (b) control over automated updates.
Kind regards....
Last edited:
