Jump to content

Keiro

Retired Forum Member
  • Posts

    117
  • Joined

  • Last visited

Everything posted by Keiro

  1. Fortunately for me, I've moved off of WHMCS. No way in hell am I moving back to WHMCS. And I won't offer WHMCS licenses to my clients. I voted for this. I was expecting them to accept the feature request. Not delete it and remove it from view. That simply tells me that they don't give a **************** about us, the people that use their software. Their actions will come back to bite them in the rear, sooner or later. Sooner or later, someone will sue WHMCS, and they will be found liable.
  2. ... Oooooh I must get ahold of this module. ;o I LOVE the ability to instantly and automatically detect spam. I already use Akismet and Stopforumspam's modules. Having both of them together is AWESOME.
  3. Annnd we've added it. Spent a while getting it to work... turns out it seems to be a WHMCS or module bug that was screwing up the template I was using. It was a major pain in the arse to track down because it wasn't obvious that the visual mode was breaking the templates... now that we've discovered the bug, we've passed it on up to IPGeek developers. That aside, it really does work exactly as advertised, once I was able to get it up and running with the help of one of their technicians. Fast response and I appreciated their patience in walking me through troubleshooting steps to trace down exactly where it was breaking. Thanks, IPGeek!
  4. Huh... I recently added a module from IPGeeks securing our password reset system. I'll have to buy this module as soon as we've enough funds available to secure a copy of this module. You should see if you can collaborate with IPGeeks with their password reset module and integrate that into your module?
  5. Gonna yell at the dev when he logs into the IRC... I know where he is now. LOL
  6. Not that I've seen. We could ask someone else to check into this and fix it for us.
  7. Nope. It breaks. I haven't been able to figure out how to update it, alas. So I've removed it until someone else updates it because I'm not a WHMCS dev.
  8. We've paid for this... it's something we're concerned about. We will be adding this to our billing system after we've updated it to 5.1.2.
  9. ... Quite a bit. I actually had a client complain about this last night. >_> Out of all the clients that we have, this was the first to have complained. ... And I expect him to not be the first as more clients join us. We need to change this. I'd like to reduce as much risk as possible. Something like this? It's very valuable, indeed...
  10. I have to admit, I giggled each time I saw those tickets... we've only had this done to us like 4-5 times... but each time, they were never able to get anything into our billing system. It delights me because I like the feeling of being a smug ******* that made damn sure that there weren't many ways of getting into our system. Likewise, nothing was affected, but I quad-checked just in case and had others check as well... all good. Pretty sure with my habit of upgrading a month after an update's been released has helped keep it safe. Though, when I heard of the exploit, I immediately updated after that, so I was pretty safe anyway at that point.
  11. Thanks, you've been really helpful with the KB upgrade... wasn't expecting a free upgrade, but I wouldn't say no to it. Resubscribed to yearly updates, though. Very awesome customer service. Edit: I notice some blank categories. Planning on filling those in later? Or...?
  12. ... I did not receive notifications for new articles. Er... well, I'll probably send in a support ticket for that at some point... Wait, is that why the KB articles are borked in my 5.0.x install right now? >_>
  13. Understandable. It looks incredibly like part of WHMCS. I had to doublecheck to see. I like the very slick integration you've made so that it looks the part. However, if we pay for this now, prior to release 5 of WHMCS, how are you handling updates to that? Oh wait, I just looked at the initial post which answers my question. Oops on my part, hahahaha. Understandable. We'll order this soon, but I'm not sure if I can do that today or in the next few days.
  14. Really? It's not a monthly payment? One-time only?
  15. Heh, I am not getting updates on any thread I subscribe to in here. so I feel your pain. I'll be watching this thread for the new update.
  16. Posting in here so I can grab it off my profile because I know threads tend to get bumped off here. Also, that's a beautiful integration. If I didn't know better, I'd have said you used the Client version of the very same knowledgebase to make the admin-area only one! Did you? If you did, I'm gonna have to say, "WHMCS, why, oh, why did you not include it yourselves?" And how easy/difficult was it? Edit: Can I get a private version to check out? If that's not possible, would you be willing to provide one to me if I can send over the funds next month? I don't quite have the funds to purchase the module right now, but I will next month. However, we do need this asap.
  17. An internal wiki would be AWESOME for us as well. I'd be interested in purchasing something like this. We NEED something like this for us. WHMCS should integrate one.
  18. No option to permanently remove it? Why not set a permanent option equivalent to what you would've paid had you went to the unowned license first, that way you still get the money either way permanently?
  19. Could always PM it. I understand what you're saying, though. Really? I'll have to check on that, myself. We'll know here shortly whether or not it'll work for us as we modify it.
  20. I actually had thought about that. I also thought, "Wait... why don't we change a few of those fields to a drop-down type box thing with a text field?" Example: DRAC. Not all of us use DRAC. Why not change that particular item to a dropdown box, and list the options as: DRAC, IPMI, $OTHERITEMHERE and use the text field as a method to fill in details about said item. I'll be looking into this, myself, but it should be relatively trivial to do, I hope. Serverprodigy: What was the specific mod_sec rule so we can also know if we encounter those issues?
  21. ... Holy crap, I'm so downloading this when it's updated. For now, I'll just grab the current version. Edit: I just installed this. Worked beautifully. However, I see that there's a missing field: Datacenter. I work with two datacenter providers for my servers. It'd be nice to also be able to add that detail to each server as needed when adding new servers. Second edit: You also may want to add IPMI as a field, as well, as I use Supermicro servers.
  22. Sure. I'll use a screenshot instead. Setup -> Automation Settings -> Invoice Generation settings is as follows: Invoice dates as follows: Hold on, let me resize the images so they don't break the tables. >_> Edit: Images resized. Wow, I need to take into account my resolution sizes when taking screenshots. Anyways, as you can see in the screenshot above, a client has been invoiced several times, earlier than planned. Client's usual billing date is on the 1st. However, due to paying early, we have had to move his billing date a month forward. I do not know why this is the case, even with changing the new invoice to be generated. Why not add the option to not generate new invoices until a given point in time for that client?
  23. Right, so, I've got the following info: We're using WHMCS Version: 4.5.2 The issue is thus: Editing a client's details, particularly the due date and/or the due amount, either backwards or forwards, seems to break the billing. It seems that it'll then ignore the due dates and continue sending notices monthly as if you've never edited it in the first place. Specifically: Edit due date for client to pay to a month forward. Set it to not suspend just in case the billing system decides to be funny and bill then suspend anyway. Paranoid? Maybe, but I'd rather be safe. Let's say, for example, last month I set the client's due date to be in October, on the 1st, due to the invoice having already been paid for September. Last month gets closer to this month, WHMCS sends an invoice for this month... again, despite the client having already gotten a paid invoice, and despit the due date being moved a month forward, to October. WTF? Is anyone else encountering this seemingly strange behaviour? Or is it just me and I've somehow managed to misconfigure this? It wasn't happening until I started editing client due dates and the like. If anyone else, my google and search-fu seems to be failing me... so it has to be either A. misconfiguration, or B. some serious bug that hasn't been reported, or if it has, I'm not seeing anything being talked about it.
  24. ... Looking at the Widget documentation, it looks far easier to work with. I think we'll use that option. Thanks for posting that, Jeremy, and glad to be of help to others for posting this and asking the same question. I'll pass this on to my web designer that I mentioned in the OP, he just barely signed on with us, so I'll be teaching him how to play with our billing system and work it into our site design. Though, to ensure I get what you said, I use that script bit and change the pid for each product and let it dynamically pull the price via the widget, correct? This shouldn't interfere with the ordering links, if I recall correctly, so that shouldn't be too much of an issue to pass to our designer. Edit: Looking at the documentation again, all of the Widget provides us with basically everything we need to provide for all of our products. Awesome, this should reduce our designer's work.
  25. So, I have a web designer working on our design. I forget, how'd one integrate pricing from a subdomain that WHMCS is installed on, to a main domain that is just static HTML and the like? If possible, I'd like to ensure that the pricing is updated automatically... whatever that day's pricing is, it's automatically shown without us having to update pricing on the pages themselves each time we change it. I'd appreciate it. Thanks!
×
×
  • 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