Whmcs Addon

[Ellyn Krucke]

Dependingon your purpose, you may wish to use product addons or you may wish to use configurable options. Configurable options on products allow you to give your clients ways to alter the price of that product while product addons do not.

For product addons, WHMCS uses the prorata date setting from the associated parent product or service instead of a separate date. WHMCS will then bill for the product addon and the parent product or service on the same day of the month for their respective billing cycles.

Click a predefined addon to automatically prepopulate the Create New Addon settings with the appropriate values. For example, clicking WP Toolkit Deluxe (cPanel) will configure all of the necessary settings for an addon to sell WP Toolkit Deluxe on your compatible cPanel servers.

I recently relocated the WHMCS license from an old domain to a new one. I followed the move process according to the instructions, and the license information shows correct details for IPs, domains and directory. The old WHMCS directory is completely offline, and has a 301 redirect to the new location. I was using Chrome for all of this, so thinking it might be a cache issue, I then used Firefox, which has never visited this new site. Same results. Every other page I attempted to access in the admin panel appears to be okay.

When I log into my 'Members Area' of the whmcs.com site, I see the same information I have seen since I made the change from the old domain name. The Valid IPs, Valid Domains and Valid Directory are all correct. The license is an owned license. I clicked the 'Click here to enter a new license key' link in the error message, and reentered the information. I also tried reissuing the license again, but the same 'Invalid License' message keeps showing up.

So what does this mean? I no longer even use eNom, and had deactivated that module. Even if I did, why would WHMCS 7.5.1 have any core modules encoded by an older version of ionCube Encoder? While this page: _7.0-7.4_System_Requirements only provides requirements for WHMCS up to version 7.4, it would make sense that versions after 7.4 would not regress to need PHP 5.x.

@wsaThis issue was reported to our development team and is currently staged for release. Switching to PHP 5.6 or 7.0 will allow you to deactivate the module without encountering any errors in the meantime.

@WHMCS Alex I used to manually update, although ever since the Automatic Updater was released, I have used it every time. It seems odd that this module would have been "overlooked" by the Automatic Updater, as eNom is important enough to WHMCS that you offer a link to create a new account with them if someone does not have an existing account. Anyway, I renamed the file in question, and the reported error appears to be resolved. Thank you.

@WHMCS Alex The issue of 'outdated versions of modules' seems to be an ongoing one. I found another instance of it when I tried to look at a product. Since I used the automatic upgrade process to perform all upgrades since that process was introduced, what would you recommend? I had not planned on spending another $99 for support starting this year, and quite frankly will be steamed if I have to pay it just to fix bugs that the team introduced into WHMCS due to a poorly designed upgrade automatic process.

@WHMCS Alex Looks like it just gets worse. If you look at the attachment, you will see there are 845 files in my installation with incompatible encoding on PHP 7.0. That seems to me to be more than an oversight.

@WHMCS ChrisD Hello Chris - There are a bunch, as I mentioned previously; however, I did notice something odd as I looked through the list of files. It seems every single one listed in the incompatible list has the old account info shown.

Would it be safe to delete the contents of the table tblioncube_file_log? Everything in it pertains to where WHMCS used to be installed. The old account still exists on the same server (same IP address), although all of the files and database have been removed from the account where WHMCS used to be hosted and moved to the new account.

@WHMCS ChrisD I went ahead and emptied the table tblioncube_file_log, and of course now there are 0 incompatible encoding errors listed. That said, when I attempt to go to Setup->Products/Services->Domain Registrars, I see this:

As I mentioned previously, none of this makes any sense, as all upgrades have been performed using the automated update procedure since that process was released. This appears to be an error of some sort related to WHMCS doing housekeeping during the update process.

During the v7.6.0 update, a one-time routine will inspect and attempt to the following modules due to discontinued service by the service provider. Removal will only occur if it is not actively in use. The Activity Log will have a list of any removals. As well, if removal is not performed and the module remains in your installation, an email will be generated for all full admins so that further investigation can be performed. Inspection will be performed for the following modules:

@brian! It doesn't. Here I was thinking WHMCS would have been improved over the years, and yet it looks like the team just got lazy. I don't really care about a stray file here or there, as long as it does not lead to any security or stability issues. That said, the WHMCS team is a day late and a dollar short with this expected change in 7.6.0. I just had to buy another year's worth of support to be able to again download the version already installed on my server. Funny thing is, I noticed one of the files raising an error was 5 bytes different in size. When I inspected the file, I see that the file from my site is version 7.5.1-release.1 and is dated 17 Apr 2018. Yet the version in the new download from the WHMCS website was version 7.5.1-release.2, and dated 18 Apr 2018. This was not the only change; the encoded portion of the file was different as well.

Looks like an oversight on someone's part at WHMCS, because the release.2 version of the file SHOULD have been added to my site at during the last upgrade (since my site was up to date according to the version information on the WHMCS dashboard. Since it appears there were changes to 7.5.1 after the initial release, then I believe any such changes, however minor, should have been pushed out as a new upgrade with a new version number. Better that than have a mess like this.

