Skip to content

Barkat Husain

My feedback

5 results found

  1. 8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Barkat Husain supported this idea  · 
  2. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Barkat Husain shared this idea  · 
  3. 5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Barkat Husain shared this idea  · 
  4. 411 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Barkat Husain commented  · 

    It’s shocking that this still hasn’t been addressed—especially since users were requesting it as far back as 2016.

    Most server setups allow multiple PHP-FPM versions to run simultaneously, with Nginx configurations assigning specific versions per site. Implementing this is a basic feature, not a technical hurdle, yet Cloudways has ignored it for nearly nine years. That’s inexcusable.

    Once again, I’ve hit this roadblock today. Cloudways, this is unacceptable.

    PHP-FPM inherently supports multiple versions, so why doesn’t Cloudways? A proper solution would allow users to:

    1) Enable multiple PHP versions at the server level (with a default).

    2) Assign the required version per application.

    Even budget hosts offer this flexibility. For a premium managed service to lack such a critical feature—without even acknowledging it—is baffling.

    This Isn’t Just a Request—It’s a Necessity
    We manage 100+ applications, and upgrading PHP globally isn’t an option. Testing and fixing every app simultaneously is impossible. Per-application PHP version control is mandatory. If this isn’t implemented, we’ll have no choice but to migrate to a platform that actually meets modern standards.

    When I reached to cloudways support, their "solution" was to add another server. It’s lazy, costly, and proves how out of touch Cloudways is with real-world needs.

    Falling behind like this is unacceptable in our rapidly evolving industry. Cloudways, when will you finally listen to your users?

    Barkat Husain supported this idea  · 
  5. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Barkat Husain commented  · 

    The latest stable version of PHP is PHP 8.4.8, released on June 5, 2025. It is a bug fix release for the 8.4 series.

    The most recent major version is PHP 8.4, released in November 2024.

    Still PHP 8.4 is not available in cloudways, Magento 2 is supporting it, client is asking for support in PHP 8.4 , so do we have wait till our client go away due to this cloudways lazyness?

    Barkat Husain supported this idea  ·