Paul

There probably should be something in the documentation to indicate which API it implements. I don't understand what you mean by "isn't fully tokenized" though. Blesta does not at any point store sensitive card details for Stripe, just the token. (Unless configured to do so instead of tokens). The contention is the pass-through of card details. It's still tokenized, it just isn't using stripe.js to keep your server from seeing those details when the payment account is initially created. The result is that Stripe works a lot like Authorize'net's CIM method. As far as I know, there is no stripe.js equivalent to Authorize.net CIM. There's less risk than storing card details, but some risk because of pass-through, and a requirement for PCI. Cody will have to comment on the design aspect of a javascript implementation.

Stripe is a merchant gateway and does not work like PayPal at all, so it's not possible. A payment account exists in Blesta, and Blesta makes the necessary API calls to Stripe when it wants to charge a card (and passes the token). Allowing Stripe to inject javascript code in the process means that a feature is necessary by which all merchant gateways could do the same.

The Lounge is the best place for this.

Yes, please start a new thread in the feature requests forum.

Check out /components/invoice_templates/default_invoice/default_invoice_pdf.php, lines 15-30. I wonder if we should allow the font size to be set in invoice customization.

There is a known issue where going to /admin/upgrade can cause an error and prevent you from running the upgrader. It has to do with maintenance mode being enabled. You may run the following via a shell to upgrade with maintenance mode on.. php ./index.php admin/upgrade Or, disable maintenance mode and try again via /admin/upgrade in your browser. See CORE-1081 for details on this bug. It is resolved and will be in the next release.

I thought we were keeping the thread fresh. Come to think of it, this is in the wrong forum. </closed>

There are others successfully running Blesta on Windows, and we're committed to fix any issues that arise on that OS. Still, we recommend Linux over Windows.

Just an update to this, we made the roadmap public. You can view it at dev.blesta.com. Please note that when we made this public, all tasks in the system were marked private. We are gradually making existing tasks public, and most new tasks are created public.

Are other emails sent? Using invalid tags within the email can cause this kind of issue. What module are you using? Do you mind posting the text and html content for your service creation email template, and the package welcome content?

I've added this as CORE-1082, and you may track the progress there.

Amazon payments will happen, but because demand is not high it's not at the top of our priority yet. There are some other more highly requested gateways that we're working on first.

We'll need steps to reproduce. This was a bug in a past release, but has since been corrected. I tested this myself on 3.1.2 yesterday, by unchecking the "Use Module" option when creating a cPanel account and it worked flawlessly. If you're experiencing the issue on 3.1.2, please open a thread here - http://www.blesta.com/forums/index.php?/forum/22-bugs/. Be sure to read first, and we'll need steps to replicate.

You might have to save and edit in source mode only. We spent a lot of time considering different WYSIWYG editors that are license friendly, and it was the best, but they all seem to have some problems.

Are you running the latest version, 3.1.2?

I heard this one probably a year ago, still funny. But at work I can't stand it when people don't wash their hands.. or they do that quick 1 second hand rinse no soap thing, even worse it just mobilizes all the germs.

The goal is a beta sometime next month. Beta period would probably last 2-3 weeks.

The "theme" for 3.3 is "Invoices", including proforma among other things. I really, really, really want to see price overrides in here also. I want to see those in 3.2, but it's a toss up of whether it will make it into 3.2. If it doesn't make it into 3.2, it's a must for 3.3.

What about your welcome email content from the package? That is interjected into those service variables.

Please see http://www.blesta.com/forums/index.php?/topic/2040-unexpected-character-in-filters/ It's interesting that your'e getting a similar error. I wonder if there's an issue in your email template.

When you're adding a new client, or when you're adding a service to a client? Chances are good there's an issue with the content of one of your email templates. Probably the Service Creation, or Account Registration templates. What do you have in those for HTML and Text?

In the WYSIWYG editor for the template, highlight the Pay Now text, then click the link icon in the editor. Enter the tag: {invoice.payment_url} for the URL. Also check the text version, since links can't be created in the same way, you may have something like this in the text area: Pay Now, visit https://{invoice.payment_url} (No login required)

When you create a package that uses the cPanel module, you can enter package welcome email details. See http://docs.blesta.com/display/user/cPanel#cPanel-SampleEmail for sample email content to use. When the package is ordered, and the service is created, this email is sent to the customer.

You want general if you're just selling hosting, and domain and other if you're selling domains or domains and hosting.

After you create a package, you just need to create an order form. Under Packages > Order Form. When you create an order form, you specify what package groups to add to it. A package group is a group with 1 or more packages. Make the order form the default order form, and it will appear via the order link on the portal page.