Cody

The data required by logicboxes varies with each TLD, so it's not necessarily a dependency of using the module.

The latest version of the import manager is included in the first post of this thread. Download it if you are running some version other than 1.0.3 of the import manager plugin. This plugin comes prepackaged with the WHMCS migrator, so no need to download that separately if you're upgrading the import manager. If you already have version 1.0.3 of the import manager plugin then simply download the WHMCS migrator as per the instructions. This update will display any errors encountered during the import process. Run it and report back any errors you receive.

Looks like you either moved servers or disabled the Mailparse extension. That extension is required for parsing incoming emails for the ticket system.

Okay, so the reason why there is no customer-id is because the customer could not be created due to a missing address-line-1. Update the client's record and be sure to set an address.

I'm thinking about turning my Pi into a sprinkler control system, and creating an interface to configure schedules over the internet, and possibly tie into weather monitoring service (NOAA) to automatically disable/reschedule during rain showers. It could be fun to play around with when used in conjunction with my video surveillance system.

Sounds like this might be related to CORE-532 fixed in 3.0.3 (discussed here: http://www.blesta.com/forums/index.php?/topic/949-fao-tyson-domain-customer-id-field-and-yearly-bug/?p=8259). Can you post the details of the module log for the request? If this is indeed related to CORE-532, it's impossible for us to reproduce as the logicboxes API does not function the same in the dev environment as it does in the live environment, which is quite annoying. Added CORE-832 to investigate once we have the module log details.

Fixed in 3.0.5.

Update to the import has been released. Get the latest version here.

CORE-831 is fixed in 3.0.5.

Based on their docs (http://secure.netbilling.com/public/docs/merchant/public/directmode/directmode3protocol.html) it doesn't look like they support offsite storage. Looks like a pretty simple and straight forward gateway though.

There's an migrator for WHMCS in the import manager plugin included with Blesta. It will import pretty much everything but packages, services, and module info. We should have an updated version out next week that includes support for importing packages, services, and module info as well.

CORE-824 is fixed in 3.0.5.

It's redundant for me to keep saying this, "Because it would be redundant". "Because it would be redundant". $5.00 USD $25.00 USD $16.00 USD $15.95 USD Why do I have to keep saying "USD" for every price when everything displayed on that page is in USD? That's the definition of redundant.

Yes, I would always use a prefix (e.g. $).

What you're asking is equivalent to asking "When does it make sense to invoice a customer on August 14th?" It completely depends on your business. If I was running a company in North America and did business with the US and Canada I would enabled currency codes for display because both countries use "dollars" ($), but the values are which are completely different, therefore necessitating the display of the currency code to differentiate the two. This is not a bug because that's how it's designed to work. No, it's not a bug for the aforementioned reasons. And you've already accepted that you can configure things to work how you want them to, so why do you persist with this silliness? Paul was involved in the decision making on the reason to exclude the display of currency codes from the package listings of the order forms in order to remove redundancy. Just because you don't like the way something works does not a bug make.

That question is relative and depends entirely on your business, locality, and whether or not you process multiple currencies.

That question is relative and depends entirely on your business, locality, and whether or not you process multiple currencies.

You're confusing currency code with currency prefix/suffix again. Like I said, only the currency code is not displayed for package price listings on order forms. If you want prices listed as: x.yz USD Do the following: Disable display of currency codes Edit USD currency, remove the prefix and set the suffix to " USD" That's all you have to do.

As I said, you can disable display of currency codes and then set a suffix of " USD" for the currency. That should get you want you want. The reason why the listing of services does not display the currency code is because it is redundant. All prices displayed on screen for the order form are of the same currency -- always.

Another issue might be that the SFTP user doesn't have permission to write to the directory where the backups are going, but then I would expect you'd see something in the cron log about that.

You have the ability to control the prefix and suffix for each individual currency, as well as whether or not to display the currency code after the price. So you have the ability to configure every aspect of how currencies are displayed. What about that doesn't work for you? The format is [prefix] [price] [suffix] [currency code]. You can set whatever you want for prefix and suffix per currency and enable/disable currency code. If you want you can include the currency code as part of the prefix or suffix of any currency. Without currency code enabled: $x.yz $x.yz USD x.yz x.yz USD x.yz$ x.yz$ USD USD x.yz$ USD x.yz USD $x.yz$ USD USD $x.yz With currency code enabled: $x.yz [uSD] $x.yz USD [uSD] x.yz [uSD] x.yz USD [uSD] x.yz$ [uSD] x.yz$ USD [uSD] USD x.yz$ [uSD] USD x.yz [uSD] USD $x.yz$ USD [uSD] USD $x.yz [uSD]

What version of Blesta?

The currency code is not a suffix. You can disable display of currency codes under [settings] > [Company] > [Currencies] > [Currency Setup].

I don't see any problems with your screenshot, and given that 3.0.4 had no CSS changes I'm going to go out on a limb and say not a bug.