Cody

You can look at two different events (you'll need to create a plugin that can listen for these events).
 
One of the following:
Transactions.add Invoices.setClosed  
The first is triggered when a transaction is added. The second is triggered when an invoice is closed, which happens when it's paid. Sounds like you'd want to go with #2

If submitting your username at /admin/login/reset/ does not produce an email in the log_email table then the username you provided doesn't match any staff user. Remember, your username is not necessarily your email address. Look in the users table for your admin user. Note the id, then look in the staff table for a staff user with that same id set for the user_id field. If you don't find on, that user is not a staff member.

Turn error reporting to -1
 
in /config/blesta.php:
 
Configure::errorReporting(-1);

Yeah, you can change it. /plugin/order/views/templates/wizard/cart.pdt near the very bottom of that file.

With just a tiny bit of html you can make that happen. You'll just want to replace the checkbox I'm the order form template with a hidden field that has the same name and value.

Attached is the hotfix. Replace /app/models/emails.php with the attached file prior to running the upgrade. This issue only affects users running PHP 5.1 and 5.2.
emails.php

Hm. Sounds like a firewall issue on that port.

This is intentional behavior.

Rotation Policy controls the amount of time to retain most log data, cron log being the exception as that is controlled by the Blesta.cron_log_retention_days configuration.
 
Options that control what logs to delete can be found in the configuration. They include:
 
Blesta.auto_delete_accountaccess_logs
Blesta.auto_delete_contact_logs
Blesta.auto_delete_email_logs
Blesta.auto_delete_gateway_logs
Blesta.auto_delete_module_logs
Blesta.auto_delete_transaction_logs
Blesta.auto_delete_user_logs

Alternatively, you could create the service and choose not to invoice it, or edit the invoice after it is created to remove the setup fee line item.

No, the clients.id_value field is for display purposes only.

Already reported and fixed for 3.0.7.

That's the problem right there. See the article I linked in the manual in my last post.
With a passphrase set you can only batch payments, or do manual one time payments.

Try this:
 
Update /components/gateways/nonmerchant/_2checkout/_2checkout.php (line # 290)
 
from
 
        $order_number = ($this->ifSet($post['demo']) == "Y") ? "1" : $this->ifSet($this->meta['transaction_id']);  
to
 
        $order_number = ($this->ifSet($post['demo']) == "Y") ? "1" : $this->ifSet($post['order_number']);

Forcing HTTPS.
 
Since you made the redirect a 301 you might need to clear you'll probably need to clear your cache to see the change.

Find the user_id in the staff table, then look up that user_id in the users table.
 
The most common mistake for resetting passwords has been users entering their email address instead of their username when requesting a password reset. Be sure to use your username and you should receive the reset at the email address as listed in the users table.
 
In the event that you still don't receive the reset message, check the log_email table for the message. If it's in there you can copy/paste the URL out of the message into your browser.

The renew date is the date that the next invoice is due. In some instances you may want to create an invoice for today (2013-09-13), but you want the next invoice to be due on the 1st, so you set the renew date for 2013-10-01. If you set the term to 1 month, then another invoice will be generated on 2013-11-01, etc.
 
More details on Creating Invoices in the manual.

Disable ONLY_FULL_GROUP_BY.

Try the following:
 
open /app/models/gateway_manager.php and change (line 244):
 
                    if (substr($file, 0, 1) != "." && is_dir(COMPONENTDIR . "gateways" . DS . $file . DS . $gateway)) {  
to:
 
                    if (substr($gateway, 0, 1) != "." && is_dir(COMPONENTDIR . "gateways" . DS . $file . DS . $gateway)) {