All Activity

So what did you mean when you said: You said it works and then said it doesn't work. Then you said it doesn't work. I am not trying to back you into a corner. I am simply trying to understand.

Hi @Ezyhosting, A few years ago GoCardless changed the formatting of their redirect URLs. Accordingly V8.5.2 and above are updated to accommodate this new format: MODULE-7849 — Prevent erroneous failure on receipt of new url schema for GoCardless manadates https://docs.whmcs.com/releases/8-5/8-5-change-log/#852-security

Unbelievable cmsbased.net Today I received an invoice for a service. It was supposed to be a one-time payment, but now they're trying to charge again for "Support" that doesn't exist. They never responded to the single ticket I submitted, despite repeated follow-ups. They're forcing me to cancel my bank card because I can't manage it through their system. This is a *—at least in my country, it's reportable. It's a disgrace to the community. Happy Holidays.

I have changed the redirect_map in the main.js of my template, and it has been fixed. After changing the product groups in the admin panel, I had to change the mapping url here too. Because it was mapping to the previous groups. I have tried this one you suggested, too. But both ordering a new service and store are linking to: /cart But thank you for your suggestion

Hi all, I'm still running an owned version of WHMCS 7.8.3 It was working perfectly untill I decided to do a fresh install. I,m using gocardless as the payment method. I can retrieve mandates from the payments gateway so its communicating with GoCardless. When Setting up a mandate, it gives the error below --------------------------------------------- Oops! Something went wrong and we couldn't process your request. Please go back to the previous page and try again. Error: Invalid filename for redirect: https://pay.gocardless.com/billing/static/flow?id=BRF01KD19RJK4NAJ48TYHZ720ZRVTC96 ---------------------------------------------- However, if I enter that url directly into the browser, it works perfectly. I suspect I'm missing some patch that may have been made available previously. Does anyone know of what the patch was, and if so where I can get a copy of it from? Thanks.

Hi @zomex, I'm pleased to hear you were able to get the example code working. I can confirm from the page history, that at the time of writing, the example code on the page has not changed since 2016.

The hook doc I linked to in this thread was not working at the time of the v9 RC. The code was quietly updated, you are now implying that the code sample was working since v6 and now in v9 but the code was not working in v9 which is the reason I created this post. The quietly new updated code does now work in v9.

Hi @zomex, As part of the upgrade to the Smarty template engine in WHMCS v9.0, the legacy variable $template is no longer available and template_object is not exposed. The note on the documentation page will be updated to reflect this. We have recommend that all custom PHP logic be performed via hooks since WHMCS v6, and the example on this page works in 9.0 too.

Hey hmaddy, It is possible that some files are missing or incorrect in your installation. Likely files from different versions are present at the same time. Raise up a ticket to our support and our team will happily assist you!

Hey negin! I believe you could use something as the following? {* SERVICES *} <a class="{if $filename eq 'clientarea' && $smarty.get.action eq 'services'}active{/if}"> {* STORE (cart root + product groups) *} <a class="{if $filename eq 'cart'}active{/if}"> You can narrow them depending on the active file.

If you tick the "Debugging" do you get any additional errors in your logs?

I was using cPanel hosting, but it's not good for HTML5. I had to get a dedicated server and Cloudflare.

Hey Fabio! Have you managed to get this sorted? This warning usually means that the PHP version used by the web interface and the PHP version used by the system cron are not the same. This can happen when multiple PHP versions are present, or when the cron job is still pointing to an older PHP binary. To troubleshoot this: Go to Utilities > System > PHP Info and check the Loaded Configuration File to confirm which PHP version the web server is using. Then check which PHP binary is being used by the cron (CLI). Compare the PHP version and the php.ini file used by both to make sure they match. If they don’t, the cron command needs to be updated to explicitly call the same PHP version as the web server, or your system administrator can adjust the defaults accordingly. Also note that the warning won’t clear immediately. WHMCS only re-evaluates this check after the next successful daily cron run. You can find more details in our documentation here: https://docs.whmcs.com/8-13/system/automation/cron-tutorials/resolve-a-cron-php-mismatch/ In short, WHMCS is running under one PHP version, while the cron job is likely using another. Once both are aligned, the warning and the cron issues should be resolved by the next daily run. If needed, our team can take a closer look, just open a ticket and we’ll be happy to help.

Hey Leonel! This usually means you will need your mail server configuration to allow connections to external SMTP servers. And/Or whitelist your WHMCS's IP. You can also get further information by checking the "Debugging" box when clicking on Configure Mail Provider.

Modules Stack developed the advanced Credit History Module for the WHMCS platform. Credit History for WHMCS lets clients easily view and manage their credit activity from the client area, including purchased credits, applied credits, and detailed invoice tracking for full transparency and better account control. Check more details here - https://members.modulesstack.com/index.php?m=product_page&pid=7&name=credit-history-for-whmcs

That’s normal behavior. The Login to DirectAdmin (SSO) button doesn’t sync passwords. If the password is changed directly in DirectAdmin, WHMCS can’t auto-log in and will redirect to the DirectAdmin login page instead. This is expected in newer WHMCS versions.

I must have something set up incorrectly because the Login to DirectAdmin button doesn't work if the passwords don't match. If the client changes their password on DirectAdmin then the button only directs them to the login screen on the DirectAdmin server.

Thanks for the report and taking part in the pre-release testing. We have opened case WHMCS-24694 to resolve this in the stable release. In the meantime you can switch from the Nexus theme to Twenty One or Six.

As the Release Candidate has now been published, I have split the subsequent commentary into individual threads by corresponding topic in the 9.0 RC Discussion board: https://whmcs.community/forum/660-whmcs-90-rc-discussion/ As such this thread has server its purpose so will be closed,

Hi @TheHostingHeroes @andp97, Thanks for the reports and taking part in the pre-release testing, we have updated the links in both these locations now,

No one is talking about Nexus @John. That's a optional feature. Us developers are frustrated about the situation due to this being a major standards update. The update itself is good, we all welcome improved standards. But almost all modules will need to be updated, you're rushing the update through as quickly as possible. To rub salt in the wounds you chose to do this during the holidays. It's so crazy it's almost laughable. And you try to justify this decision rather than accept that it wasn't a wise idea.

@DennisHermannsen, You can self-reissue your development license via the client area. No need to contact Customer Service for that task.

Exactly. Huge update for developers and they choose to rush it through during the holidays. No beta period

Hi all, We welcome bug reports via https://bugs.whmcs.com as always. This time around, we made a conscious decision to skip a public beta and go straight to a Release Candidate with 9.0. Why? Because preparing a public beta includes documentation, support paths, and feedback loops takes significant time and resources from both product and engineering teams. Rather than slow the overall timeline, we focused our efforts on delivering a more feature-rich, stable RC that gets you closer to the final experience. We didn’t make this call in a vacuum, members of our UX Research Group are instrumental in guiding the design of the Nexus Cart. We ran a closed beta with select partners and hosted live demos at CloudFest USA, where we gathered in-depth, face-to-face feedback. That input was incredibly valuable, and we used it to help shape the current WHMCS 9.0 RC.

... and contact WHMCS support to have the development licensed reissued. ... and then rename the directory back to make your development installation match your production installation as close as possible, once this issue is fixed, and then contact WHMCS support to have the license reissued again. @WHMCS John WHMCS really goofed this RC. It's released just before the holidays and will hit stable very shortly after everyone gets back to work. I hope you understand why developers are frustrated with this.