Michael
My feedback
2 results found
-
11 votesMichael
supported this idea
·
An error occurred while saving the comment -
10 votes
Thank you for the ideas and for explaining specific cases.
Michael
supported this idea
·
This is a great idea, but I want to add on it and explain the issues and use cases.
If you need to have different versions of PHP for subdomains you cannot do it with PHP selector because it is user based on the whole domain account. So to make it work you have to first make the whole domain account and everything inheritable, then select the version of alt-php, and afterwards break the inheritance and change the php version for other subdomains, selecting ea versions. This is a terrible process and now we have a mixture of two different selectors.
I think the proper approach should be:
1. Modify PHP Selector to allow setting different alt-php versions for different subdomains
2. Do away with inheritance, it's just another unnecessary setting. It is enough to have a default PHP version to be used initially, and then the user can change it for each domain or subdomain
3. Most important! >>> Decouple MultiPHP manager from PHP Selector. Cant and should not use both on the same server. User decides if he wants one or the other FOR THE WHOLE SERVER. Then if you enable one the other is unavailable. This will also make the selection of the PHP version much easier. When selecting in MultiPHP manager, there is no need to see all the alt-php versions. When selecting in PHP selector, there is no need to see all the ea-php versions. Also will prevent issues due to mismatched selections.
Finally- the use case: why is it important to have different versions of PHP for the same user account? because when we want to upgrade the PHP version, we create for the client a beta site under the same domain and that is where we put all the migration and new features. We need to be able to do it without disrupting the live site.