• Resolved etalented

    (@etalented)


    Hi- Im using this for theme update.
    I maybe not using it as designed- I have the plugin hosted on the same site where I am trying to update the theme. The plugin picks up the new version available from GitLab OK, and I can Update my theme- but I get the Update Failed: Download Failed. Service Unavailable error when trying to update the Theme.
    Not sure how to debug this on the server side TBH.
    Any ideas?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Alexandre Froger

    (@frogerme)

    Hello @etalented!
    Your intuition was right: WP PUS cannot play the role of server and client at the same time: When updates are triggered on a WordPress install, a hidden file .maintenance is created, and all access to that WordPress install is blocked. Then in your case a call to that same install is made reflectively, and it lands on, well, a locked WordPress install under maintenance, and fails.

    To use it as designed, there should be both a client and a server on separate installs. The easiest, simplest and fastest way to set it up is with a subdomain or subfolder with a WordPress install dedicated to WP PUS, separated from the client site where the package (theme or plugin) is installed.

    As for debugging, there is an extensive API, functions and filters at the disposal of developers. It can be quite the learning curve, but it can be really flexible and powerful.

    Happy coding, and would you have more questions and/or bugs to report, please feel free to follow up on github!

    Plugin Author Alexandre Froger

    (@frogerme)

    BTW, closing the support topic here, marked as resolved.

    Thread Starter etalented

    (@etalented)

    Thanks @frogerme! I will setup a separate subdomain install as you suggest…which in the end I can use for all theme & plugin deployments so I dont mind doing that ??

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Theme Update Failed- Service Unavailable’ is closed to new replies.