Leaderboard

I think we need some more discussion on this. It would be great if users of other currencies could chime in here about their country/currency requirements. The easiest solution, I think, would be when we calculate invoice totals (Invoices::calcLineTotals()) we format the values in decimal format to limit the length of the fractional portion. For example, the total 1234.5600 in "# ###" format is displayed as 1 235 in currency format. However, perhaps the total value should instead be rounded as well to 1235. Since this may vary from country to country and currency to currency, perhaps it should be a system config option or currency setting.

It use to display it in the field, but we changed this because passwords should be in password fields. However, it's a 2 step fix the 2nd step is to design a modal popup that allows you to see the password and possibly alter how it's generated. (length, characters, etc). We just haven't got to the 2nd step yet, so this feature at the moment is admittedly less useful.

Sorry, wasn't holding back, just was busy! First, I didn't realize that it was Blesta that was adding the /client/ to the end of the url. That's the same url I installed my old WHMCS configuration and I was fixated that it was getting it from the whmcs import. That was my fault. I first uninstalled the portal module, changed the host url to the main domain, not the sub domain, then changed it back to the sub domain, and reinstalled the portal module. I don't know what it did, but it fixed it. I don't know if it just cleaned up the database entry or corrected the issue after the import from whmcs. Whatever it did, it fixed it and it works and the first payment with Blesta came in today with no hitches. I'll keep whmcs for one more month, just in case, but it looks like I'm fully converted!

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.

The next release is 3.0.3, which is a patch release. Patch releases don't contain new features, so it won't be in there. It might make it in 3.1.0, but that depends entirely on the type of feedback we get, since this issue is still open for discussion.

Here's my first set of logs (think my last response was from the 2nd log): Input: https://httpapi.com/api/customers/search.json a:5:{s:8:"username";s:16:"xxxxxxxx";s:13:"no-of-records";i:10;s:7:"page-no";i:1;s:11:"auth-userid";s:6:"xxxxxxxxxxx";s:7:"api-key";s:32:"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx";} (SUCCESS) Output: https://httpapi.com/api/customers/search.json {"status":"ERROR","message":"Method Not Allowed. Use GET"} (ERROR) Input: https://httpapi.com/api/customers/signup.json a:16:{s:4:"name";s:10:"xxxxxxxx";s:7:"company";s:14:"Not Applicable";s:5:"email";s:16:"xxxxxxxx";s:14:"address-line-1";s:11:"PO Box xxxxx";s:14:"address-line-2";s:0:"";s:4:"city";s:6:"xxxxx";s:5:"state";s:2:"xx";s:7:"zipcode";s:5:"xxxxx";s:7:"country";s:2:"US";s:8:"phone-cc";s:1:"1";s:5:"phone";s:7:"1111111";s:8:"username";s:16:"xxxxxxxx";s:6:"passwd";s:15:"xxxxxxxxxxxxx";s:9:"lang-pref";s:2:"en";s:11:"auth-userid";s:6:"xxxxxxxxx";s:7:"api-key";s:32:"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx";} (SUCCESS) Output: https://httpapi.com/api/customers/signup.json 10067263 (SUCCESS) Input: https://httpapi.com/api/contacts/add.json a:15:{s:4:"name";s:10:"xxxxxxx";s:7:"company";s:14:"Not Applicable";s:5:"email";s:16:"xxxxxxx";s:14:"address-line-1";s:11:"xxxx";s:14:"address-line-2";s:0:"";s:4:"city";s:6:"xxxx";s:5:"state";s:2:"xx";s:7:"zipcode";s:5:"xxxxx";s:7:"country";s:2:"US";s:8:"phone-cc";s:1:"1";s:5:"phone";s:7:"1111111";s:4:"type";s:7:"Contact";s:11:"customer-id";N;s:11:"auth-userid";s:6:"xxxxxx";s:7:"api-key";s:32:"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx";} (SUCCESS) Output: https://httpapi.com/api/contacts/add.json {"status":"ERROR","message":"Required parameter missing: customer-id"} (ERROR) (The logs repeated this message 6 times) I created this by having an existing customer and going Client -->> Browse -->> Select Customer -->> Add Service -->> Choose Package (Domain Registration) -->> Then selected do not invoice, do not provision using logic boxes module and do not send email to customer and I selected 1 year term. Also selected Status "Active" and entered the domain name and proper nameservers along with the term. This domain is already registered, so I was trying to get it added to the customers account (just a test account for now) so it shows up there and it produces the errors after I run the cron job to sync.

