Skip to main content

How to manually downgrade from WHM v. 74?

Comments

8 comments

  • cPanelMichael
    Hello @postcd, After you upgrade to a new major version of cPanel & WHM, you cannot downgrade to a previous major version of cPanel & WHM. This is documented at: Update Preferences - Version 74 Documentation - cPanel Documentation The best approach to downgrade would be to setup a new server running an earlier version (use version 70 if you take this approach since it's the
    0
  • stormy
    Is there no chance that the XML API could be brought back into v74?
    0
  • cPanelMichael
    Is there no chance that the XML API could be brought back into v74?

    Hello @stormy, That's correct. It's been deprecated since cPanel & WHM version 66, and was removed from the product in version 74: cPanel Deprecation Plan - cPanel Knowledge Base - cPanel Documentation Here's a link to the March 2017 Development Update noting it's planned removal: March Development Update | cPanel Blog [QUOTE]
    • XML-like output of APIs The XML-like output of our API (often called the XML API) is already officially deprecated, and cPanel & WHM Version 70 will be the last version to support this output. Integrators and API users will want to begin switching to use the JSON output of the API now. The XLM-like format has long caused problems for integrators and developers because it is not valid XML, and we find that removing it completely will help reduce that.

    Thank you.
    0
  • postcd
    Setting up a new server just to bring working XML API feature back is NOT a good solution (even it is solution, thank you for that) because of a downtime caused by the migration. Instead you should create a tool that allows WHM downgrade or create tutorial that helps to replace JSON API by XML API for those that want it. I think it is very bad when developer (cpanel) cease esential features that people relying and where adapting to changes cost them money and trust of their customers and also wasting money finding a programmer to rework API scripts. I do not read your announcement that are burried deep in your websites. I should have been prompted or given choice to stay with old API or at least somehow return to it instead of being adviced to install new server and do difficult migration causing downtimes.
    0
  • rpvw
    I think it is very bad when developer (cpanel) cease esential features that people relying and where adapting to changes cost them money and trust of their customers and also wasting money finding a programmer to rework API scripts.

    cPanel did give you over 12 months notice of the depreciation and removal. cPanel can't be expected to keep everything the same forever to suit your reluctance to embrace progress.
    I do not read your announcement that are burried deep in your websites.

    The announcement was certainly NOT buried, and I believe was available vis RSS ( cPanel Mailing List | cPanel, Inc. ) which you should probably be subscribed to as a responsible web host operating cPanel anyway. I don't often come to the defence of cPanel, but in this case, I am sorry to say that I think the oversight rests squarely with you. Apart from keeping an eye on the forums which are full of interesting comments, ideas and, most importantly advice, other resources include RSS feeds of interest that a responsible web host might benefit from :
    0
  • JayFromEpic
    I honestly would just recommend updating your WHMCS installation. If you are using the latest version, then it should not be a problem. It would be much cheaper to pay WHMCS I believe $35 for an integration into your existing website and manually include any customization versus trying to go through dangerous path of setting up a new server and migrating websites back.
    0
  • Tarak Nath
    Yes agree with @JayFromEpic, I think also this would be hassle free solution right now.
    0
  • postcd
    Thank you all for the replies. I got help on WHMCS forum, got updated cpanel module. Maybe it also flying somewhere over the internet.
    0

Please sign in to leave a comment.