lostinspace

Ah, remembered what it was that fixed our issue: Had to create "/path/to/whmcs/modules/support"directory. Something to do with WHMCS looking for Kayako support integration (which we do not use). I can't remember if it was a post on the forums that led us there or our error logs or a little of both. It sprung up after upgrading to PHP 5.3.3. So yeah *shrugs*. EDIT: http://forum.whmcs.com/showthread.php?t=30701&highlight=modules%2Fsupport

Check to see if you have an error_log file in the directory from apache. I believe we fixed a similar issue by creating a missing directory found from the error logs.

Not since 4.0.2.

Domain Pricing (Bottom).

Reports > CSV Exports > Clients

Maybe you ran across it in this thread: http://forum.whmcs.com/showthread.php?t=16269

Hey folks, While I wait on a ticket response I thought I'd throw this out to the community for a pulse check. We've experienced the following issue since v4 update. When orders are paid with the Quantum Payment Gateway, WHMCS is doubling the transaction (same transaction number) in the system (transaction log shows two transactions with the same ID and invoices reflect two transactions). There is only one transaction sent to the actual gateway. The only real issue this is causing is applying double payments to new order invoices (second payment shows as credit). This is not happening when invoices are batched automatically nightly - only on initial orders. Anyone else experience this?

Hello, We've experienced an issue where flagged tickets are able to be searched and responded to by other admins. For example, ADMIN-A flags ticket for himself. ADMIN-B logs in, has no permissions under his role to view flagged tickets, but is able to search for the ticket ID that ADMIN-A flagged and take any action they wish from that point on. Is this by design? I would think that flagging a ticket should prevent other admins from responding to the ticket.

The way we've overcome this is to set a minimum order. So you could set a minimum of 2 slots (probably don't need less than that). Then you set the base price of the product according to the cost of a 2 slot server. Hope that helps.

Actually, I just tested this and the ticket was opened in both departments without issue. So what I said isn't true. However, the e-mail addresses in my test e-mail were terminated with a ";" and not a ",".

It's because it was sent to TWO departments.

Same here. The integration with WHMCS works very well.

We handle all CC processing directly through WHMCS (3.8.1). We recently received this e-mail from Quantum. Wondering if anyone else has received it? Just wondering if the Quatum module needs to be updated?

Actually, yes, people have requested some enhancements to the enom functions: http://forum.whmcs.com/showthread.php?t=15798 So you have an audience...

In the case of manually accepting credit cards using WHMCS I can see how WHMCS fits the PCI-DSS model. However, when utilizing a CC merchant gateway, I believe it changes the scenario - wouldn't you think?

Umm, reading through some of their site this seems more related to merchant gateways rather than billing software like WHMCS.

Perhaps these files are pre-suPHP? One thing that will certainly break scripts after suPHP implementation is old files owned by "nobody". You should give the files within the html directory a mass chown according to their correct owner. This would definately explain the issues you're seeing with files still requiring 777.

We're assuming there's going to be two notices; one from the SSL Company and one from WHMCS. Can't speak to specifics since none of our SSL customers that singed up through WHMCS will renew for a year ;o). We set ours up as a recurring package (1 and 2 year purchases). According to the wiki you can then set the years by the configurable option method but we found that that won't change the recurrence of the package. You then get a renewal date of one or two years regardless of the amount of years set in the configurable options. We thought about trying the onetime payment setting in the package but then found that the package won't renew. Simply having the automation of the SSL module was enough to trump the risk of not having more than two year SSL purchases so we chose not mess with it further.

Np. I know the wiki search doesn't always produce results for some reason so I dug for it since I knew it was definately in there somewhere.

Yep, if you're an enom reseller you can start using the module: http://wiki.whmcs.com/Enom_SSL_Certificates

How about editing the following in the language files: $_LANG["orderfreedomainappliesto"] = "applies to the following extensions only (This renders $$ of fees non-refundable)"; This then appears under the domain ordering options after they select their billing terms.

The only way to do it is to issue the domains as "transfers". Why didn't that work?

When you are viewing the pending order (after you add it) simply uncheck "send to registrar" (since you already have the domain) and "sent to client" so the customer doesn't get a second registration e-mail.

Place a transfer order for the domain.

{if $service_custom_field_dedicatedip} Dedicated IP: {$service_custom_field_dedicatedip} {/if} Where "dedicatedip" might be "Dedicated IP" in the custom field.