Skip to content

Settings and activity

2 results found

  1. 14 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)
    under review  ·  Ani King responded

    Thank you so much for your feedback regarding sftp users within Managed WordPress. While we currently have sftp/ssh users and permissions set up with security in mind, I understand that may not be allowing you to accomplish what you need, and we are actively reviewing ways to improve upon ways that you and others access your sites.

    An error occurred while saving the comment
    Steve Simons commented  · 

    Maybe with the exception of the little 1 or couple seat site packages, MWP accounts ideally will have lots of sites, therefore multiple administrative/developers needing access to those various sites, the single credential solution as now is completely inadequate and only addresses SFTP/SSH.

    Think bigger. The ideal platform with multiple users needing access to multiple sites, isn't just an SFTP/SSH issue. A central MWP account list of users, with access options per site per user granting access (logs, configuration, copy to staging, ssh, sftp, etc.). As a design firm, agency, or enterprise, it's not going to be unique users per site, it will usually be many users with access to multiple sites.

    Ideally we could setup a user (admin/developer), each would have a set of credentials, and a list of sites/functions they are permitted.

  2. 13 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)
    planned  ·  Ani King responded

    We are currently looking at ways to improve upon domain changes and appreciate you sharing your feedback about how this impacts you so we can make sure it’s considered as we go forward.

    An error occurred while saving the comment
    Steve Simons commented  · 

    This is a major limitation.

    It's a really big deal especially if you're wanting to migrate existing sites. There is no way you can migrate an existing site to MWP without downtime, something that is almost never a limitation anywhere else (example LW Cloud Sites).

    It makes it impossible to just edit your hosts file and truly test a site, as many licenses (fonts, plugins, chat services, etc.) are keyed to the site name and other integrations (SSO, etc.) expect a referrer from or are configured to redirect to the real site name. A testing url/sitename simply isn't a viable solution for test many sites anymore.

    I'm guessing this limitation might be because the SSL certificate issuing process requires an http challenge, which isn't available to the platform until the dns is updated. Provide support for DNS challenges, or option to upload our own SSL certificate (which would be another stand-alone Vote Yes item), or even using temporarily a self-signed certificate would be better than the current solution.

    Steve Simons supported this idea  ·