Tyson

I think "Offline Payment" is the name of the gateway. Gateways are only shown in the language they are installed in. So updating the language definition would not take effect for multiple languages at the moment. However, if you only support one language, you can translate that in the gateway's language file and uninstall/reinstall the gateway in Blesta so that it will take effect.

You were probably experiencing this bug, so it would be best to upgrade Blesta.

This gateway is available in v3.6.0, renamed Converge (CORE-1312).

The box won't appear in the client UI if only one option is available starting in v3.6.0 (CORE-1467).

Payment types can differentiate between credit/debit in v3.6.0 (CORE-1479), and those that are 'credit' will not be counted toward revenue (CORE-1480). You can configure payment types under [settings] -> [system] -> [General] -> [Payment Types]. By default, only "In House Credit" will be set as credit.

cPanel account usernames will allow for lengths up to 16 characters in v3.6.0 (CORE-1516).

Blesta will come with a BrainTree gateway in v3.6.0 (CORE-1598). However, unlike ChrisB's BrainTree gateway, it will not initially support offsite credit card processing.

The length of the company name set for contacts has increased from 64 to 128 characters in v3.6.0 (CORE-1623).

New payment accounts created will be set to autodebit automatically if one does not already exist--starting in v3.6.0 (CORE-1653).

The OP's request for invoice PDFs to be attached to the invoice reminder/late notice emails will be in v3.6.0 (CORE-1724).

The OP's original request has been added to v3.6.0 in CORE-1770 and CORE-1811.

This has been updated in v3.6.0 (CORE-1803) to use different language for the "Invoice Number" label in the PDF.

This is fixed for v3.6.0.

Are they logged in to Blesta? If so, link them to /your_blesta_installation/client/pay/method/INVOICE_ID to pay a specific invoice. If they're not logged in, you can create a link for them to pay a specific invoice without logging in by appending a GET parameter, "sid", to the URL I mentioned which contains a hash. You can find an example of this in the cron.

When a service is not paid by any means, PayPal or otherwise, it will be suspended automatically by cron according to your settings governing this effect. These settings can be found in one of two places: Under [settings] -> [billing/Payment] -> [invoice and Charge Options] if you are using your company settings. Or (optionally), under [settings] -> [Client Groups] -> (edit) if your client group overrides your company settings. Also, the cron task that performs this action must be enabled under [settings] -> [Automation].

The current behavior, where {num} starts back at one, is expected with the use of the other temporal tags {day}, {month}, and {year}. When the invoice is created, the formatting set on the invoice replaces these temporal tags with their current values. If you had "{num}-{month}", then the {num} would start over at 1 with the first invoice in every new month. Similarly "{num}-{year}" would start the number at 1 with the first invoice of every new year. To avoid having the {num} start at 1 again, you would have to stop using {day}, {month}, or {year} tags.

Why not update /config/blesta.php and set the 'results_per_page' for each of the admin/client paginations to what you want them to be set to? That sounds like the simplest solution.

1. Write a query to fetch client credit amounts. Credits are determined as transaction amounts received that have not been applied. 2. The system requires certain fields, like a last name. If you want to remove it, you can update the Clients model to ignore the rules. 3. Update the Emails model, send method, to fetch the client's phone number and set it as a tag in all email templates. Similarly, fetch the credits from the Transactions model, getCredits method. 4. Staff have access to companies and particular pages as defined in staff group permissions. You would have to add another layer of restriction to filter based on client groups and enforce that rule on all client pages.

Where in Blesta?

Problems with a hypervisor today, so some sites may be slow or unresponsive.

Using Bootstrap's Accordion would be nice. Otherwise you can use a simple jquery .show/.hide or .animate for a similar effect. In either case you'll need to update the template (under /plugins/order/views/..) and filter your package descriptions into an excerpt with a button that shows the full description or excerpt.

The cron log wouldn't contain anything regarding PayPal logs. You would find those under the `log_gateways` table instead.

I [unfortunately] read some of the comments from the thread that the OP linked, and I thought I was reading YouTube video comments. It contains the same typical troll-bashing behavior with an occassional reasonable comment sprinkled in every now and then. There were so many unreasonable and nonsensical arguments I had to close my browser window to prevent the stupidity from saturating my eyes.

I want the screenshots displayed larger too.

It seems like you're confusing two separate things: the cookie versus a POST request. Logging into Blesta will need to send the login credentials to the server, so there will be a POST request containing the username, password, and CSRF token. After successfully logging in, a cookie will be created with the session ID. I would suggest taking a closer look at the content of the cookie.