atcynthia

I purchased and installed this module the beginning of this month... can't seem to get it to work properly and the knowledgebase is basic/limited. I've reached out to Webfrigate multiple times with questions, including 3 difference support tickets. I haven't heard peep. I thought, oh well, nothing ventured nothing gained. I'll just remove my credit card... can't. Is that legal? Guess I'll have to dispute any charges.

We stopped upgrading WHMCS just after Autorelease was disabled because it "broke" the way we were using WHMCS servers. We've had other issues with upgrades, so we just stopped upgrading. However, I have read some posts that lead me to believe that Autorelease may have been re-enabled. Is this true?

We use the ticket creation functionality of AutoRelease in our products which were then linked to the servers for reporting purposes as well. The other modules don't have the ticket creation functionality that we need. I believe I looked at every single module for this option. If someone sees something that I did not, I would love to hear about it.

I guess it depends on your perspective. In my case, its removal has created a great deal of work for me. I believe I explained in my earlier post but allow me further explain how we used autorelease: 1. to initiate actions through auto-ticket creation 2. products (services) were linked to servers so that we could mass mail based on a server 3. products were linked to servers so that we could audit the services on each server 4. provided a quick view of the number of services on a server. Obviously this setup is a precursor to automation... we aren't quite there yet. It was a very unfortunate programming change for us.

According to a response from WHMCS support, products/services with 'autorelease' as a module setting cannot be linked to a server... "As a module with no external communication, no servers need ever be created assigned to the AutoRelease module as they would serve no purpose. Only products should be assigned to this module. It is because of this their removal from the Server configuration page was made. If your business operations necessitate services being assigned to a service, I recommend creating a provisioning module of your own: http://docs.whmcs.com/Provisioning_Module_Developer_Docs "

Autorelease is not an option in the server config. Server types start with "Castcontrol" in alpha order. Autorelease is only available in the product config. I could use one of the other server options and then link the servers and products, but I need to use autorelease for its functionality.

We ran into this as well. We have been using autorelease in the product to initiate actions through auto-ticket creation. We also tie our products to servers so that we can mass mail based on a server type. Now that autorelease is not an option in the servers, we can't tie our products to a server. This has created a real problem for us.

We think we have narrowed it down to a conflict with our custom invoice. We have reverted to the standard invoice until we can identify the specific issue with the custom invoice.

Major bugs happening with v5.3.3 (just updated last night)... system is double posting payments, not sending automatic emails confirming payment, internal server errors occurring when attempting to view PDF invoices and when attempting to manually send payment confirmation email, over payment posted does not reflect credit on the account - that's what we've discovered so far. Yikes!!

Did the account have a cancellation pending (e.g. the auto-terminate was checked)? We are an ISP and have been dealing with issues with suspend and 'auto-terminate' combined as follows: We sometimes need to put a customer on ‘vacation hold’. In the ISP world we call these suspends. Well we ran into trouble with suspending accounts because it does not stop billing and it causes late notices and suspend for non-payment emails to be sent. I am thinking the solution is to use the 'auto-terminate'. This stops the billing from cycling, leaves the account in 'open cancellations' and the service active. The problem is the automated suspend. Oddly, WHMCS will suspend the service at the selected automation time period and send a suspend email even when an account has a zero balance. The only solution to this that I can see is to do the following: - Set the account to 'auto-terminate' at the end of the cycle with the reason 'vacation hold' & thus preventing future invoicing. - Disable the account from receiving late notices in profile. These accounts will appear in 'open cancellations' where we can monitor them. When the client wants to reactivate: - remove the auto-terminate - set the next billing date to the appropriate date to start new invoicing - remove the disabled late notices in the profile I'm still exploring this issue and hope this will work. I don't think it will be much good for us once we get into scripting service activations, suspensions (what we consider vacation hold) and terminations.