{"id":75,"date":"2011-02-25T15:48:26","date_gmt":"2011-02-25T20:48:26","guid":{"rendered":"http:\/\/blogs.wp.stage.cpanel.net\/2011\/02\/cpanel_1130_6\/"},"modified":"2011-02-25T15:48:26","modified_gmt":"2011-02-25T20:48:26","slug":"cpanel_1130_6","status":"publish","type":"post","link":"https:\/\/devel.www.cpanel.net\/blog\/products\/cpanel_1130_6\/","title":{"rendered":"cPanel 11.30"},"content":{"rendered":"
The release of cPanel & WHM version 11.30 in EDGE is right around the corner. With this release we have made numerous changes, added a few features and fixed some bugs. Predominantly, these changes can be encompassed in a few bullet points:<\/p>\n
Though each of these changes may seem small when listed as bullet points, there are a few details that you, as someone who customizes or integrates with cPanel & WHM should be aware of.<\/p>\n
Update System<\/strong> Some parts of this change will have a major impact on developers.\u00a0 Most importantly, \/scripts will be relocated to \/usr\/local\/cpanel\/scripts.\u00a0 When this happens, we will attempt to migrate the data in \/scripts to \/usr\/local\/cpanel\/scripts and then backup \/scripts and symlink \/usr\/local\/cpanel\/scripts to \/scripts.\u00a0 There are a couple of scenarios where this will not happen:<\/p>\n In this scenario, an email should be sent to the user asking them to resolve the issue. The user should also be updated to the latest version of 11.28 (rather than 11.30).\u00a0 In a standard cPanel install, or even a heavily customized one, this should not be an issue.<\/p>\n Another major part of this change is the reworking of how RPMs are versioned with the product.\u00a0 Previously, an RPM has been tied to a specific tier. For example, exim may have a different version for EDGE and CURRENT.\u00a0 Now, the RPM version is tied to the version of the product. Thus,if you are running 11.30.3 in the EDGE tier or CURRENT tier, you will have the same version of exim. We will also be offering the ability to source RPMs from a custom repo. This means that, if you wish to provide your customer with your own version of ProFTPd or dovecot, it is now possible in a way that is supported (more on this in a future post).<\/p>\n Also, \/etc\/cpupdate.conf now uses a different format for determining the prescribed version. This file will break the update tier and update method into separate tiers.\u00a0 A valid cpupdate.conf will now look something like:<\/p>\n CPANEL=release Valid values for CPANEL are: stable, release, current, edge. Addition of Cpanel::PublicAPI<\/strong> Eventually, a full set of modules will be available to query all of our APIs via any method available.<\/p>\n Removal of Legacy Themes<\/strong> New API Calls & Hook<\/strong> xml-api: api2: Note: <\/strong>Documentation on these calls will be available once version 11.30 hits CURRENT.<\/p>\n Hook:
\nThe rewrite of the cPanel & WHM update system (or upcp) has been a major project of ours for quite some time now.\u00a0 There are numerous improvements in this version, including the addition of long term support, better logging and many other benefits for both users and developers.<\/p>\n\n
\nUPDATES=manual<\/p>\n
\nValid values for UPDATES are: automatic, manual, never.<\/p>\n
\ncPanel & WHM 11.30 contains the first version of Cpanel::PublicAPI, a perl module capable of querying APIs from a single interface.\u00a0 This module deprecates the old Cpanel::Accounting module and offers a few new pieces of functionality:<\/p>\n\n
\nIn cPanel & WHM 11.28, we dropped support for x, x2, bluelagoon and monsoon. Within the 11.30 release cycle, we will stop distributing them all together.\u00a0 If you develop a theme that is based off of one of these themes, we strongly suggest that you update to a theme using cPanel\u2019s API2.\u00a0 If you require guidance updating your themes, you can always contact us via our ticket system.<\/p>\n
\nWe have added a few new API calls within version 11.30, specifically:<\/p>\n
\nupdateconfig – This call allows you to set your preferred release tier.<\/p>\n
\nMysqlFE::adddb – Add a database
\nMysqlFE::adduser – Add a Mysql user
\nMysqlFE::adduserdb – Grant a user permission to access a DB
\nMysqlFE::addhost – Allow a new host to access Mysql
\nMysqlFE::deldb – Delete a database
\nMysqlFE::deluser – Delete a user
\nMysqlFE::delhost – Delete a host\u2019s access
\nMysqlFE::deluserdb – Remove a user\u2019s permission to access a database
\nEmail::delforwarder – Allow deletion of Email Forwarders
\nEmail::adddomainforward – Add a domain forwarder<\/p>\n
\nWe have now added a \u201cmodifyacct\u201d hook at \/usr\/local\/cpanel\/scripts\/postmodifyacct and \/usr\/local\/cpanel\/scripts\/premodifyacct. It will be passed all the new values for an account.<\/p>\n