Cody

Package pricing ID values really have nothing to do with package IDs. Everytime a package is created one or more package pricing options are created as well. Package pricings are stored in the package_pricing table. Don't rely on package pricing IDs being functionally determined by package ID.

What version of Blesta? I seem to recall something like this being a bug in 3.0.0.

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.

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.

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.

CORE-720 is fixed for 3.0.3.

The error was triggered while importing email log entries. Interestingly, it looks like you have entries in your email log without a to address. Obviously that's not logical, but it's good you got the error as it allow us to improve the migrator to handle all of these bizarre issues with WHMCS. Update line 845 of /plugins/import_manager/components/migrators/whmcs/whmcs_migrator.php: from: $vars = array( to: if ($message->to == "") continue; $vars = array(

Nothing else to say. http://source-docs.blesta.com/class-AppModel.html#_systemEncrypt http://source-docs.blesta.com/class-AppModel.html#_systemDecrypt

To fix update line 672 of /plugins/import_manager/components/migrators/whmcs/whmcs_migrator.php: from: $departs = explode(",", $departs); to: if (!isset($this->mappings['staff'][$remote_admin_id])) continue; $departs = explode(",", $departs);

Just got my paws on a hostbill installation. I haven't spent but a couple minutes with it, but oh my.... exploit, exploit, exploit.

Are you saying you didn't have any closed tickets, or that the closed ticket you had don't appear? All tickets should be imported, and I see closed tickets in our test environment. Thanks, I'll take a look. Services aren't yet supported by the current version of this migrator.

Let us know if you notice any issues with the imported data so we can be sure to fix those.

Updated migrator.

We'll be releasing an update soon, with additional features a fixes. Didn't have time to build it today.

Closing as not a bug. If OP, or anyone else for that matter, can provide steps to duplicate please open a new thread for discussion.

Closed as not a bug.

Moved to support forums since we're using SMTP with SSL on port 465 and it works fine. Are you sure you're not running TLS on port 465, or perhaps no security? When you say you're using SMTP with TLS on port 587, is this is the same mail server? Do these settings work for sending mail?

Well, technically it is your side, since your data isn't formatted exactly as our test data.

Try changing line 609, or there abouts, of whmcs_migrator.php: from: 'amount' => $transaction->credit, to: 'amount' => $credit->credit,

You can move just about everything outside of the public directory, with the proper code changes. We only recommend having the uploads and temp directories above the publically accessible directory at this time, however. Spend time with my family, contribute to open source projects, and play video games. I'm in the middle of The Last of Us right now. Absolutely not, though you may need to have support and updates in order to upgrade depending on your license type. You're welcome.

Licenses are linked to install path, domain, and IP address. We can enabled multiple IPs and domains per install, though this is typically only done for multi-company licenses but there may be something we can do to acomodate you. Only what's necessary to protect licensing. By lifetime are you referring to our lifetime owned license? That license includes support and updates for life, so there's no need to purchase anything else to receive support and updates. Owned licenses include 1 year of support and updates, after which you may optionally purchase support and updates on a yearly basis. Releases follow semantic versioning, and patch releases are always free. As an example, if you are running 3.0.0 and we release 3.1.0 but you are not current with your support and updates at the time of that release you may upgrade to any 3.0.x release, but you will need support and updates to upgrade to the 3.1 minor release. You can install Blesta anywhere you'd like. You can certainly do that if you're comfortable with a little PHP. Or you can create static HTML pages that simply link to pages within the Blesta order form. A number of users are currently running Blesta on nginx. Kudos to cloudrck. Security is by far our top priority, so we make a strong effort to releases security patches as fast as possible. The average turn around time varies depending on the severity of the issue, but can range between a few hours to about a week.

Change line 536 of whmcs_migrator.php... from: to: if (!isset($this->mappings['recurring_invoices'])) return;

Please note that the latest version of this migrator is included with the latest release of Blesta. Instructions BACK UP YOUR BLESTA DATABASE If you are not running import manager plugin version 1.0.3 download import_manager_1.0.3.zip and unzip to /plugins/ Unzip the contents of whmcs_migrator_b8.zip to /plugins/import_manager/components/migrators/ You should now have /plugins/import_manager/components/migrators/whmcs/ Go to [settings] > [Company] > [Plugins] and install the Import Manager Click the Manage button on the Import Manager and proceed through the steps The migration process may take a while. It imports A LOT of stuff. Data Imported Staff (including login passwords) Client Groups Clients (excluding login passwords) Credit Card Payment Accounts Custom Client Fields and Values Client Notes Contacts Tax Rules Currencies Invoices Recurring Invoices Transactions (partial refunds refund the original and create a new transaction for the difference) Client Credits Invoice Credits Support Departments Support Tickets (excluding attachments) Support Predefined Response Categories Support Predefined Responses Sent Emails The following Settings: Mail Delivery Type SMTP Host, User, Password, Port, and Security Type Invoice Days Before Renewal Invoice Reminder Settings Auto Debit Days Before Due Suspend Services After Due Calendar Events Products (become packages) Registrars (become modules/module rows) Servers (become modules/module rows) Services Domains (become services) Notes All custom pricing overrides will be imported as package pricing potentially creating multiple prices for the same term and currency WHMCS uses plain MD5 passwords for admin users. To enable support for these passwords update (/config/blesta.php) Configure::set("Blesta.auth_legacy_passwords", false); to Configure::set("Blesta.auth_legacy_passwords", true); What's new in b6 Added debugging option. Added check for gmp extension. Added support for refunds. Import refunded invoices as void. What's new in b7 Only sets quantity for package if stock conrtrol enabled Extracts all numberic values from ticket ID to better ensure ticket numbers come through What's new in b8 Introduced transactions for deferred commits (speed improvements) Now forces UTF-8 connection to WHMCS database to ensure special characters come through import_manager_1.0.3.zip whmcs_migrator_b3.zip whmcs_migrator_b4.zip whmcs_migrator_b5.zip whmcs_migrator_b6.zip whmcs_migrator_b7.zip whmcs_migrator_b8.zip

That's actually the expected behavior. The version number displayed in the footer is the version of the files. There's a separate version number for the database schema, and they're not always in sync. However, you do raise a good point. In the future we may want to automatically direct to the upgrade screen if/when an upgrade is possible.