Leaderboard

Hi everyone, We here at noclayer.com have been discussing implementation of our application for Blesta. We believe that this would be a welcome addition for Blesta users. We're planning to implement the following features: Asset tracking / Server inventory Location Mapping rDNS/IP management disabling a switch port for a server that is suspended / enable on un-suspension IPMI / DRAC / iLO integration, IP KVM ,reboots, reset Server provisioning Bandwidth provisioning Cacti/Nagios integration Cable management Datacenter/COLO planning plus more... The above and a lot of other useful features which will propel Blesta + NocLayer into a new playing field, it would be a direct competitor to the likes of Ubersmith and HostBill. Please tell us your thoughts. Thank you. Igor Noclayer.com

Hi, I write this because over recent weeks I have seen multiple people trying to run Blesta on one of the more latest PHP releases such as PHP 5.4 with the Suhosin PHP hardening patch applied. Because problems are happening with the setup they seem to be blaming Blesta for the issue when actually the issue is residing from the Suhosin PHP patch. As I write Suhosin barely has support for PHP 5.4 and doesn't even currently support PHP 5.5 at all some providers are now starting to drop the usage of Suhosin and consider it a dead project because the development of the project is no longer moving forward to cater for the changes within PHP. I can confirm that Blesta will happily run with Suhosin using PHP 5.3 alhough PHP 5.3 is now End Of Life security fixes will still be released into 2014 as they generally keep the security fixes coming for about 1 year once EOL status is declared. Based on the current status of Suhosin moving forward I wouldn't recommend running it any further in production until it becomes a stable project again with regular releases to keep supporting more current PHP builds. Am sure this will help those who are facing such issues.

FYI, mine is line 78. I know this wasn't directed to me but I'll see if it makes mine work better with showing errors.

Take a look at tblaccounts. The refundid is the id of the original transaction id that was refunded. The amountout is the amount of the refund. This means that an invoice can be paid in full by one transaction which is what you would expect, but another transaction could be a partial refund. This happens all the time, an invoice for $100 could be paid by one transaction but then a refund of $25.00 was issued on that original payment and refunded back to their credit card or paypal account. This could be for any reason, but the issue here is that the invoice is considered paid in full but shows a status of refunded. WHMCS uses refunded for a status whether the invoice is 100% refunded or just partially refunded. You're going to have to look at transactions that have a refundid and process them differently. Same with the invoices they are tied to. Here's a potential and rough work flow. Is transaction a refund? What is the invoice amount due Is this a full refund? If yes, void the invoice If no, the invoice is paid

There's no link in WHMCS between the refunded transactions and the original. Refunds appear to be handled simply as negative credits, unless I'm mistaken and WHMCS only uses them for display purposes, not for accounting? I'm seeing something different. Considering the following scenario: An invoice is due for $100. The client pays $50, then $25 is refunded. The new due amount for the invoice is $75. The invoice is still considered unpaid. It would appear to me that if an invoice is "refunded" that means it's considered paid in full. The problem with that there may not be any transactions that make that a true statement. Moreover, taking my example above. If I refund the additional $25, the invoice is now considered "Refunded" even though it still has $100 due. That makes no sense to me.

I agree - if the WHMCS importer was 100% finished, and the packages could be reordered, and the new order forms were in, and Blesta v3 wasn't basically an entirely new system, I'd be leaning on them a little harder for this. As it is, I can manage for now.

The issue you have is related to custom client fields. Somehow you have a custom field assigned to a client multiple times in WHMCS (or your client_values table in Blesta is not empty). Try changing line 334 from: $this->local->insert("client_values", $vars); to: $this->local->duplicate("value", "=", $vars['value'])->insert("client_values", $vars);

I would say they should make two importers LOL na maybe a option. Fresh Import [ ] Merge Import [ ] First system I know to do that.

I definitely like the second option better.

Exactly! Otherwise, you can't buy another company without manually importing all the data. There should be a better data migration path.

