Jump to content

All Activity

This stream auto-updates

  1. Today
  2. Hi Everyone, This thread is being locked due to the conversation getting out of hand. Could I please ask all members to review the WHMCS Community Guidelines.
  3. Hello everyone! I would like to introduce my digital marketing website, Thwahira Digital Muse. I provide digital marketing services to help businesses improve their online presence and reach their target audience. My services include: - Search Engine Optimization (SEO) - Social Media Marketing - Meta Ads - Website Development I created this website to showcase my services, skills and digital marketing work. You can visit my website here: https://thwahiradigitalmuse.com/ I would appreciate your feedback and suggestions. Thank you!
  4. Hi everyone, I wanted to take a moment to introduce web codeworks, our range of WHMCS modules. We've been using WHMCS within our own business for some time and, like many others, found there were certain specific features and improvements we wanted that weren't available out of the box. Rather than work around these limitations, we decided to develop our own modules. These were originally built to meet our own operational requirements, but we figured that if they're useful to us, they might be useful to other businesses running WHMCS too! We've therefore started making these modules commercially available under our web codeworks brand. Our current range includes: Feature Requests – Allow customers to submit, discuss and vote on feature suggestions, with the ability to track progress and provide updates. Enhanced Announcements – Extend the standard WHMCS announcements functionality with categories, tags and improved filtering. Enhanced Knowledgebase – Restrict knowledgebase categories based on the products a customer owns, ensuring relevant content is available to the right customers. Banner Manager – Display scheduled, colour-coded notices and announcements throughout the client area. Enhanced Status – Improve the WHMCS network status experience with service components, incident timelines and customer-specific service information. Enhanced Support – Combine a flexible service catalogue with secure information collection, detailed SLA reporting and administrator time tracking, all built around native WHMCS tickets. Contract Management – Manage the contract lifecycle directly within WHMCS, from template creation through to electronic signature. Publish versioned PDF agreements to clients, capture signatures and retain completed documents alongside supporting evidence. A little about our approach Our aim is to build practical extensions that improve the functionality already available and solve genuine day-to-day business challenges. As these modules originated from our own requirements, we've approached development from the perspective of actually using them to run a business, rather than simply building features to sell. We're continuing to develop and improve the range, with ongoing maintenance, compatibility updates and support. Take a look You can find out more about the modules, including features and pricing (including free 7 day trials), on our website: https://8b1b.co.uk/webcodeworks.php We're also listed on WHMCS Marketplace too. We'd be interested to hear what others think too, particularly whether you've encountered similar limitations in WHMCS or have suggestions for features that would make managing your business easier. Thanks for reading, and happy to answer any questions! 8b1b / web codeworks https://8b1b.co.uk/webcodeworks.php
  5. +1 to Damo on redirects and client communication. A few WHMCS-specific items that are easy to miss when the domain changes: Before switching Reissue the WHMCS licence for the new domain/folder in the WHMCS Members Area, otherwise the licence check fails as soon as the URL changes. SSL on the new domain, and keep SSL on the old one, because it still has to serve the redirects. SPF, DKIM and DMARC set up on the new domain before any mail goes out from it. The switch Update System URL (plus Domain / Logo URL) under System Settings > General Settings. Make the 301 keep the path and query string, so old invoice links in emails (viewinvoice.php?id=…) and bookmarks still work. Update callback/webhook URLs at your payment gateways (Stripe webhooks, PayPal IPN, etc.), plus any OAuth/SSO apps and API IP whitelists. If you pipe or import tickets by email, add the new support addresses and keep the old ones forwarding for a good while. After Send a client announcement and update email template footers and signatures. Keep the old domain and redirects for at least a year, because people find old invoice links years later. Check Utilities > Automation Status to confirm cron and automation still run normally. Billing email can move gradually: reply from the new address and keep the old one as an alias.
  6. Hi, The two do different jobs: Account Details > Language (also on the client's profile in admin) is the client's default language. WHMCS uses it for all emails and notifications sent to that client (invoices, ticket replies, service emails), and it's the language the client area loads in when they log in. The language picker in the client area changes the language for the current session, i.e. what they're looking at right now. Whether clients can use it depends on System Settings > General Settings > Localisation > Allow users to change language. So for a client who prefers French, set their profile language to French and their emails will go out in French, even if they never touch the picker. It's also handy for staff, because the client's preferred language shows on their profile and tickets.
  7. Hi Sudipto, That trace shows the updater failing during the file-update (Composer) step, but the actual error message isn't included. It's usually the first line above the trace, or you'll find it in Utilities > Logs > Activity Log right after the failed attempt. Could you post that line (with paths/secrets removed)? Meanwhile, these are the usual causes at that step: PHP 8.4: if the site runs on PHP 8.4, there's a known issue updating 9.1.0 → 9.1.1 on 8.4 (errors mentioning the illuminate package). Switch the domain to PHP 8.3, run the update, then switch back. See: https://whmcs.community/topic/367815-issue-with-updating-910-911-on-php-8427/ Update staging path: under Utilities > Update WHMCS > Configure Update Settings, the temporary path must exist, be writable by the PHP user, sit outside public_html, and have free disk space (roughly 3× your WHMCS install size). File ownership/permissions: after a migration or a restore done as root, some files may not be owned by your account user, so the updater can't overwrite them. Fix ownership of everything under the WHMCS folder. PHP limits: memory_limit of at least 256M and max_execution_time of 300+ during the update. ionCube Loader: must be a version that supports both the target WHMCS release and your PHP version. If it still fails, a manual update is safe: take a full file and database backup, download the full release zip from the WHMCS Members Area, upload it over your install (keep configuration.php and your custom admin folder name if you renamed it), then visit /install/ to run the database upgrade and delete the install folder afterwards.
  8. We set up redirects from the old to the new. It is straightforward with rewrites to cater for older formatted URLs Educate clients in all communications about the new url. Invoice notes, helpdesk auto replies, email signatures.
  9. Suppose a hosting business finally acquires its exact brand .com after years on a longer domain. I'd be tempted to redirect the new name first and leave the existing client area and billing email addresses alone for a while. Customers may have bookmarked the portal or still be opening links from old invoices. For anyone who's moved an established WHMCS business to a new domain, what kept bringing you back to the old address after the main move?
  10. My provisioning stopped working and I can’t seem to figure it out. Using Nxt panel and it has always worked until 2 weeks ago Everything fails now and can’t create new accounts etc or extend them
  11. Yesterday
  12. We run a small hosting outfit out of South Dakota, and WHMCS handles billing for a handful of small clients. Between that and the camper we take out on weekends, I ended up looking at replacing the toilet in the RV with an 18.5-inch Kohree model, and it got me thinking about how much of my setup I manage through WHMCS versus just keeping a note somewhere. What I am unsure about is whether it makes sense to log hardware and equipment purchases like this as billable or inventory items in WHMCS, or if that is overcomplicating a system that is really meant for hosting services. I do not want to create clutter in the client area for something unrelated to their hosting. Has anyone here used WHMCS for tracking non-hosting assets or add-on products? Curious how you structured it and whether it caused confusion with invoices.
  13. We have released a free, MIT licensed addon module that connects WHMCS to Affiliatant, an affiliate platform for merchants running their own programme. **What it does** - Reports every invoice, including renewals, each credited to the original referral rather than counted as a new sale from nobody. On a hosting book that is the difference between paying an affiliate once and paying them every year the customer stays. - Mirrors the affiliates you already have in WHMCS, so an existing programme does not start again from an empty list. - Reports refunds, from the gateway and entered by hand, so commission already recorded is reversed rather than left standing. - Mirrors clicks, commission and withdrawal requests from the WHMCS affiliate system. **How it sits beside the WHMCS affiliate system** It runs alongside. Nothing WHMCS does today stops working when the module is installed. WHMCS keeps calculating and paying its own commission, and those figures are recorded for comparison rather than sent, so no sale is counted twice. There is one setting that changes that, making Affiliatant the source of truth, and it is off until you turn it on. **Technical** - One codebase for WHMCS 8.x and 9.x. No Smarty, so the tags removed in 9.0 do not reach it. It never writes to an invoice, so invoice immutability does not affect it. - PHP 7.4 grammar, which runs unchanged on the 8.2 and 8.4 that WHMCS 9 wants. - Plain source. No ionCube, no licence key, no licence server, and nothing that calls home to decide whether it will run. - It adds one table of its own, a queue, so an event is retried rather than lost when an API call fails. - Four files. No composer dependencies. It runs on the WHMCS cron you already have. **What it costs** The addon is free. It needs an Affiliatant account, which is where the tracking, the commission rules, the fraud checks and the payout file live. Twenty attributed conversions a month are free with every feature and no card; above that it is a monthly subscription. Affiliatant never holds your money: it produces the file of who to pay and how much, and the payment leaves your own bank, PayPal or Wise account. **Known limits, stated up front** - WHMCS records an affiliate click as a raw hit with no link, no sub ID and no destination, so mirrored clicks carry only the affiliate. Links created in Affiliatant carry everything. - A refund processed only in your payment gateway is invisible to WHMCS and therefore to this module. Refund through WHMCS, or reverse it by hand. - Single source of truth is off by default. Until it is on, WHMCS and Affiliatant both accrue commission and you must pay from one of them only. Download: affiliatant.com/downloads/whmcs Source and licence are in the zip. Happy to answer questions here.
  14. Update: WHMCS Support confirmed this is a known issue, tracked as WHMCS-26898 (rounding in the return conversion). No ETA yet. Keep an eye on the release notes for that case number.
  15. We had to remove the charge.succeeded destination event as well because duplicate entries were getting recorded in the transaction list for "add funds" invoices. Automated or manual captures of standard invoices were not causing a duplicate entry which is why this was missed originally.
  16. Last week
  17. Hi all, The domain checker code provided under Utilities > Integration Code doesn’t work when added to an external page. This has been the case for a few WHMCS versions now. Could someone from WHMCS look into this? If the code needs updating, please update it in the admin area too, as people will understandably expect the supplied code to work. Has anyone else run into this or found a fix? Thanks, Jack
  18. Owned License ($30.00) - https://www.hardsoftcode.com/cart/link/stoat-notifications-for-whmcs/owned Source Code License ($200.00) - https://www.hardsoftcode.com/cart/link/stoat-notifications-for-whmcs/source
  19. Hi all, Since moving from the legacy Stripe module to Stripe Dynamic Payments (WHMCS 9.1.x), we see payments recorded 0.01 short (or over) when the invoice currency differs from the Stripe account’s settlement currency. Short payments leave the invoice Unpaid with a 0.01 balance, even though Stripe charged the customer the full amount. Setup WHMCS default/client currency: USD Stripe account settlement currency: EUR Convert To For Processing: None, so Stripe charges the customer in USD What happens Stripe charges the exact invoice amount in USD and converts it to EUR for the balance. Stripe Dynamic Payments then seems to take the EUR balance amount and convert it back with Stripe’s exchange rate, instead of recording the amount that was actually charged. Illustrative example: Invoice: USD 19.99, and Stripe charges USD 19.99 ✔ Balance transaction: EUR 18.26 (rate 0.9137) WHMCS records 18.26 / 0.9137 = 19.9847 → USD 19.98 Invoice stays Unpaid, balance 0.01 The fee is converted back the same way, which is fine. The payment amount should not be. How often The EUR amount is rounded to cents and then converted back, so roughly 1 in 10 payments is off by a cent whenever the exchange rate is below 1 (e.g. USD → EUR). About half of those underpay, leaving the invoice Unpaid. The other half overpay, adding 0.01 credit to the client. When the rate is above 1 (e.g. GBP → EUR), the error can’t reach a full cent. Legacy module did not do this With the same Stripe account and the same setup, the legacy Stripe module recorded hundreds of USD/GBP payments to the exact cent. With Stripe Dynamic Payments, our very first USD payment was already off, so this looks like a regression in the new module. Workarounds considered Manually adding a 0.01 payment: works, but it’s manual and easy to miss. Unpaid invoices also trigger reminders and overdue processing. Convert To For Processing = settlement currency: not a real option for us. It charges USD customers in EUR, so their bank converts the amount and often adds fees. The amount on their statement then no longer matches the invoice. WHMCS would also still have to convert the EUR payment back to the invoice currency, so the rounding issue might simply move. Adding a USD settlement account in Stripe would avoid the conversion entirely, but not everyone can or wants to do that. I’ve opened a support ticket with WHMCS but don't expect a fix anytime soon. Has anyone else run into this with Stripe Dynamic Payments? Does anyone have a better workaround, or know whether a fix is planned? Thanks!
  20. Hi everyone, I’m sharing the current lineup of WHMCS modules from HardSoftCode. They’re built for speed, security and easy day-to-day administration. Utilities Pages Manager ($65): build unlimited rich-content pages in the client area, including internal, PHP and standalone pages and reusable blocks. Advanced SEO Manager ($40): control meta tags, Open Graph, Twitter Cards, canonical URLs and schema.org data. Menu Manager ($40): manage the client area menus for both visitors and logged-in clients. Support Tools Support PIN Pro ($45): clients generate temporary numeric PINs so your team can verify identity by phone or chat. Staff Chat ($45): real-time chat inside the WHMCS admin area, with file sharing, mentions and search. Performance & Security Change User Password ($30): brings back the admin’s ability to change a user’s password in WHMCS 8, with every action logged. Delete/Close Account ($40): lets clients request account closure with password confirmation, optional captcha and email verification, and a grace period. Notifications Stoat Notifications ($30): connects the native WHMCS notification system to your Stoat workspace. Other Magic Login Link ($40): passwordless client login through a secure, time-limited link. Browse everything here: https://www.hardsoftcode.com/products I’d love your feedback. Which features are you missing in WHMCS? Reply with your ideas and I’ll consider them for future modules.
  21. Stoat Notifications for WHMCS connects the native WHMCS notification system to your Stoat workspace. Once installed, Stoat appears as a notification provider next to the built-in options. You create a notification rule, select Stoat, and WHMCS posts each matching event into the Stoat channel of your choice through a webhook. Stoat renders Markdown on the client side, so messages arrive formatted, with bold titles, linked headings, tidy attribute lists and colour-coded embeds, instead of a block of plain text. The module is built for teams that live in Stoat and want billing, support and system events in front of them without watching email or refreshing the admin area. A paid invoice, a new order, a support ticket or a failed payment can each go to a different channel with its own format, colour and sender identity. You can send a full message with an embed, a compact Markdown-only message, or an embed-only card, and choose per rule whether attributes such as client, invoice, service and department are included, shown one per line, or collapsed into a single inline row. Silent messages let low-priority events appear in the channel without pinging anyone. Setup is deliberately simple. There are no database changes and no addon activation step. Copy the Stoat folder into modules/notifications/, paste the webhook URL from your Stoat channel settings, and save. WHMCS immediately posts a connection test, and the test is always strict, so a missing SendMessages, SendEmbeds or Masquerade permission shows up while you configure the provider rather than the first time a real invoice is paid. Provider settings and notification rules are stored by WHMCS, so upgrades are as easy as replacing the folder and saving the configuration once. Reliability and security are treated as core features. Every webhook URL is validated before each request: HTTPS only, no embedded credentials, no query string or fragment, a correct webhook path, and a host limited to stoat.chat or *.stoat.chat unless you enable self-hosted mode. TLS is verified, redirects are not followed, and the webhook token is redacted from module log entries. Content, embed titles, descriptions and sender names are checked against Stoat's limits before sending, with Markdown-aware truncation that closes unfinished code blocks. Mentions such as @everyone, @here and @online are neutralised, so notification text can never ping an entire server. When Stoat rejects an optional feature, you decide the behaviour: fail loudly with Strict Delivery, or retry once without the rejected embed or masquerade. Stoat error types are mapped to clear, actionable messages, covering missing permissions, invalid tokens, slowmode and more. If you are moving from the Guilded notification module, the transition is easy. Decimal embed colours are converted to hex automatically, and attributes that Stoat embeds can't hold as separate fields are folded into the embed description as Markdown. Self-hosted Stoat instances are supported, and a full eight-page documentation site covers installation, permissions, settings, message formats, worked examples, security and troubleshooting. The Problem It Solves WHMCS events like new orders, paid invoices, support tickets and failed payments are easy to miss when they only land in email or the admin area. Teams that already work in Stoat have to check a second place, and generic webhook workarounds usually send plain, unformatted text that is hard to scan, can't be routed per event, and often leaves webhook URLs exposed in logs. What the Module Provides Stoat Notifications for WHMCS adds Stoat as a native provider in the WHMCS notification system. Create a notification rule, choose Stoat, and WHMCS posts formatted messages straight into your Stoat channel through a webhook. Each rule can use its own channel, format and colour, so billing, support and system alerts can go where they belong. There are no database changes and no addon activation. Copy the folder, paste your webhook URL, and save. Features Message delivery Three formats: Message + Embed (default), Message only, or Embed only Markdown rendering for titles, messages, and attribute labels and values Rich embeds with title, description, link and custom colour Optional silent messages that don't ping the channel Attributes (client, invoice, service, department and so on) shown as separate lines or on one inline row Routing and appearance Per-rule webhook override to send each rule to a different channel Optional custom sender name and avatar through Stoat masquerade Per-rule embed colour, with Guilded-style decimal colours converted to hex automatically Reliability Strict Delivery toggle: fail on a rejected feature, or retry once without it Embed-only notifications never degrade to an empty message Connection test on save, so missing permissions show up during setup Markdown-aware truncation that closes unfinished code blocks Configurable request timeout (1-30 seconds) Actionable error messages for Stoat errors such as missing permissions, invalid tokens and slowmode Security HTTPS only, with TLS verification and no redirect following Strict webhook URL validation before every request Host restricted to stoat.chat unless self-hosted mode is enabled Webhook token redacted from module logs @everyone, @here and @online mentions neutralised in notification text
  22. Update error Error: WHMCS\Installer\Update\Updater->performFileUpdate() at /home/user/domains/domain.com/public_html/domain/admin/update.php:0 WHMCS\Installer\Composer\ComposerUpdate->update() at /vendor/whmcs/whmcs-foundation/lib/Installer/Update/Updater.php:0 WHMCS\Installer\Composer\ComposerUpdate->doComposerCommand() at /home/user/domains/domain.com/public_html/domain.com/vendor/whmcs/whmcs-foundation/lib/Installer/Composer/ComposerUpdate.php:0 WHMCS\Installer\Composer\ComposerUpdate->{closure:WHMCS\Installer\Composer\ComposerUpdate::update():586}() at more......
  23. Hi Huzaifa, welcome to the WHMCS Community! Glad you joined us!
  24. Thank you! This absolutely helped me. Had the exact same issue. Also after the upgrade, and returning to php 8.4 I ran the WHMCS internal scan for php 8.4 compatibility and it came back all green, so maybe we're okay for the next update. Really appreciate you taking the time to post this.
  25. Though I appreciate the response, I also could have asked AI and copy/pasted the entire thing. All all of your replies I checked appear to be 100% AI generated, please don't bother replying to my posts, if possible.
  26. Hi everyone, We're planning to offer S3-compatible object storage services using our own Ceph RGW backend, with WHMCS handling customer management, provisioning, and billing. We're looking for an existing WHMCS integration module (official or third-party) that supports: Automatic provisioning of Ceph RGW S3 accounts Access key and secret key management Bucket and storage quota management Storage usage metering and billing Service suspension and termination We've searched the WHMCS Marketplace and Community community but haven't found a module specifically supporting Ceph RGW. Does anyone know of an existing module, or have experience integrating WHMCS with Ceph RGW? We're hoping to avoid developing a custom module from scratch. Any recommendations would be greatly appreciated. Thanks!
  1. Load more activity
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated