WHMCS Integration • WordPress, Joomla, Custom Templates
WHMCS is the leading web hosting manager. It covers all aspects of running a hosting business but for the rest is a bit too basic. For example, the built-in news and knowledge base systems seem to come from the 90's. There's no room for Search Engine Optimization and a blogging platform. It also lacks new technologies like Open Graph Protocol and Structured Data.
As opposite, CMS like WordPress, Joomla or Drupal are great for publishing contents. They include all the recent SEO enhancements. Blog? Check. News? Check. Documentation? Check. The only problem is that a CMS doesn't know anything about managing a hosting business.
You might be thinking that using both systems together is a great idea as you get the best from both ecosystems. In one shot you're also addressing weak points, but is that really true? It took us almost a decade to understand that mixing WHMCS with say WordPress is a terrible idea. All you get is Frankenstein.
The problem here is that a CMS gives the impression that your site is taking shape very quickly. Installation is a question of minutes. There are a thousands of templates to choose from. If you have a special requirement, thousands of plugins are just a click away.
The truth is that using a CMS to deliver contents and WHMCS to manage your hosting business, is like taking care of two babies. You have more to do and less time to do it. Let us describe you what you're going to face if you choose to follow this path.
To make your hosting business shine and prosper, first you should be learning the tools you rely on. Avoiding common mistakes in WHMCS is crucial since the learning curve is very steep.
As a reference, we use WHMCS from day one and we're still learning. It takes years before you feel confident. Using a CMS next to WHMCS slows this process even further. In fact you need to keep up with an additional software like WordPress, Joomla or Drupal.
How can an human keep an eye on tickets, servers, web panels, modules, registrars, CMS and plugins all in the same time? If you have a team of professionals or your name is John Wick that's good but is it really worth it?
Running two systems doubles complexity. You end up having multiple databases, credentials, GDPR & cookie policies. Invoices, orders, payments, products and services are on WHMCS. Posts, comments, marketing campaigns and analytic tools are on the CMS.
No matter how good is your team, you dissipate energies and waste time. The situation is aggravated when you are a one-man company or have a small team. In this case you can't cope up with such a structure and you will likely neglect part of the duties.
WHMCS and your chosen CMS both need updates. You can't postpone them for too long. It would expose yourself to the obvious risks of running outdated software.
We cannot speak for CMS, but WHMCS over the last few years has become a time bomb. Upgrading WHMCS is like jumping off cliffs believing you can fly. Before you attempt an upgrade, you need to:
- Backup all files (200+ MB) and database (40 MB up to several gigabytes)
- Make sure all third-party modules are compatible with the latest version
- Double-check all settings and action hooks in use
- Update template in line with recent changes
- Deal with new bugs that adds up to old ones that never get fixed
- Try new features that most of the times look incomplete and never tested before
- React to an option that has been deprecated for whatever reason
If you are brave enough you can try to upgrade a production system. If something goes wrong you have to perform a roll-back. Far more likely, first you will attempt the upgrade on a test system that hosts a clone of your WHMCS that adds to serious time loss that could better be spent on managerial duties.
It looks boring, complicated and time-consuming and it actually is. Minutes add up fast and lost productivity is real. That's why more and more hosting companies can be reluctant to upgrade WHMCS. Some are even still running WHMCS v5 released on 2011. Upgrading is scary and we're just looking at WHMCS.
What about the CMS? It doesn't magically update itself so you need to go through a similar process again. How many months will your patience last? Anything can break your integration or "bridge" in any moment.
In the long run, sooner or later you end up discarding updates diminishing security level. Taking care of WHMCS, CMS and the integration itself is in fact a frustrating experience.
You surely want your chosen CMS and WHMCS to look the same. This way visitors don't notice they're navigating through different platforms. To this end, you need to create two versions of the same template. It can take weeks or months depending on your skills.
It should be noted that WHMCS uses Smarty and Bootstrap 3 till v7 and Bootstrap 4 from v8.1. Moreover almost every time there's a major release, old templates are dropped in favor of new ones. WHMCS staff don't give a damn about backward compatibility.
A CMS likely uses HTML and probably the latest stable version of Bootstrap. As result, responsiveness and syntax are going to be different on the two systems. Making things twice taking into account exceptions is not a wise way to invest time.
Let me ask you one question. How can you plan upgrades when you rely on systems that have different development life cycle? With budget, time and expertise. Things that small and medium-sized enterprises can't invest on templates.
CMS are generally always on top of things in line with new trends and technologies. On the other hand WHMCS always falls behind. It doesn't even try to keep up with changes as their focus is something else.
So here you go. In 2020 WHMCS starts implementing Bootstrap 4 that was released on 2015. In the same time Bootstrap 5 is almost ready to be used in production and soon will be available on any CMS. With these premises, templates take an unreasonable amount of time for small and medium-sized enterprises.
Next we have the need to share customer logins between WHMCS and the CMS and sync users' database. Of course logout have to work from both sides. You can make it happen with a couple of action hooks, PHP scripts or a bridge. But the final result is not the same as having customers consolidated on one platform.
Going back and forth from CMS to WHMCS feels like traveling in two cars. You write posts, approve comments and create landing pages on the CMS while invoices, services and payments occur on WHMCS. It's counter-intuitive design.
What about products' page, order process, members area, contact us and news? Such features exist on both WHMCS and CMS. The first step is deciding who does what. Second put it into practice with a bunch of scripts. Let's focus on news supposing you want to use WordPress.
Begin disabling WHMCS Announcements by coding a couple of action hooks. Once you removed all references from navbar and sidebars, redirect visitors to WordPress. Last create htaccess rules to redirect old announcements still indexed on Google.
This requires programming skills, extensive knowledge of WHMCS and a couple of hours. And we are just talking of news. There are tens of duplicated features that need to be addressed. That's not impossible but it's starting to become too much effort to be worth it.
Let's move to analytics, conversion tracking and marketing campaigns. Who should benefit from such efforts? WordPress or WHMCS? No matter what the answer is. Both need tracking and analytics otherwise you miss half of the data.
What's the point of having visitors clicking on Facebook Ads and see them disappearning when they move from WordPress to WHMCS? This undermines your efforts as you can't even understand if your marketing campaigns are generating sales.
A CMS rocks from an SEO perspective while WHMCS is terrible. A post on your CMS outshines WHMCS where you are actually selling products.
Most people try to solve the problem by replicating products' pages on WordPress and link them to their counterparts on WHMCS. This adds steps to the purchasing process making it too long and complex for no actual reason.
Moreover WHMCS is so bad at SEO that causes problems with indexing and duplicate content. This affects also your CMS since search engines see them as a whole and not as two separate entities.
Both platforms have to stay on separate hosting plans to avoid vulnerabilities. In fact a cracker could get access to WHMCS by exploiting a vulnerability of your CMS and viceversa. The very fact that systems have to stay separated can turn the easiest of the task into a PHP nightmare. That's how most people end up using iframes which is bad.
We could go on forever with examples but it's clear that WHMCS bridges and integrations are not the way to go. It requires to much work and efforts that you weren't expecting. Completing an integration takes months. Keeping it functional with upgrades is an ongoing concern that never ends.
It's so exhausting that sooner or later nobody cares anymore to update the CMS and WHMCS. We speak speak from experience. The majority of CMS we integrated with WHMCS have been abandoned because few companies have time and skills to update them.
From time to time the owners of these websites contact us. They want us to "refresh" the integration but let's face it. Integration is not a sustainable process from both sides. It is expensive for customers and extremely boring for developers to code. The good news is that there's another way.
We have more than 14 years of experience in WHMCS. We completed countless integrations with several CMS and custom-made sites. We realized that we were reinventing the wheel on every integration so we came up with the idea of using WHMCS as CMS.
It took us a lot of time but we finally managed to wipe out clumsy "bridges" and fragile integrations. We developed a module to transform WHMCS into a complete CMS. It lets you publish contents on the internet to:
- Deliver news
- Attract potential customers with a blogging platform
- Offer Tier 0 (self-help) support writing documentation
- Improve service quality opening to feature requests, bug reporting and ratings
- Inform people about software releases
- Offer live demo for service free trial and premium (paid) tickets
- Multi-domain and Multi-brand support
- IP Geolocation
The module is named Mercury and has nothing to envy to WordPress, Joomla or Drupal. It comes comes packed with all latest SEO tools:
- Meta descriptions
- Open Graph Protocol
- Structured Data JSON-LD
- SEO Friendly URL
- Canonical URL
- Sitemap generator
- Multi-language support
This same post you are reading is powered by Mercury. More in particular this entire website is based on WHMCS and every page you see (news, posts, documentation, live demo, changelogs, feature requests...) is possible thanks to Mercury.
We don't waste time with templates, two admin interfaces, separate databases, credentials... it's all part of WHMCS. This way we accomplished to use WHMCS both as CRM and CMS.
We're proud to say that integrations and "bridges" are things from the past. Mercury improves productivity in daily use. Next time you start thinking about an integration, do yourself a favor and give a try to Mercury. Additionally it includes:
- HereLang to translate contents on the fly
- SorTables for data visualization
- Improved fields with MagicInput
By using Mercury you won't have any of the disadvantages listed above. WHMCS will be the only panel to use for both CRM and CMS.
You might also be interested in our free collection of action hooks for WHMCS.