SwiftModders LLC

Hi Guys, I am working on updating one of my modules to allow file attachments. What is the recommended way to do this? Are we free to upload files how we see fit or should I try to leverage the file storage system WHMCS provides? I didn't see any documentation regarding file uploads for developers. I just wanted to make sure I was creating something that would be easy for my customers. Thanks in advance for your feedback and suggestions!

Version 1.0.7 is now available to download! This release is fully compatible with WHMCS 7.10+ Changelog: Support for Menu Manager (Beta) Support for Cookie Consent Popup Support for FontAwesome Pro Duotone Icons Added new option to auto-hide sidebar when viewing the cart Added proper alert link styles Improved the addon styles in the shopping cart Moved the contact us alert below the order summary Updated to FontAwesome 5.13.1 Added tooltips to header icon menu items Other minor design improvements Fixed a bug where the “Lights Out?” toggle shows when the “Dark Theme” is disabled LIMITED TIME OFFER FOR THE SPRING! Save 35% on any SwiftModders WHMCS Theme and Module! This offer does not require a promo code and is active immediately. This offer cannot be combined with any active promo code. Order the Allure WHMCS Theme | Learn More

I feel like I am probably talking to myself, but just in case anyone else is curious about the 4th paramter, it's email: clientId contactId passwordHash clientEmail Those are the 4 parameters currently being used for the generateClientLoginHash method. Unfortunately, this didn't solve my problem with Menu::context('client'), but it could be helpful for other developers. Ultimately, the issue I am having is I cannot figure out a way to pass Menu:context('client') as non-NULL. I would imagine that setting the UID and UPW in a session within WHMCS would generate a client object, but it doesn't. I'm not sure if there is another way around this.

Has anyone else noticed that the WHMCS\Authentication\Client::generateClientLoginHash() method now requires 4 parameters as opposed to 3? Does anyone have any clue as to what the 4 parameters are?

Hey Guys, I am attempting to create a client session and in the past I've always used: $_SESSION['uid'] = 1; This typically works fine if I wanted to grab some information specifically for a client, but that does not seem to work within some navbars that use: Menu::context('client'); I was wondering if there is a way to set a client session so that the navbar hooks will believe a client is currently running this session. I guess, ultimately, I want to know is there a better way to set a client session besides just setting the UID. Thanks for any advice!

No, they just informed they added a case for the issue.

Yes, I reported the issue to WHMCS and they have made a case for it to be fixed. The emailing everyday issue for me seems to stem from an older cron folder. I had to manually update it as it was misconfigured. Still the email marketer does not function the way it should. This is probably related to what gbotica said above. Your template field is reset every time you edit it. So it's possible you edited the rule and the template selected something else.

Hi All, I am trying to grab the primary (and secondary) navbar for a logged-in user from within my module. I'm trying to pull the object so I can store it for later use. I'm able to grab the navbar for a non-logged in user easily, but for some reason, it's not changing when I set the session UID to a specific client ID and run navbar hooks. Example: $_SESSION['uid'] = 1; $primaryNavbar = Menu::primaryNavbar(); $secondaryNavbar = Menu::secondaryNavbar(); run_hook('ClientAreaPrimaryNavbar', $primaryNavbar); run_hook('ClientAreaSecondaryNavbar', $secondaryNavbar); If I try to return the $primaryNavbar, it returns the non-logged in user. Is there a better way to set the user ID and grab what the $primaryNavbar would look like? Edit: I forgot to mention that I am trying to pull this information into the admin-side of my module, not the client-side (frontend).

Pricing Update for all SwiftModders WHMCS Themes: Going forward, all SwiftModders WHMCS Themes (including the Allure WHMCS Theme) will have a fixed renewal cost of $15 per year. This renewal is for support and updates and is optional. Your license will remain active for as long as you wish to have it, but you will not have access to premium support or the latest downloads. Lifetime licenses are available!

Pricing Update: The SwiftModders WHMCS Feature Requester Module is now a one-time license with an optional $15 per year renewal for support and updates. Thank you to all of my clients for their feedback and recommendations in making this change!

Has anyone else noticed that after the WHMCS 7.10 update that the Email Market no longer functions as expected? I woke up to some upset clients who received the same emails (after a 24-hour period) that should only be sent once. Does anyone else have a similar issue?

Version 1.0.6 is now available to download! Changelog: Support for WHMCS 7.10 Consolidated all customization options to the SwiftModders WHMCS Theme Installer LIMITED TIME OFFER FOR THE SPRING! Save 35% on any SwiftModders WHMCS Theme and Module! This offer does not require a promo code and is active immediately. This offer cannot be combined with any active promo code. Order the Allure WHMCS Theme | Learn More

I am very excited to announce my first stand-alone WHMCS Module, the SwiftModders WHMCS Feature Requester, is now available for purchase! This module will give your clients the ability to submit feature requests for your products and services from within WHMCS. The module allows for you to set up product groups and your clients will only be able to access feature requests for the products they actively own via the groups. There are also many more features that come with this initial release: Vote Up/Down Requests: All your customers and staff will be able to vote up or down specific feature requests they have access to view. Comments System: Each feature request will allow other customers or staff to respond and discuss the viability of the request. Anonymous Posting: For customers that want to maintain a level of privacy, enable the ability to post their feature requests and comments anonymously. Product Groups: Create specific product groups so your clients can only submit feature requests for the products they own. Moderation Queue: Require an admin approve submitted feature requests before being posted to the public. Request Categories: Setup feature request categories that can either be specific to a product group or globally used throughout the system. Email Preferences: Your customers will have easy access to disable specific email notifications from the feature requester module. Admin Role Centric: Using pre-built WHMCS admin roles, you can set permissions for specific actions like moderating, editing and deleting feature requests. User Rules & Ban System: Specify rules that your customers must follow before allowing them access to the feature requester system. For more information on the Feature Requester product, please visit the product page. For more information on how to use the Feature Requester module, please browse the documentation. If you have any pre-sales questions regarding the Feature Requester module, please do not hesitate to email sales@swiftmodders.com or use the live chat when available. For any technical issues with the product, please open a support ticket.

Thanks! I ended up coming up with my own solution, but this is definitely helpful information for everyone 🙂

Thank you to everyone who reached out with interest! I have created a new product page on SwiftModders for this upcoming module that you can find here: https://swiftmodders.com/products/whmcs-modules/swiftmodders-whmcs-feature-requester/ I'm also looking for a handful of BETA testers for the product. If you're interested, please apply here: https://swiftmodders.com/beta-tester-application/ All chosen BETA testers will receive a free copy of the product as a thank you for their time! Thank you again for your interest!