Paul

A screenshot would be nice.

It should be your API password, not the password you log in with. Anything show up in their reporting when trying to send an email? Try the manual invoice delivery option on a client profile page, click the check box next to an invoice and try sending a copy to yourself. Do you get any errors?

Do you have port 587 egress open at your firewall? We use Mandrill ourselves and have the following options selected: Delivery Method: SMTP SMTP Security: TLS SMTP Host: smtp.mandrillapp.com SMTP Port: 587 SMTP User: (Your username, usually your email address) SMTP Password: (Your mandrill password) If the port is open, and the settings are correct, I don't see any reason this shouldn't work. It doesn't require any special PHP extensions, as long as there aren't PHP functions in the disabled list in your php.ini that might affect this it should work.

Does Multicraft default to port 25565 if no other servers exist on the IP? Since the default behavior was that it increments the port number, I would assume so. People paying for a dedicated IP address are going to typically expect it to be on the default port.

Invoices are not immediately sent out via email unless you check the box on a client profile page and click the button to send it. There is an entire invoice delivery system that can send via email, paper, fax, and postal mail. The cron delivers invoices, and by default this occurs every 5 minutes when the cron runs. See Settings > Company > Automation > Deliver Invoices. If you are creating an invoice manually and want to send it right away, uncheck the deliver box, then manually send it after it's created by clicking the checkbox next to the invoice and submitting the form on the client's profile page.

Transactions are intended for receivables only. All customer payments should be recorded as a transaction. If the entire amount of a transaction is not applied to one or more invoices, then the remainder is considered an account credit. By default, this credit is automatically applied to any future open invoices. I'm not sure if that answers your question. In short, if you want to record transactions so that they can be applied to invoices -- great! If not, be aware than transactions that are not applied to invoices are counted as credits.

It will be in 3.3, and 3.3 is nearing beta release.

A recurring invoice is a good way to go! That's what I would do if it were a consistent retainer type.

I PM'd you a trial key to use, let me know if you have any trouble.

You MUST set a cron key under Settings > System > Automation. Then call it like so.. http://www.cfmldeveloper.com/billing/index.php/cron/?cron_key=CRONKEY WHERE CRONKEY is your cron key as displayed under "Updated Cron Key".

Blesta bills recurring services in advance rather than in arrears, however if you're billing for work manually there should be no problem with that. For example, do work during June, then bill on July 1st for that work, you can enter whatever date you want for those tasks.

.htaccess and mod_rewrite are not required. Without it, everything just begins with index.php. It's not a problem. You come up with some mind boggling analogies Mike, lol.

UPDATE: This extension should be fine now, you can ignore this post. We do not recommend installing this plugin in its current form. Users have reported the Tools page displays a 404 error, even after uninstalling the plugin. If you are experiencing these issues, try removing the plugin files from the server. I'll change the subject back if the author corrects this issue.

I sent you a trial key via PM.

Did you have the "Use Module" box checked? If so, try again unchecking the box instead.

A short list of common tags should be displayed in the Package above the WYSIWYG editor for the welcome email. The tags related to the service depend largely on the module being used, here's an example of tags available for cPanel -- http://docs.blesta.com/display/user/cPanel#cPanel-WelcomeEmail Click "Additional Tags" for a more complete list. What module are you using?

Here are the docs on setting up a cron job - http://docs.blesta.com/display/user/Installing+Blesta#InstallingBlesta-4.SetupaCronJob If you plan to run via a GET request, you'll be interested in this:

We understand there is a legitimate need to be able to manually apply credits to future invoices, and not have them be applied automatically. This has been implemented for version 3.3, and will be part of that release. Are there any other items that you're concerned about?

Added!

Added!

Looks nice, do you want to enter it?

Looks nice but I think a fully featured plugin and set of modules for Blesta would work best. Focus on what makes GSP's unique and let Blesta handle the rest. But, if you do develop it as a standalone panel, you can still write a module for Blesta.

I've responded to both of your threads. The biggest issue it seems like you have is being able to manually apply credits, but there is a work around for that, which I described. If you have "Automatically Apply Loose Credits" checked under Settings > Company > Billing/Payment, then Blesta will apply overpayments/credits automatically to the oldest invoices first. Some people don't want credits to be applied automatically, so you can uncheck this option. In 3.3, you will then be able to manually apply credits as an admin, and clients will be able to as well during checkout on an order form, or when making payment for an invoice in the client area. Most people are content with automatic application of credits, so it hasn't got much attention, but if you want credits to be applied manually, then 3.3 will solve that for you. It's also important to note that when an admin or client makes a payment, they can pay multiple invoices at one time, all of them, or just specific ones in specific amounts.

Click the "Manage" link for their service in their client profile. Then select to change the renew date, and set the renew date to the end of the term for which they have paid. Then, manually create an invoice under Actions "Create Invoice" for that amount. Word the line item however you like, something like "Prepaid service xyz through date".

We hope to have 3.3 out soon. What I suggest doing is voiding the transaction (In Blesta only, do not check the use gateway checkbox if payment was made through a gateway) and then re-recording it. If you go to "Record Payment" under Actions, you can add the payment back in manually and apply exactly how much of that payment to which invoices you want. Just enter the same transaction amount, and transaction number