This is an unofficial Google Chrome extension for WHMCS. The purpose of this extension is to indicate when you have pending tickets or orders which need attention. The extension polls your admin URL once per minute, additionally keeping in sync each time you navigate within the admin area. You are then alerted to pending tickets/orders in two ways:
- An icon with badge indicating the current total pending count.
- Notifications triggered when the count increases.
You can install the extension from the Chrome Web Store. If you to prefer to install from source, just download the source, visit chrome://extensions and use the "Load unpacked extension..." option to let Chrome know which directory the source lives in.
Following installation you'll need to access the extension's options page and configure your WHMCS admin URL.
There's not much to explain, the extension does what it says on the tin!
You can click on the extension's notifications to open a new tab on the appropriate WHMCS page (either pending orders or pending tickets). You can also click on the icon in your browser window to highlight the existing WHMCS tab or open a new one. To avoid loss of any unsubmitted form data, the extension will never reload existing tabs.
Installing this extension will prompt you to allow the extension to "Read and change all your data on the websites you visit". The extension cannot request access to specific URL's at runtime (following configuration of your admin URL), as such access to all URL's must be requested at installation time.
This was created for my own personal needs as a quick weekend project. The source code isn't perfect and shortcuts may have been made in places.
The extension does not use the WHMCS external API, so you're expected to be using the default admin theme ("blend") for the correct values to be read from HTML.
First version released, Hello World!
Fixed a syncing issue when visiting whmcsconnect.php.
Remove unnecessary code from notifications. Hopefully this update fixes the repeat notification issue, however I'm struggling to reproduce this problem accurately.
Fixed repeat notification issue. This was caused by the background page being killed while inactive, destroying the state each time. The last known notification counts are now stored in chrome.storage for persistence.
New option to disable notifications.