<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[WHMCS Services Forum - License Questions]]></title>
		<link>https://forum.whmcsservices.net/</link>
		<description><![CDATA[WHMCS Services Forum - https://forum.whmcsservices.net]]></description>
		<pubDate>Fri, 10 Apr 2026 09:11:57 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[What is a development license?]]></title>
			<link>https://forum.whmcsservices.net/showthread.php?tid=68</link>
			<pubDate>Wed, 15 Oct 2025 23:39:19 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.whmcsservices.net/member.php?action=profile&uid=6">wsadmin</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.whmcsservices.net/showthread.php?tid=68</guid>
			<description><![CDATA[A development license allows you to setup a secondary instance of WHMCS for testing and development purposes.<br />
<br />
You get one free with the module you bought and if you need second developer license it will cost one-time &#36;25.00 fee<br />
<br />
Please open a ticket to license dept.]]></description>
			<content:encoded><![CDATA[A development license allows you to setup a secondary instance of WHMCS for testing and development purposes.<br />
<br />
You get one free with the module you bought and if you need second developer license it will cost one-time &#36;25.00 fee<br />
<br />
Please open a ticket to license dept.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Registered user needs to unlock another domain]]></title>
			<link>https://forum.whmcsservices.net/showthread.php?tid=67</link>
			<pubDate>Wed, 15 Oct 2025 23:38:54 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.whmcsservices.net/member.php?action=profile&uid=1">whmcsservices</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.whmcsservices.net/showthread.php?tid=67</guid>
			<description><![CDATA[Our licensing policy for a single-user license allows you to install your WHMCSServices.com product on one Domain. The main understanding is that it is not used simultaneously by different people.<br />
<br />
To unlock a second (or new) Domain, you will have to repeat the unlock process with the second domain. Note that the same unlock key will not work on both domains, as the key is made specifically for the displayed site code (unique with every installation), then you will need to pay a small fee.<br />
<br />
...and then contact Support]]></description>
			<content:encoded><![CDATA[Our licensing policy for a single-user license allows you to install your WHMCSServices.com product on one Domain. The main understanding is that it is not used simultaneously by different people.<br />
<br />
To unlock a second (or new) Domain, you will have to repeat the unlock process with the second domain. Note that the same unlock key will not work on both domains, as the key is made specifically for the displayed site code (unique with every installation), then you will need to pay a small fee.<br />
<br />
...and then contact Support]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Where can I reissue my License?]]></title>
			<link>https://forum.whmcsservices.net/showthread.php?tid=66</link>
			<pubDate>Wed, 15 Oct 2025 23:36:13 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.whmcsservices.net/member.php?action=profile&uid=6">wsadmin</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.whmcsservices.net/showthread.php?tid=66</guid>
			<description><![CDATA[All Licences can be reissued for free without limitations. Login into our client area and click the “<span style="font-weight: bold;" class="mycode_b">Services &gt; My Licenses</span>” link from the client menu. Click the module for the license Details and from the products details page click the tab "Reissue" &gt; "Reissue Licence".]]></description>
			<content:encoded><![CDATA[All Licences can be reissued for free without limitations. Login into our client area and click the “<span style="font-weight: bold;" class="mycode_b">Services &gt; My Licenses</span>” link from the client menu. Click the module for the license Details and from the products details page click the tab "Reissue" &gt; "Reissue Licence".]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Difference Between Licence and Source Code versions of WHMCS modules]]></title>
			<link>https://forum.whmcsservices.net/showthread.php?tid=65</link>
			<pubDate>Wed, 15 Oct 2025 23:35:37 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.whmcsservices.net/member.php?action=profile&uid=1">whmcsservices</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.whmcsservices.net/showthread.php?tid=65</guid>
			<description><![CDATA[We get a lot of questions about the difference between the Licence and Source code versions of our modules, so we would just like to clear things up.<br />
<br />
Both versions are exactly the same code and features; there is never a difference between features. Licence Version check our licensing system, which checks the license against our database, and the source code doesn't<br />
<br />
The Licence version is encoded with IonCube just like WHMCS is, meaning the PHP files cannot be read or changed (any template files included are always open source).<br />
<br />
The Source code version is <span style="font-weight: bold;" class="mycode_b">NOT</span> encoded with IonCube and can be installed on any number of domains, provided you (your company) own (s) them. You are not allowed to sell or give away the module to others.<br />
<br />
Both versions are also always released at the same time.]]></description>
			<content:encoded><![CDATA[We get a lot of questions about the difference between the Licence and Source code versions of our modules, so we would just like to clear things up.<br />
<br />
Both versions are exactly the same code and features; there is never a difference between features. Licence Version check our licensing system, which checks the license against our database, and the source code doesn't<br />
<br />
The Licence version is encoded with IonCube just like WHMCS is, meaning the PHP files cannot be read or changed (any template files included are always open source).<br />
<br />
The Source code version is <span style="font-weight: bold;" class="mycode_b">NOT</span> encoded with IonCube and can be installed on any number of domains, provided you (your company) own (s) them. You are not allowed to sell or give away the module to others.<br />
<br />
Both versions are also always released at the same time.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Version overview and information]]></title>
			<link>https://forum.whmcsservices.net/showthread.php?tid=36</link>
			<pubDate>Wed, 15 Oct 2025 22:06:59 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.whmcsservices.net/member.php?action=profile&uid=5">citytecks</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.whmcsservices.net/showthread.php?tid=36</guid>
			<description><![CDATA[Since WHMCS Services now has several active versions and also different types of updates, there are 4 types of updates. These are:<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Major Release:</span> A major release is a new main version and contains changes to the core and usually introduces new features. 1.0 and 2.0 are major releases. You can recognize one such an update also the first number of the version number changes. With Major Releases there is always only one complete upgrade and no incremental.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Minor Release:</span> A Minor release includes new features and can also include changes to the schema and prepare major updates. The versions 2.1.0, 2.2.0 and 2.3.0 are for example Minor Releases. These updates always change the average number. With Minor Releases there is always only one complete upgrade and no incremental.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Maintenance Release:</span> Maintenance Release is, as the name suggests, maintenance updates where bugs are fixed. The versions 1.3.1 and 1.1.2 are, for example, such updates. Here the last number always changes. There is also a small incremental update for maintenance releases.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Security Release:</span> Security releases contain security-relevant updates which, for example, close security gaps. These updates are usually accompanied by maintenance releases and should be implemented promptly. Here again, the last number of the version number changes.]]></description>
			<content:encoded><![CDATA[Since WHMCS Services now has several active versions and also different types of updates, there are 4 types of updates. These are:<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Major Release:</span> A major release is a new main version and contains changes to the core and usually introduces new features. 1.0 and 2.0 are major releases. You can recognize one such an update also the first number of the version number changes. With Major Releases there is always only one complete upgrade and no incremental.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Minor Release:</span> A Minor release includes new features and can also include changes to the schema and prepare major updates. The versions 2.1.0, 2.2.0 and 2.3.0 are for example Minor Releases. These updates always change the average number. With Minor Releases there is always only one complete upgrade and no incremental.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Maintenance Release:</span> Maintenance Release is, as the name suggests, maintenance updates where bugs are fixed. The versions 1.3.1 and 1.1.2 are, for example, such updates. Here the last number always changes. There is also a small incremental update for maintenance releases.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Security Release:</span> Security releases contain security-relevant updates which, for example, close security gaps. These updates are usually accompanied by maintenance releases and should be implemented promptly. Here again, the last number of the version number changes.]]></content:encoded>
		</item>
	</channel>
</rss>