Paul

I have assigned this to CORE-852 Add support for vault to quantum gateway.

This is something we'll be looking at pretty soon. If there are no configurable options, we would like to skip that step entirely. It's a little bit complicated because the order system isn't aware whether the module has these options or not which is why it works as it does at the moment.

Physical products that need to be shipped out are likely better suited for a shopping cart like Magento. There are a few things that would need to be added to Blesta to give better support for physical items. Ability to sell "one time" items that don't stay listed as active services. The ability to check out without having an account. Ability to request separate shipping information, and management interface changes to track this Tie ins with shippers like UPS/Fedex/USPS And probably some more stuff You could fudge it and make it work, but if you're doing any kind of volume I'd suggest a shopping cart like Magento.

I haven't heard of Naxis before, but curious where this goes. Will you be publishing a recommended rule set?

We've talked about a package clone ability, drop you into the create a new package form with all the details copied in. It's a good idea, any more +1's?!

If they are anything like some of the USB barcode readers you can buy, they just scan and convert it into numbers and input the value into a form field. I'm sure the proprietary ones like the paypal card reader only works with their app.. but maybe there's a generic card swiper out there,.. someplace?

I suggest looking at tickets specifically immediately before and after this one. If something shifted, it's likely that one and everything after it would be wrong.

Doesn't APF/BFD have issues with virtual servers? We use to use it and switched to CSF/LFD because of it if I recall. Maybe we can nudge Interworx towards CSF/LFD.

The importer should install the support plugin automatically.

I'm pretty sure the card readers could just input the card number into the appropriate field in Blesta on swipe, through the browser on your device (iPad or whatever). There's a lot that can be done to support this more fully, like a mobile interface, and some tweaks with card present in mind.. but yeah, not high priority at the moment.

Why not cancel any active services, and void any open invoices?

I think people are starting to realize that it's time to move on, and we're grateful for everyone that decides to make Blesta their billing application of choice.

We submitted a responsible disclosure document to them today, all issues we found were confirmed to still be issues in their latest release. We'll see how they handle it.

Very nice! I'm a fan of getting things to work optimally with few resources. Then, just scale it up as you need. For a HA setup, heartbeat with 2 dedicated servers is a good way to go. I have set up a couple applications similarly in the past and it works pretty well.. The only issue I've had besides the pain in resyncing MySQL from slave back to master after a failover is failover flapping with heartbeat when there is an issue with the switch or router on the public network. With 2 servers I usually just use a crossover cable for the private network for heartbeat.

Good idea Also, it sounds like we're going to be adding some reporting to the importer to try to identify how long different operations are taking. We might be able to optimize some things and speed the importer up.. but it is doing a lot of stuff, including decrypting and encrypting credit card and other data. Some tasks are just going to take a while, but I can understand the frustration of waiting and then getting an error. I appreciate all the feedback everyone is giving us, and your patience. When we first released this, it worked perfectly with our tiny little test data set. More people, and more data expose little issues that we can better accommodate, so thanks!

A voided invoice is completely dead in Blesta. It will not be used to determine if a service should be suspended or not, and no actions can be performed on it, other than unvoiding it -- which would return it to a normal invoice. When voiding an invoice, any payments applied to the invoice will be returned to the transaction as a credit. It won't try to refund or void the transaction. So, the only issue I can see you having is that voiding an invoice will result in a credit if a payment was applied to the invoice. There are several ways you can handle this. Void the transaction in Blesta only (not using gateway) Create an invoice to balance the account out and negate the credit. When we imported our data, I had a handful of accounts that were imported from Blesta 1.x to Blesta 2.x that had issues when they were imported into Blesta 3, and I had to use the above methods to correct them. It wasn't ideal, but it worked.

Note taken, no obvious affiliate links. There will need to be a unique link, with some type of identifier, but I agree.. I don't click on anything that has the word "aff" in it as part of a URL parameter.

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).

That's pretty odd, we've never seen that happen before. Had you made any changes to the database prior to this? What version of MySQL and PHP are you running?

It looks like it's not able to connect to your SolusVM master and retrieve the information. These details are fetched dynamically from the API. Please confirm your SolusVM module settings.

Are you using the CIM or AIM method? I found this thread which may be helpful http://www.primothemes.com/forums/viewtopic.php?f=4&t=14940

Sounds good, should have proxmox beta module available for testing by the end of this week.

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.

No worries. We could have followed the flow and gone with a grid with a handful of options, but we figure you might want to do a 5yr term, or a 6 week term, or 30 days instead of 1 month.. who knows?

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.