eworksmedia
New Pleskian
Why is it not possible to install any additional PHP versions as an Apache module? You're a control panel provider, not an industry standards creator. Nobody cares what Odin thinks about module VS cgi VS fastcgi, nobody. If Odin personally doesn't want to run their websites as an apache module, good for them. Plesk, a control panel, should allow its users the ability to do whatever they please considering its their website(s), not Odin's website. Does Odin support the individual websites on every Plesk customer's server? No. Does Odin make the business decisions for the end-users of Plesk or the websites they host? No. However, they've already made the business decision for all its users by not even allowing you to install PHP as an apache module manually and register it with Plesk. When you try, you get this junk "Wrong syntax for command's '-type' parameter. 'module' does not match the pattern '/^(cgi|fastcgi|fpm)$/'."
This is the same problem you had a couple versions ago when you forced all new Subscriptions inside Plesk to 301 redirect with "www" or without "www" on creation until you released a patch that removed that stupid forced functionality. Again, it's the website's choice what to do in that situation and you finally figured that out. Here we are again, forcing your users to use what you want, rather than empowering them to use what they want.
How do we work around this stupidity so we can continue to operate a business?
This is the same problem you had a couple versions ago when you forced all new Subscriptions inside Plesk to 301 redirect with "www" or without "www" on creation until you released a patch that removed that stupid forced functionality. Again, it's the website's choice what to do in that situation and you finally figured that out. Here we are again, forcing your users to use what you want, rather than empowering them to use what they want.
How do we work around this stupidity so we can continue to operate a business?