<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>addon-modules-general on</title><link>https://docs.whmcs.com/9-1/tags/addon-modules-general/</link><description>Recent content in addon-modules-general on</description><generator>Hugo -- gohugo.io</generator><atom:link href="https://docs.whmcs.com/9-1/tags/addon-modules-general/index.xml" rel="self" type="application/rss+xml"/><item><title>Addon Module Oops! Errors</title><link>https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-addon-modules/addon-module-oops-errors/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-addon-modules/addon-module-oops-errors/</guid><description>Covers the generic Oops! error that appears when an addon module is incompatible with the WHMCS version or system configuration, and the fix: remove the module files from the /modules/addons directory or obtain an updated version from the developer.</description></item><item><title>Missing Addon Modules</title><link>https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-addon-modules/missing-addon-modules/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-addon-modules/missing-addon-modules/</guid><description>Explains why an addon module does not appear in the Admin Area Addons menu: the module files are missing from the system, or the logged-in administrator role lacks the required module access, and the fix — verify the module&amp;rsquo;s files exist and that the administrator role includes it.</description></item></channel></rss>