Walther

It would be a nightmare. A lot of add-on modules (that need to be updated too, cause of the different PHP version), and a lot of custom hooks (that also will need to be modified in order to work with a higher PHP version). I guess it will last for at least a few working days, maybe more... so the straight update is not viable. The database migration is also safest (anything going wrong during migration? Not an issue, just roll back and study how to fix it...) So, again, the original question: according to WHMCS doc the database migration is a breeze ( https://docs.whmcs.com/8-13/system/system-tutorials/move-whmcs-to-a-new-server/ ), but will it work with such a high version difference?

Problem: I have a fairly old WHMCS installation (WHMCS 7.10.2 and PHP 7.3.3), which is now at the end of its useful life. The current WHMCS installation is used for both the website (service presentation pages, price lists, “about us,” etc.) and the customer area. (It seemed like a good idea at the time, but it’s not: it’s a mess, management is rigid, there’s no SEO optimisation, creating multilingual pages is a mess…) So I was thinking of installing the new WHMCS in a different directory (e.g., my.example.com) and developing the main site with WP on example.com. This way I could: leave the old WHMCS site running on example.com for as long as necessary develop the new customer area on my.example.com develop the new site offline Once everything is ready, I “just” need to: delete the site on example.com install the new WP site on example.com migrate the database from the old WHMCS installation to the new one set up a series of redirects in .htaccess from the old URLs to the new ones My questions are: Did I miss something along the way? Is there something I haven’t thought of? I'll need to migrate the database from a WHMCS 7.3.3 installation to 8.13… which tables do I need to migrate? Can I do it from phpmyadmin, or are there differences in the database structure?

Nope, it doesn't work... 😟 I guess something must be set in PHP code too, but I can't find any example or documentation about...

I'm trying to create a page to display a report with several thousand records using tablelist.tpl. The problem is that I can't get pagination to work: it always shows all the (2000+) records on a single screen, whereas I would like them to be displayed in groups (10, 25, or 50), as is done, for example, in clientareadomains.tpl. However, I haven't been able to find any documentation on tablelist.tpl anywhere, so I have no idea how to implement this... Below is my TPL code: {include file="$template/includes/tablelist.tpl" tableName="DomainsResellerLogs" noSortColumns="4,5,6" filterColumn="0"} <script type="text/javascript"> jQuery(document).ready(function() { var table = getTableInstance('DomainsResellerLogs'); table.on('draw.dt', function() { //further customizations as needed }); }); </script> <div class="table-container"> <table id="tableDomainsResellerLogs" class="table table-list"> <thead> <tr> <th>Date</th> <th>Order ID</th> <th>Rel ID</th> <th>Request</th> <th>Response</th> <th>Result</th> <th>IP</th> </tr> </thead> <tbody> {foreach from=$logs item=log} <tr> <td><pre>{$log->date|wordwrap:10:"<br>":true}</pre></td> <td>{$log->order_id}</td> <td>{$log->relid}</td> <td><pre>{$log->request|wordwrap:40:"<br>":true}</pre></td> <td><pre>{$log->response|wordwrap:40:"<br>":true}</pre></td> <td>{$log->result}</td> <td><pre>{$log->ip}</pre></td> </tr> {/foreach} </tbody> </table> </div>

Update: 01/02/24 everything worked fine again (without any correction or any other operation) 02/02/24 - very same issue, but just for a few hours. Now it seems everything is running fine again. No one knows why it wasn't working, no one knows why now it's working again. I guess there was some connectivity issue, but PayPal does not provide any tool to check connectivity, so it's impossible to analyze it.

Thank you: but I already checked the charset, and it's ok ... so, sadly, it's not a charset error. (BTW: I guess that "IPN Handshake Invalid" is a general error, that covers not only charset errors but also many other different errors... and in WHMCS they reported just the more common)

I agree. But I also checked all the "improvements" of WHMCS in its following history versions, and also the bugs introduced with the newer versions... and so it's very hard to state that newer WHMCS versions are "safer" than the one I'm currently using. Even more: it's almost always possible to run safely also out-of-date software. It's more difficult, you need to create a safe environment, but it's possible (and I know many businesses much larger than mine running on much older software, and even on PHP 5.x ...)

Did the full reset fix the issue? I've been experiencing this very same issue since 15/1 ... and I just wrote my own post about it, with a few further details

I'm using WHMCS 7.10.2 (no way to update: it's a Owned "lifetime" license, and 7.10.2 is the last version I can use with my current license) I'm using the standard PayPal as default gateway module (and also the PayPal Basic), and everything was running fine until 15/1 ... After 15/1 something changed somewhere, and PayPal stopped working properly. That's to say: - the user is redirected on PayPal, he pays... but IPN is not transmitted back by WHMCS - looking into PayPal webhook logs, I can find that every transaction is "pending" with a FAIL_SOFT error - in PayPal, the URL for the webhook is right ( example.com/modules/gateways/callback/paypalwebhooks.php) - no info available in WHMCS gateway log (last PayPal entry is 15/1 with "Subscription Payment: Success") - I tried the IPN simulator of PayPal, and doing a call in WHMCS gateway Log I can find only a "IPN Handshake Invalid" So, I need to insert into WHMCS manually every PayPal payment received... very annoying and time-consuming... (Nothing changed in my WHMCS, and neither in server configuration, so I guess something changed about PayPal...) PayPal support is completely useless, and WHMCS support about Is anyone experiencing the same issue? What may have changed 15/1?