I thought this was funny. Is there much participation any longer on their forums? Is it possible any longer to get an AWBS license key? We would want to install a copy so that we can build an importer.

Ok, that seems to be fine for now, but is there a plan to allow selection of the template either via configuration file or URL? Also, you need to upload the "default_smooth" folder that in inside the LC-smooth directory and rename that one to default.

My steps to create this error are slightly different but here are my logs: I was trying to attach them but they're too big. Here's a manual edit: Input: https://httpapi.com/api/contacts/add.json a:15:{s:4:"name";s:10:"xxxxx";s:7:"company";s:14:"Not Applicable";s:5:"email";s:16:"xxxxx";s:14:"address-line-1";s:11:"xxxxx";s:14:"address-line-2";s:0:"";s:4:"city";s:6:"xxxxx";s:5:"state";s:2:"xx";s:7:"zipcode";s:5:"xxxxx";s:7:"country";s:2:"US";s:8:"phone-cc";s:1:"1";s:5:"phone";s:7:"1111111";s:4:"type";s:7:"Contact";s:11:"customer-id";N;s:11:"auth-userid";s:6:"xxxxxx";s:7:"api-key";s:32:"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx";} Output: https://httpapi.com/api/contacts/add.json {"status":"ERROR","message":"Required parameter missing: customer-id"} Input: https://httpapi.com/api/customers/search.json a:5:{s:8:"username";s:16:"xxxxxxx";s:13:"no-of-records";i:10;s:7:"page-no";i:1;s:11:"auth-userid";s:6:"xxxx";s:7:"api-key";s:32:"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx";} Output: https://httpapi.com/api/customers/search.json {"status":"ERROR","message":"Method Not Allowed. Use GET"}

CORE-720 is fixed for 3.0.3.

I have looked for that box but i see nothing. I uploaded a fresh 3.0.2 downloaded today and the crc is not the same. Now i have the correct box "Invoices" at the top and the "view" option. Thank you !

wow! and nah your good luck, else we wouldn't have Blesta

This feature already exists. When a client logs in, their dashboard lists their invoices with an option to "View" each one. Clicking this will download the invoice PDF. Does this not happen for you?

The way it works is intended. Previously, it was a plain text field along with some other fields in Blesta, but those needed to by made into password-type fields. We plan to come back to this to improve how passwords are generated such that you would have an option to view the generated password.

Could certainly give that a go, I'm running a throw-away VM just for trying out Blesta.

Suhosin isn't required, so that's fine, does it find the GD formats mate? and yes it seems it can't detect the CURL. Which is the issue. You'll need the devs help as I've never installed Blesta on Ubuntu before. Sorry. It's 5am in California where the guys are from.

Yeah, direct purchase + 1 dev license max per owned license can be requested. Dev licenses are strictly non-production.

Yes, please send API documentation. If they have a well written PHP API library, that would be useful as well and save some time.

The license is legit, however you PM'd me and I'd like a ticket to reference. Support & Updates good through Aug 14, 2014. Edit: Rob, the process is that once Gualter makes a sale, he will open a ticket or update his ticket with the buyers information and we will contact the buyer and arrange the transfer. Currently we do not charge a transfer fee.

Please post 1 feature request per thread, and include as much information about the feature as possible. Having 1 feature request per thread allows the thread to focus entirely on that feature. One of our goals is to gauge community interest in a particular feature, which helps us prioritize the feature if we decide to add it. If we do add the feature to our project management system, we will usually post a task ID associated with it. The feature can then be tracked in the thread to completion. Posting multiple feature requests in a single thread waters down the request, and it will usually receive fewer responses. So, sticking to 1 request per thread increases the odds of it being implemented!

CORE-747, tentatively scheduled for 3.3.

Here are a few.. CORE-604: Merge tickets CORE-605: Custom ticket statuses CORE-606: Staff signatures CORE-607: Split tickets Some of the others need more planning before I can assign a task to them, including the automatic actions, which we want to implement but it's pretty involved, at least how we want it to work.