WisTex

Are you sure that the GDPR requires you to delete their account? The billing information in WHMCS is directly related to the invoices and VAT records, which you are supposed to retain. It does not make sense that the right to be forgotten includes financial and tax records. If that was the case, people could just call up their credit card company and tell them to delete their account so there is no record of what they owe or where to send the bill. https://www.gdpreu.org/right-to-be-forgotten/ One of the exceptions of the right to be forgotten is "If the data is used to comply with a legal obligation or ruling." It sounds to me that, if you are required by law to keep the invoices and the contact information related to that invoice, you are not required to delete their account under the GDPR, even if they ask you to do so. Their contact information is directly related to the financial transactions on their account. They should not be able to delete that. But, I am not an attorney or solicitor, so you may want to check on that yourself. But if you could delete your contact information at your bank or vendor, that would just be silly.

I have it set up so that it imports emails into the ticket system. The cron is set up, and the cron does run, but the Support Ticket Mail Import Log shows the following error for every email: Argument 7 passed to processPoppedTicket() must be an instance of WHMCS\Mail\AutoSubmittedHeader, array given, called in /home/username/whmcsdata/crons/pop.php on line 0 WHMCS 8.8.0 cPanel 110.0 (Build 12)

People typically use the affiliates program to track commissions, as that is what it is designed for. Although using promo codes with an attached discount is also used by some web hosts to track affiliates as well. I haven't heard of anyone using promo codes without a discount through. You could modify the template or language files so that it no longer says "0% discount applied" but I think it would be better if you used the affiliated program feature or used promo codes that have a discount attached to them.

I was reading the documentation about the "Order Days Grace" that is located under General Settings > Ordering with the description "The number of days to allow for payment of an order before being overdue." I was wondering if this could be used to, in effect, create Net 30 or Net 15 billing, where the due date is set 30 or 15 days after the order is placed. Based on the documentation, I believe this achieves that. And it appears that the domain grace and redemption period is managed separately under General Settings > Domains. I would like to confirm that: The "Order Days Grace" only applies to product and service invoices, and not domains. That domain grace / redemption periods are managed separately from this setting. All future invoices for renewals also have the same grace period. Also, is there any way to do the following? Only allow approved customers to have a grace period on invoices. My goal is to allow approved vetted customers Net 30 billing for products and services (but NOT domains), while everyone else must pay in advance. Is there any way to set it up like this?

One thing that WHMCS just did is niche themselves. I was hoping that WHMCS could be used as a general billing system, but with the new licensing terms and pricing, it simply does not make sense to use WHMCS for anything other than hosting and domains and related reoccurring services. Especially since they seem to count one-time purchases as active clients. They are currently the best at hosting and domains billing, and they want to get paid for that. I understand and respect that. They want to be a premium product. They will lose customers who do not want to pay premium prices, but they will be more profitable on the customers they keep. This will spur more competition who will swoop in to fill the non-premium void, but WHMCS seems to be okay with that. As long as WHMCS keeps advancing and stays ahead of everyone else in features and usability, they will be okay. But as soon as a competitor matches the features at a better price point, the scales will be tipped. This can either go one of three ways: Quicken vs. Tons of New Competitors - Quicken remains the most respected brand, but the accounting space is now crowded with competitors, many who are catching up fast. Sim City vs. Cities: Skylines - Sim City was the best until Cities: Skylines came out. Sim City still exists, but no new releases have come out in years. Toys R Us vs. Walmart - Toys R Us were everywhere, and then Walmart came along. Toys R US faltered, stagnated, and ultimately died, while Walmart grew by leaps and bounds. So, is WHMCS going to be Quicken, Sim City, or Toys R Us? Only time will tell. I had big plans to use WHMCS to manage all of my customers. But under the new licensing, they just relegated themselves to hosting and domains only. In fact, I am creating a brand that is specifically for hosting and domains, and then billing all my non-hosting customers under another brand. It does not make economic sense to pay a license fee for someone who made a one-time purchase of a course or downloaded a free product once. It should be interesting how this plays out. WHMCS is now niche and premium. This changes the game significantly.

It did stop working a couple of updates ago. Before, having getuserid.php in the root directory, and then including it in any PHP file outside of the root directory would work. But something broke it in a recent WHMCS update.

