cPanel & WHM Version 98 has been released, and brings a slew of great updates. Take a look at what is included, and then upgrade today!

Link to the same API Shell page from all other versions of that same function

Michael-IDA shared this idea 5 years ago
Open Discussion

From ticket 7167791:


Suggestion #03:


=== API Shell for cPanel for 11.52 EDGE builds

https://documentation.cpanel.net/display/ALD/API+Shell+for+cPanel


"This documentation is for cPanel & WHM 11.52 EDGE builds. The "RELEASE" version of our documentation can be found in the 11.50 Documentation space."


"11.50 Documentation" links to the generic page: https://documentation.cpanel.net/display/1150Docs


=== API Shell for cPanel for cPanel & WHM version 11.50

https://documentation.cpanel.net/display/1150Docs/API+Shell+for+cPanel


Assuming the only difference between 11.52 (ALD?) documentation and 11.50 documentation is the pathing difference in the URL of "/ALD/" and "/1150Docs/".


Why not link to the actual API Shell "11.50 Documentation" page on the "11.52 EDGE builds" page instead of linking to the generic 11.50 home page? It would require a very simple template change to create the URL rewrite.


In addition, if the pathing is as easily identified for each of the LTS, STABLE, RELEASE, CURRENT, or EDGE releases found on:


WHM » Home » Server Configuration » Update Preferences


Providing all of the associated links should be done.


An Example:


###

This documentation is for cPanel & WHM 11.52 EDGE builds. Other tier corresponding versions of this documentation are:


- LTS => 11.50 Documentation

- STABLE => 11.50 Documentation

- RELEASE => 11.50 Documentation

- CURRENT => 11.52 Documentation

- EDGE => 11.51 Documentation

###


"RELEASE => 11.50 Documentation" links to:

https://documentation.cpanel.net/display/1150Docs/API+Shell+for+cPanel


with whatever is appropriate for the other tiers.


Rewrite however looks good, but I do suggest listing every tier found on the Update Preferences page, even if it's a repeat of the exact page they are on or even if several tiers link to the same documentation page.


Reason #03:

This would save an enormous amount of people's time trying to find the exact same page for the version they are actually using. And should be very simple to do.

Best Answer
photo

Thank you so much for your feedback. With the way our system is currently set up, this would take a pretty significant amount of overhead. We definitely see the usefulness of this, though, so we'll keep it on our radar to try to incorporate in the future!

Replies (1)

photo
1

Thank you so much for your feedback. With the way our system is currently set up, this would take a pretty significant amount of overhead. We definitely see the usefulness of this, though, so we'll keep it on our radar to try to incorporate in the future!

Leave a Comment
 
Attach a file