Leaderboard

Good points, electric. You've highlighted exactly why we've designed Blesta to be so modular and customizable. Of course, I'm always surprised when people say Blesta is basic or simple, or otherwise lacking in features when compared to some other systems. It makes me smile, knowing we did a good job with not overwhelming the user. But it also means we may not be conveying all of the features of Blesta to users that are used to systems that have cut corners. Take for example service terms. Most systems support one time, monthly, bimonthly, annually, and biannually. Blesta supports hundreds of thousands of possible terms! Other systems supporting only email delivery of invoices. Blesta supports email, fax, and postal mail (yes, invoices that actually fit into double-windowed envelopes and can be printed through Blesta or mailed directly from Blesta) Other systems have a basic API that was added as an after thought. Blesta's API automatically grows with every release, and with every plugin installed. Multi-company,... the list goes on. While I can definitely see how someone used to another system might notice some things currently unavailable, the net result is Blesta is more featureful overall; and growing daily.

It becomes apparent when you create a custom theme with stark colours to differentiate between "Navigation Text Color" and "Navigation Text Active Color" that the "Return to portal" and "Log in" buttons are back to front in their colours. To illustrate, I create a theme with these colours for the Navigation text: It appears like this: As you can see, the "Return to portal" and "Log in" buttons are using the "Navigation Text Active Color" even though they are not active (in contrast, the bar underneath is behaving correctly). When looking in the CSS (app\views\client\default\css\theme.css), if you look carefully it is apparent that it is back to front in the code. As it stands, this is how the code is: .login_sec .button a { color:#theme_navigation_text_active_color;} .login_sec .button a:hover { color:#theme_navigation_text_color;} However, it should be: .login_sec .button a { color:#theme_navigation_text_color;} .login_sec .button a:hover { color:#theme_navigation_text_active_color;} With the css corrected, the "Return to portal" and "Log in" then use the correct colours:

Either use "|/usr/bin/php /path/to/script.php" in your ~/.forward Or if you want to continue using just "|/path/to/script.php" like you have now, open the PHP file and add a hashbang as the first line of the file. Don't forget the bang or it will be treated as comment, and your file will be executed as a normal sh shell script, which seems to be happening now. #!/usr/bin/php

If it's a trial you need to get Paul to re issue it else the company you got the license from needs to re issue it as it's stuck to the IP, username and the directory

FYI, order forms and pay invoice pages have been completely reworked for version 3.2, taking into consideration feedback we've received regarding offline payments.

Having lots of modules, plugins, and features is only nice if you actually need them. If WHMCS does something that Blesta doesn't, and you actually *need* that feature... then go for it. Use WHMCS. (And be sure to let the Blesta developers know about the feature you needed, so they can be aware of it.) Otherwise... if you don't actually need all those features and functions that WHMCS has... it is just software bloat and adds no real value to your business. In that case, then you should choose the software that meets your needs, and gives you the best sense of trust and partnership. Do you trust the WHMCS company? Do they seem like the kind of company you want to rely on for the most important and critical part of your business? (Billing, customer management, etc...) Software features is just one part of making the decision. If you don't actually *need* the many features included with WHMCS, then why include those features in your decision?

Edit the following file: /components/modules/logicboxes/config/logicboxes.php

In short, you need to take the payment as a transaction and then apply it to the invoice.

Man I have just the client for this!