I am glad that I read this before setting up WHMCS. I was planning on using WHMCS for a general billing platform, but if a one-time client that ordered from you 5 years ago is considered an active client and goes against your active client ceiling, then WHMCS simply is not suitable for one-time products. So, new strategy for me: WHMCS is only for reoccurring hosting and domain names. All other billing will go through a competing company's platform. I love WHMCS, but it does not make business sense to pay a license for clients that do not generate reoccurring revenue. Especially if that one "purchase" was a free promotional item that they didn't even pay for. I can understand if a one-time client or free item counted against your active client ceiling for a certain period of time, but after 30 days or 90 days, if the customer has not ordered again, they should not be considered an active client. Maybe it already does this and we don't know about it. But it does not make sense for stale customers to be listed as active. Hopefully WHMCS can clarify whether stale accounts count against your cap forever or not.

The update broke the login redirect. Previously you could use the following code: <form action="/dologin.php?goto=/subdirectory/filename.php?variable=1" method="post"> And it would redirect you to https://example.com/subdirectory/filename.php?variable=1 as intended. Instead, it is redirecting you to https://example.com/filename.php?variable=1 For some reason, it is removing the subdirectory, which totally breaks our website. Can we get this fixed, please?

Yes, you have to legally disclose those types of cookies, as indicated in the link to the EU government website. But the WHMCS session cookie legally does not have to be declared. The EU government even states as such. While it is true that it is better to err on the safe side to avoid fines (if you are subject to EU jurisdiction), on the other hand, if everyone has a cookie notice, then the cookie notice becomes meaningless because consumers cannot tell the difference between a website that is using exempt cookies and a website using marketing or tracking cookies. As a website operator, you should know what cookies are being generated and provide the appropriate notice. Not doing so means that you don't understand the security and data collection of your own website.

I've noticed some threads about cookies and I was wondering myself about WHMCS cookies and the EU Cookie Law. I did a little digging and the cookie that WHMCS generates appears to be exempt from the law because it is necessary for the operation of the website. Or, in other words, under the law, the user's action of creating an account implies consent that a cookie is used to manage user sessions so the user can actually log in, therefore you don't have to ask for consent. http://ec.europa.eu/ipg/basics/legal/cookies/index_en.htm So, unless you are adding additional cookies, you don't need to ask for consent to use cookies. You don't have to ask for consent for a user login session cookie.

Will using the DirectoryIndex directive in .htaccess affect WHMCS in any way? All the calls WHMCS tries to make seem to be directed to index.php, so there does not appear to be a problem. .htaccess DirectoryIndex main.php Is this the best way to change the default home page or is there a better way?

Since I can't edit the previous post, I'd like to clarify that: This is a way to create pages that can access the WHCMS login state outside of the WHMCS root directory. Not sure if my usage of "root" in the last sentence was clear that I meant the WHMCS root, and not necessarily the root of your website.

Good point. I was thinking of "outside" as being "not in the WHMCS root directory" because the documentation on how to make pages clearly states that using the example code outside of the root directory is not supported. So a more accurate statement would have been that this is a way to create pages outside of the root directory.

Found the solution. The sample code provided by WHMCS assumes you want to use the WHMCS templating system. But if you do not want to use WHMCS's templating system and output your PHP code directly, then you have to take a different approach. First, you create a file in WHMCS's root directory that accesses WHMCS's session and sets variables: getuserid.php <?php // gets session variables from WHMCS require("init.php"); $ca = new WHMCS_ClientArea(); // sets userid for the logged in user. Is set to 0 if no one is logged in. $userid = $ca->getUserID() ; // sets loggedin to true if logged in, and false if not logged in. If ($userid > 0) { $loggedin = true; } else { $loggedin = false; } // if you want to test if it is working, uncomment this line. // echo "User ID = " . $userid; // if you want to test whether $loggedin variable is set, uncomment these 2 lines. // if ($loggedin) { echo "Logged in"; } // else { echo "Not logged in"; } ?> You can then include this in any PHP file you want anywhere in the file system. So if you want to put your custom code or third-party script in a subdirectory, you can. You would include the following code and then use the variable as needed. any.php <?php // use this if your file is in the same directory. require("getuserid.php"); // use this instead if your file is in a subdirectory. // require("../getuserid.php"); // test to make sure it is working. echo $userid; // use if then logic to determine what to show. if ($loggedin) { /* insert code for logged in users here */ } else { /* insert code for everyone else here */ } ?> Modify as needed, obviously. I hope that helps.

It appears modules would not be a suitable solution for my issue, for the following reasons: The example code outputs the WHMCS header and footer even though I don't need it. The template and the PHP code are separated in WHMCS and in my existing script, HTML and PHP are merged. As such, it is actually impossible to just cut and paste the code from the other script into the module and have it work. Since the whole purpose of integrating the other script is to not have to rewrite it, modules would not be an ideal way to do it.