{"id":62,"date":"2009-12-21T14:19:34","date_gmt":"2009-12-21T14:19:34","guid":{"rendered":"http:\/\/blogs.wp.stage.cpanel.net\/2009\/12\/known_integration_issues_inside_of_1125\/"},"modified":"2009-12-21T14:19:34","modified_gmt":"2009-12-21T14:19:34","slug":"known_integration_issues_inside_of_1125","status":"publish","type":"post","link":"https:\/\/devel.www.cpanel.net\/blog\/products\/known_integration_issues_inside_of_1125\/","title":{"rendered":"Known Integration Issues inside of 11.25"},"content":{"rendered":"

As most of you probably know, we released 11.25 to our RELEASE branch this week.\u00a0 This is a major<\/strong> change to cPanel\/WHM which presents some issues with integration.\u00a0 I have been trying to track as many integration support requests as possible so that I can get an idea of what common issues have arisen.\u00a0 Here is a summary of the issues and what we are doing about them.<\/p>\n

Hooks Do Not Execute<\/strong>
\nWe have added a feature to 11.25.0 that keeps track of what hooks are in use.\u00a0 This new mechanism greatly improves speed within cPanel\/WHM as it no longer has to check to see if a hook exists every time an API call is made.\u00a0 Unfortunately the hooks.db<\/em> file was unreadable by any user other than root.\u00a0 If you notice that hooks are not executing on your server, please run chmod 644 \/var\/cpanel\/hooks.db<\/em>.\u00a0 This issue will be fixed in the next update.<\/p>\n

The setresellerlimits XML API call does not work with certain reseller accounts.<\/strong>
\nThe setresellerlimits<\/em> XML API call does not work with reseller accounts that did not previously have reseller limits.\u00a0 This is because the hash in \/var\/cpanel\/reseller-limits.yaml<\/em> is not being properly created.\u00a0 This issue will be resolved in the next update.<\/p>\n

API call changes that affect hook\/CustomEventHandlers<\/strong>
\nWe are moving toward making most of cPanel use API2 calls for executing events.\u00a0 This provides a much more flexible system.\u00a0 However, a major drawback to doing so is that some hooks will break.\u00a0 For example, we changed Email::addpop<\/em> to an API2 call in the interface.\u00a0 When the addpop hook is executed, it is passed a hash rather than an array, making the hook unusable.\u00a0 We have updated the following interfaces to use API2:<\/p>\n