Unluckly, the registrar module manages all the TLDs the same, so even if it's not working the user is still be able to access. Any way to remove the item from the menu using some kind of hook?

Problem: few TLDs (i.e. .es) does not allow direct modification of registrant contact data; but in WHMCS also for these domains there's the standard "contact information" page in domain management page. So it happens that the user try to do it, but it doesn't work... There's any way to remove this menu item for given TLDs? Or having a pop up to warn the user to open a ticket for this kind of operation?

About db managing using capsule I googled around quite deeply, but was able to found just trivial examples... so I have an issue I can't find a way to fix. So, i.e., I understand that with this: $domain5 = Capsule::table('tbldomains')->where('status', '=', 'Active')->select('id', 'domain')->first(); I can retrieve from db the first active domain, and with $domain5-> id I can retrieve its id , and so on... And with: $domain5 = Capsule::table('tbldomains')->where('status', '=', 'Active')->select('id', 'domain')->get(); I should retrieve all the active domains but... how to retrieve the data of every single domain? I tried (unsuccessfully) to var_export($domain5) and var_dump($domain5) to analyze the structure and understand how to retrieve single fields of every record, but it doesn't work... So, what are the right methods to do it?! 🤔

Hello. It happens that few TLDs need to be renewed days before their expiration... I.e. .es domains need to be renewed at least one week before expire date. So, i.e.: a .es domain registered 15/5/22 will expire 15/2/23, but it will be necessary to renew it before 08/02/23. If it's not renewed, the domain on 09/02/23 will go in redemption mode, and renewal will be much more expensive. But I can't find any way to manage this with WHMCS... Even if I set "expiry date" as 15/2/23 and "next due date" as 08/02/23, it happens that WHMCS does not manage redemption correctly, and so a user will be able to process the renew after 08/02/23 paying just the standard fee... And setting "expire date" as 08/02/23 does not work: the system will correct it automatically during usual domain synch... Any idea?

Does exist any way to use a custom theme just for specific pages? I would like to use a custom theme for number of custom front-end pages, but would also like to use standard six theme So, i.e.; /knowledgebase.php -> custom theme /contact.php -> custom theme /index.php -> custom theme /clientarea.php -> six /submitticket.php -> six etc. (Working on session is not possible because the very same logged user would require to use custom them if he is visiting knowledgebase.php, and six in clientarea.php ... ) Any idea?

I would like a single page being loaded using a different theme. I know it's somehow possible, because there's a hook by ModulesGarden ( https://www.modulesgarden.com/products/whmcs/geolocation-hook ) that already do it (switching the theme according the language set). I tried to dig into ModulesGarden's code (this hook is provided as source), but it's far beyond my capabilities, and I went lost... 😞 I just saw that also @MrGettingRatherFrustrated has a similar issue (he would like to switch language and currency), and also him went lost in digging ModulesGarden's code... So I realized that also WHMCS documentation is very poor about this: it seems that - somehow - it's possible in a hook to re-set system variables defining template, currency and language, but there's no "how to" about... 😞 Any idea on how to do it?