How to manually downgrade from WHM v. 74?

[postcd]

I need to revert deprecation of the XML API. My application is using it and stopped working:

CPanel/WHM - WHMCS Documentation

So how can i manually return back deprecated function XML API? I have backup of the files from time this feature was there (i mean all server files backup, so i can selectively restore files), but i assume cPanel staff knows what exactly to do to activate it again or know steps to downgrade WHM, either one.

This deprecation is an issue, because my billling system plugins would have to be reworked, my website template, all modifications also reworked as new CMS version does not support my template, etc. I do not understand how it would hurt to keep deprecated XML api in place and working, only make it non-default.

If you tell me what needs to be replaced, i can stop cPanel service and replace certain files by old ones. I acknowledge i would do it on my risk and will do backup before.

Thank You

 

[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 LTS release), and then migrate the accounts to the server using WHM >> Transfer Tool.

Thank you.

 

[stormy]

Is there no chance that the XML API could be brought back into v74?

 

[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

• 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.

 

[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.

 

[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 ( http://blog.cpanel.net/feed/ ) and by their mailing list ( 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 :

http://atom.cpanel.net/changelog/cpanel-changelog.atom
http://news.cpanel.com/feed/
http://news.cpanel.com/category/security/feed/

I am so sorry if you feel hard done by, but we are all in the same situation, and most of us have already done something about addressing the issues. I was bought up with the principle that I don't deserve to own anything I can't look after. The reality of this is I either have to learn to look after and fix the things I have myself, or I have to be in a position to pay someone else to do it for me. Bottom line; if you're unwilling or not able to pay someone else, and you cant be bothered to learn how to do it yourself, you probably shouldn't own it (and this applies equally to running a web hosting company as much as anything else)

Frankly I applaud cPanel for any progress they make, and chastise them (as usual) for not making that progress fast enough !! and yes, I do understand the vast amount of testing (that often seems insufficient and inadequate anyway) that has to be made on a wholly too extensive variety of operating systems that they have to cover to compete in the market and retain some semblance of profitability and incentive to go to work in the morning. In the same breath, it makes perfect sense to consolidate, prune and discard as many areas of the code base as possible to lighten and simplify the development road-map.

This is (unusually for me) not intended to provoke a discussion, nor is it a intended as an unconditional statement of my approval of everything that cPanel does - but on the whole, they do a pretty good job most of the time

[/end-rant]

 

[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.

 

[Tarak Nath]

Yes agree with @JayFromEpic , I think also this would be hassle free solution right now.

 

[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.