I think the reason there were two releases of v7.5.1 was because in release1 they missed out the todolist.php file (which had no changes from v7.5 but was omitted from the update)... and WHMCS took the unusual step (I can't remember them doing it before) of updating the same core download file... usually they would hotfix it, or do a maintenance release.

AFAIK the only difference between the files was the omission of the todolist.php, but if you say there were other changes, then i'll take your word on it... but yes, I would have thought the autoupdater would have used r2.

Since it appears there were changes to 7.5.1 after the initial release, then I believe any such changes, however minor, should have been pushed out as a new upgrade with a new version number. Better that than have a mess like this.

I think v7.5 was their first version to actively remove deprecated files, so it was no surprise that there may have been some missing from that list... i'd have been more surprised if they had got it completely right first time.

I am trying to create an addon module only for the admins. Can you help me on how I can render templates from each controller action instead of simly echo the content? On the sample addon it says @see AddonModule\Admin\Controller::index() but I can't find the docs...

In the addon modules's _output function that is used for the admin, it only expects HTML / string as a return and thus why they build it up using a string variable in the index function. You could use the smarty engine, feed it a template file local to the addon's directory, assign the variables needed, and then use the fetch function instead of display to then get the HTML, which you then return and WHMCS spits it out. I may have another post that details this a bit more.

Sitejet Builder includes everything that your customers need to create professional websites without needing to learn to code. WHMCS 8.10 and later includes full automation support for Sitejet Builder on cPanel & WHM and Plesk hosting servers.

You can offer Sitejet Builder as part of your hosting products or as an optional product addon. Product addons allow your customers to select optional additions, like Sitejet Builder, to the products that they purchase from you.

Make sure that at least one of the servers in WHMCS at Configuration > System Settings > Servers includes Sitejet Builder.To offer Sitejet Builder through WHMCS, your hosting server must run cPanel & WHM version 116 or higher or Plesk 12.2 or higher.

Gathering information about how your customers interact with your website and complete their orders is integral to making your business decisions. This practice, called "ecommerce tracking," is a part of most modern commercial websites and can be expanded to include other data as well.

Google Analytics is a free web analytics tool that over 50 million websites worldwide use to track and analyze website traffic. It allows you to track how people find your site, how they use it, and how they become customers ("conversion"). Google Analytics tracking technology lets you see trends for page views, visits, bounce rates, conversion rates, geographical locations, and other metrics.

The Google Analytics AddonWHMCS's Google Analytics addon has automated the processes of gathering and working with this data for several years, integrating full support for ecommerce tracking into WHMCS. It's also simple to implement: it's shipped with and is built into WHMCS by default, is free, and can be easily enabled from Configuration > Apps & Integrations.

When you use the Google Analytics addon, you'll be able to track customer movement throughout the Client Area. Then, WHMCS lets you combine it with extensive reporting on traffic sources and other demographics. Shopping cart and purchase metrics are helpful to find the right ways to expand your business and monitor revenue streams. WHMCS can also combine its data about order contents and products with the Google-tracked Client Area traffic. It will give you a great picture of your current conversion rates and the success of your marketing campaigns.

Google Analytics 4Recently, we updated the Google Analytics addon to support Google Analytics 4, referred to as Global Site Tag in the addon, in additon to the previously-supported Google Analytics and Universal Analytics versions.

Google introduced Google Analytics 4 in fall of 2020, replacing the previous default, Universal Analytics. It's a new kind of analytics that features smarter reporting capabilities compared to Universal Analytics. Data calculations like churn probability and other predictive measures will give you additional foresight into your customers' next choices. Other improvements make it easier to use advertising and allow you to view data in customer-centric reports rather than in reports focused on platforms or devices used.

Moving to Google Analytics 4 (Global Site Tag) doesn't change much in the WHMCS addon itself. The main change is simply that Google encourages conversion to Google Analytics 4 and defaults to creating Google Analytics 4 IDs for new tracking. Switching your existing use of the addon to Google Site Tag will also let you take advantage of the smarter reporting available through Google.

Making The SwitchYou can tell the version of Google Analytics you're currently using in WHMCS at Configuration > System Settings > Addon Modules. Just click Configure for the Google Analytics addon.

Analytics Version will indicate the version you're using. You can further verify the version by checking the Tracking Code: If it starts with UA-, it's for Universal Analytics or the older version of Google Analytics. (Global Site Tag codes start with G-.)

When you're ready to move over, all you need to do is log in to Google Analytics, click Admin in the bottom-left corner, and then click GA4 Setup Assistant in the Property column.

Click Get Started and then Create Property, and Google will take care of everything for you.

One easy way of finding your new ID is to search "Measurement ID" or "Tracking ID" in the top search bar. You'll see something like this appear in the search menu:

Then, all you have to do is go to Configuration > System Settings > Addon Modules in WHMCS. Just click Configure for the Google Analytics addon, set Global Site Tag as your Analytics Version, and update your Tracking Code to use the new Measurement ID.

We hope that you enjoy the new benefits of Google Analytics 4. You can find more about the Google Analytics addon for WHMCS in our documentation.

3a8082e126