Good idea If a customer contacts me or a payment fails, I cancel the subscription and tell them that they can save money by remaking the subscription when they pay for the next invoice.

Bumping this request. I understand it's a low priority, but I thought of an idea. I hate seeing things like /?aff=102 on a URL, because it tells me I'm clicking an affiliate link. I just have an aversion to that. Maybe it's just me. But what if Blesta's URL read something like /mode=9fa83829105c2b9d -- maybe some 8-digit hex value that looks innocent, but is actually the affiliate link? Far from deceptive, it gets that "aff" out of the URL and -- get this -- doesn't indicate the total number of affiliates you have. Those of us who like to keep our company data private would appreciate that.

What do you have in your users table and clients tables before running the import? SELECT * FROM users Should only have 1 record. SELECT * FROM clients Should be completely empty. I can assure you it's not a simple as you think.

twhiting9275, I've had your back everywhere else, but these guys have been great about releasing new updates to their "BETA" importer. It isn't perfect as you can tell but they are making great effort to resolve the issues. Obviously its in their best interest to perfect a WHMCS importer if they want to take in all of the refugees. Don't take your anger at WHMCS out of the Blesta devs. They are doing fantastic work considering all of the demands and issues in this thread alone.

something like this would be better off requiring a "pin" rather than a password...4-8 digits, alphanumeric only, not case sensitive

You could also choose SMTP for the delivery type, and fill in bogus information. To be certain no credit cards could be charged, set a passphrase under Settings > Company > General > Encryption. Setting a passphrase encrypts the private key, making decryption of card numbers impossible without it and requiring batch processing. The passphrase can be removed anytime (with the current passphrase, of course).

What are the values of your company settings related to client start, format and increment values? i.e. "clients_start", "clients_format", and "clients_increment" You can run the following query to check the values: SELECT * FROM `company_settings` WHERE `key` LIKE 'clients_%' AND `company_id` =1 LIMIT 0 , 30 And when did this issue start?

Just disable all tasks except the apply credits task. [settings] > [Company] > [Automation]. I don't believe any emails are sent for apply open credits, but if you want to be certain, update your mail settings ([settings] > [Company] > [Emails] > [Mail Settings]) to use invalid SMTP info. To be doubly sure no emails go out, disable email templates in [settings] > [Company] > [Emails] > . Also, if you don't feel confident enabling cron tasks you can choose to explicitly run the "applyCredits" task by passing the cron key along to the cron via a GET request: https://yourdomain.com/blesta/cron/applyCredits/?cron_key=YOUR_CRON_KEY

I did this, Blesta is dening the details, eventhough they are correct. Edit: I had to generate a new key haha, working now, thanks

Maybe some tooltips would help?

Thanks, I appreciate the testing on 5.3, that all but confirms the people running Suhosin on 5.4 are experiencing a side affect of it not being fully compatible.

Glad everything is working for you now mate

Well, I just finished reinstlaling blesta on my main domain, as well as testing out the extended module creation on my dev site...and both seemed to work fine this time around. Guess I'll have to chalk this one up to a random issue with the files/database of the previous install.

You can use the logicboxes module for resellerclub (resellerclub runs on logicboxes)

Blesta is in the process of becoming a registered trademark with the US patent office. I saw the post you are referencing, a domain with the name blestareseller in it. In order to become a Blesta reseller, we have to create a reseller account for you and we have not so far allowed anyone to be a reseller through a domain name with Blesta in it. It's unlikely we will do so.

ha! I got confused too.. when it said term and then it had monthly/yearly.. at first I was thinking.. the hell? I finally figured it out when Blesta told me term had to be a number.

No. MD5 is strictly one-way. I think the best route is to simply reset all passwords on migration and send a mass email to your client base advising them of the change.

Latest version of the migrator is up (b5). You can get it here, direct download here. Changes include: Sets country to US if not set (clients, contacts, payment accounts). Sets first/last name for payment accounts to unknown if not set. Decodes HTML entities. Imports invoice credits as in house credits.