{"id":14612,"date":"2025-06-12T08:32:13","date_gmt":"2025-06-12T14:32:13","guid":{"rendered":"https:\/\/www.supportpro.com\/blog\/?p=14612"},"modified":"2026-03-31T01:20:12","modified_gmt":"2026-03-31T07:20:12","slug":"wp-toolkit-issues-on-cpanel-110-126-110-128-whats-causing-it-and-how-to-fix-it","status":"publish","type":"post","link":"https:\/\/www.supportpro.com\/blog\/wp-toolkit-issues-on-cpanel-110-126-110-128-whats-causing-it-and-how-to-fix-it\/","title":{"rendered":"WP Toolkit Issues on cPanel 110.126 &amp; 110.128: What&#8217;s Causing It and How to Fix It"},"content":{"rendered":"\n<p>If you&#8217;re managing WordPress installations through <strong>WP Toolkit<\/strong> on cPanel, you may have noticed strange behavior or complete non-functionality after upgrading to certain cPanel versions. Specifically, users upgrading to versions 11.110.0.65, 11.126.0.21, or 11.128.0.11 have reported that WP Toolkit and other cPanel plugin functionalities are either broken or inaccessible.<\/p>\n\n\n\n<p>After some digging, the root cause appears to be the <strong>removal of a crucial directory<\/strong>:<br>\/usr\/local\/cpanel\/whostmgr\/addonfeatures<\/p>\n\n\n\n<p>Let\u2019s walk through what\u2019s going wrong, why it matters, and how to resolve it.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>What Changed in cPanel 110.126 and 110.128?<\/strong><\/h3>\n\n\n\n<p>With the release of cPanel versions in the 110.x and 128.x branches, many users observed that plugins like WP Toolkit stopped functioning as expected. This issue is particularly evident right after applying these builds:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>11.110.0.65<\/strong><strong><br><\/strong><\/li>\n\n\n\n<li><strong>11.126.0.21<\/strong><strong><br><\/strong><\/li>\n\n\n\n<li><strong>11.128.0.11<\/strong><\/li>\n<\/ul>\n\n\n\n<p>In-depth reviews of affected systems revealed a common thread \u2014 the <strong>addonfeatures directory was missing<\/strong>. This directory is vital because it serves as a <strong>registry of WHM plugin availability<\/strong>. Many third-party and bundled tools rely on it to detect available features and render their UIs accordingly. <\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Why the <\/strong><strong>\/addonfeatures<\/strong><strong> Directory Matters<\/strong><\/h3>\n\n\n\n<p>The \/usr\/local\/cpanel\/whostmgr\/addonfeatures directory acts as a flag for WHM-integrated plugins. Each file inside this directory represents a plugin that WHM should list and load. If the directory doesn\u2019t exist, <strong>WHM assumes no add-ons are available<\/strong>, effectively hiding or breaking those tools.<\/p>\n\n\n\n<p>In the context of <strong>WP Toolkit<\/strong>, this causes:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>WP Toolkit menu not showing in WHM or cPanel<br><\/li>\n\n\n\n<li>UI load failures<br><\/li>\n\n\n\n<li>Licensing issues with commercial plugins<br><\/li>\n\n\n\n<li>Broken links or \u201cmissing feature\u201d errors <\/li>\n<\/ul>\n\n\n\n<p>This bug affects <strong>not just WP Toolkit<\/strong>, but <strong>any other plugin<\/strong> that depends on WHM addon discovery via this path.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Root Cause: Update Scripts Missed It<\/strong><\/h3>\n\n\n\n<p>The problem doesn\u2019t appear to be intentional deprecation. It seems more likely that the cPanel update process either:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Removed the directory by mistake<\/strong>, or<br><\/li>\n\n\n\n<li><strong>Failed to recreate it post-upgrade<\/strong><\/li>\n<\/ol>\n\n\n\n<p>This means any plugin installation done before the update will lose its addonfeatures reference, causing the system to forget the plugin exists.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Symptoms of the Bug<\/strong><\/h3>\n\n\n\n<p>If your system is impacted, you might observe the following symptoms:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>WP Toolkit is no longer listed in WHM or cPanel<br><\/li>\n\n\n\n<li>Running whmapi1 list_addon_features returns an empty list<br><\/li>\n\n\n\n<li>Errors in plugin logs referencing missing WHM hooks<br><\/li>\n\n\n\n<li>Broken cPanel icons for third-party integrations <\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>How to Fix the Problem<\/strong><\/h3>\n\n\n\n<p>The solution is fortunately <strong>simple and safe<\/strong>. You just need to <strong>recreate the missing directory and repopulate it<\/strong>.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Step 1: Recreate the Directory<\/strong><\/h4>\n\n\n\n<pre class=\"wp-block-code\"><code>mkdir -p \/usr\/local\/cpanel\/whostmgr\/addonfeatures<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Step 2: Add the WP Toolkit Flag<\/strong><\/h4>\n\n\n\n<p>Inside the newly created directory, add a file named wp-toolkit (or use the relevant plugin identifier):<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>touch \/usr\/local\/cpanel\/whostmgr\/addonfeatures\/wp-toolkit<\/code><\/pre>\n\n\n\n<p>Note: If you use other plugins, you\u2019ll need to add their respective flag files too.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Step 3: Restart cPanel Services<\/strong><\/h4>\n\n\n\n<pre class=\"wp-block-code\"><code>\/scripts\/restartsrv_cpsrvd<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Step 4: Clear the Cache (Optional but Recommended)<\/strong><\/h4>\n\n\n\n<pre class=\"wp-block-code\"><code>\/usr\/local\/cpanel\/bin\/whmapi1 flush_cpanel_cache<\/code><\/pre>\n\n\n\n<p>After this, navigate back to WHM or cPanel. Your WP Toolkit tab should now be visible and fully functional.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Preventing the Issue in Future Updates<\/strong><\/h3>\n\n\n\n<p>Here are some best practices to avoid getting caught off guard again:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Opt for the cPanel <strong>Long-Term Support (LTS)<\/strong> release channel when deploying in production environments.<br><\/li>\n\n\n\n<li>Set up <strong>nightly backups<\/strong> to ensure you can quickly restore your system if something goes wrong.<br><\/li>\n\n\n\n<li><strong>Subscribe to cPanel change logs and forums<\/strong> to stay updated on known bugs.<br><\/li>\n\n\n\n<li><strong>Use pre\/post update hooks<\/strong> to check plugin directories or restore from backup. <\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Final Thoughts<\/strong><\/h3>\n\n\n\n<p>Software updates are vital for security and performance, but they can occasionally introduce unintended side effects. This particular bug in cPanel versions 110.126 and 110.128 is a good reminder to <strong>test updates in staging<\/strong> before applying them to production systems.<\/p>\n\n\n\n<p>Luckily, this issue has a straightforward fix. If you\u2019re a system admin or web host affected by this glitch, re-creating the missing addonfeatures directory should quickly bring things back to normal. A <a href=\"https:\/\/www.supportpro.com\/blog\/choosing-the-right-cloud-support-service-provider\/\" title=\"good Service provider\">good Service provider<\/a> doesn&#8217;t just keep the lights on &#8211; they enable your business to move faster, safer.<\/p>\n\n\n\n<p>Stay patched, but stay prepared with a <a href=\"https:\/\/www.supportpro.com\/serveradministration.php\" title=\"\">good, dedicated server management<\/a> Plan from <a href=\"https:\/\/support.cpanel.net\/hc\/en-us\/community\/posts\/19407422173335--SupportPRO-Outsourced-Web-Hosting-Server-Management-Support-Specialists-\" title=\"\">SupportPRO<\/a>.<\/p>\n\n\n\n<div class=\"wp-block-media-text alignwide has-media-on-the-right is-stacked-on-mobile is-vertically-aligned-center has-white-background-color has-background\"><div class=\"wp-block-media-text__content\">\n<p class=\"has-large-font-size\">Facing issues? <\/p>\n\n\n\n<p class=\"has-large-font-size\">Our technical support<br>engineers can solve it. <\/p>\n\n\n\n<!--HubSpot Call-to-Action Code --><span class=\"hs-cta-wrapper\" id=\"hs-cta-wrapper-3350a795-db50-482f-9911-301930d1b1be\"><span class=\"hs-cta-node hs-cta-3350a795-db50-482f-9911-301930d1b1be\" id=\"hs-cta-3350a795-db50-482f-9911-301930d1b1be\"><!--[if lte IE 8]><div id=\"hs-cta-ie-element\"><\/div><![endif]--><a href=\"https:\/\/cta-redirect.hubspot.com\/cta\/redirect\/2725694\/3350a795-db50-482f-9911-301930d1b1be\" ><img decoding=\"async\" class=\"hs-cta-img\" id=\"hs-cta-img-3350a795-db50-482f-9911-301930d1b1be\" style=\"border-width:0px;\" src=\"https:\/\/no-cache.hubspot.com\/cta\/default\/2725694\/3350a795-db50-482f-9911-301930d1b1be.png\"  alt=\"Contact Us today!\"\/><\/a><\/span><script charset=\"utf-8\" src=\"https:\/\/js.hscta.net\/cta\/current.js\"><\/script><script type=\"text\/javascript\"> hbspt.cta.load(2725694, '3350a795-db50-482f-9911-301930d1b1be', {\"useNewLoader\":\"true\",\"region\":\"na1\"}); <\/script><\/span><!-- end HubSpot Call-to-Action Code -->\n<\/div><figure class=\"wp-block-media-text__media\"><img fetchpriority=\"high\" decoding=\"async\" width=\"904\" height=\"931\" src=\"https:\/\/www.supportpro.com\/blog\/wp-content\/uploads\/2022\/09\/Free-server-checkup.png\" alt=\"guy server checkup\" class=\"wp-image-12943 size-full\" srcset=\"https:\/\/www.supportpro.com\/blog\/wp-content\/uploads\/2022\/09\/Free-server-checkup.png 904w, https:\/\/www.supportpro.com\/blog\/wp-content\/uploads\/2022\/09\/Free-server-checkup-291x300.png 291w, https:\/\/www.supportpro.com\/blog\/wp-content\/uploads\/2022\/09\/Free-server-checkup-768x791.png 768w, https:\/\/www.supportpro.com\/blog\/wp-content\/uploads\/2022\/09\/Free-server-checkup-585x602.png 585w\" sizes=\"(max-width: 904px) 100vw, 904px\" \/><\/figure><\/div>\n","protected":false},"excerpt":{"rendered":"<p>If you&#8217;re managing WordPress installations through WP Toolkit on cPanel, you may have noticed strange behavior or complete non-functionality after upgrading to certain cPanel versions. Specifically, users upgrading to versions&hellip;<\/p>\n","protected":false},"author":4,"featured_media":14613,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_lmt_disableupdate":"","_lmt_disable":"","footnotes":""},"categories":[66,194],"tags":[],"class_list":["post-14612","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cpanel","category-dedicated-server-support"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/posts\/14612","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/comments?post=14612"}],"version-history":[{"count":3,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/posts\/14612\/revisions"}],"predecessor-version":[{"id":16862,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/posts\/14612\/revisions\/16862"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/media\/14613"}],"wp:attachment":[{"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/media?parent=14612"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/categories?post=14612"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/tags?post=14612"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}