Paul

If the license is with us directly, then you need to open a ticket from the client area at https://account.blesta.com/client/login

Interesting. On our cPanel dev server php-cli is a symlink to /usr/local/bin/php

It's in our short-term bucket, so it's not planned for a specific release at the moment. Our short term bucket is what we dig through when planning releases and when we are ahead of schedule. The earliest it would appear is 4.0, but more likely 4.1 or 4.2

Yeah definitely. The task describes a link to client groups.

I've added these to our "short term" bucket, so they are at least prioritized

See CORE-2010 which describes the ability to create order forms that are not publicly available, but available to authenticated clients who belong to select client groups. I believe this will more effectively fit your purpose, and it's an item we've been discussing internally over the past few weeks.

Just a note on this. Since this thread was started, we added a setting under Settings > Company > Billing/Payments > Invoice Customization called "Payments/Credits". If this is checked, invoices will show any payments already applied to the invoice. If sending all open invoices to a client, they will be able to see how much is effectively due for each invoice when payments/credits are displayed. The only issue I think, is that it does not show a summary of the total due across all open invoices.

We are considering this.. however, why not put all your items on the same order form?

You can update the header/footer for Blesta to match your website. The file is /app/views/client/bootstrap/structure.pdt

/app/views/client/bootstrap/structure.pdt contains the header and footer for the client area. Order forms have their own templates as well under /plugins/order/.

We would love people to be able to participate by voting for features in Jira, but due to Jira's licensing scheme it's very cost prohibitive as they charge us by the user. Commenting on the original thread, or starting a new one under feature requests would be the best way to log support.. this thread definitely helps.

See translate.blesta.com for crowd sourced languages. See https://docs.blesta.com/display/user/Internationalization+and+Languages for how to install them.

Awesome, congrats on your first Blesta module! Looking good

As far as I understand it, the payment details should be sent directly to Braintree, including CVV if you are entering those details when making payment and not using a previously stored payment account. That's how I would expect it to work, but maybe what is actually happening is a little different. This is something we'll need Cody or Tyson to look into.

We upgraded our Multicraft Dev server to 2.0 and talked with Daniel from Multicraft. We have the latest MulticraftAPI.php library, which according to Daniel is just a drop-in. We should be looking at this pretty soon. v2.0 seems much better, at least visually. Do you suspect the vast majority of people have or will be upgrading?

I just updated our Multicraft Dev server and it does look much better. We will be updating the module soon to use the new API. Any feel for how many people have upgraded to Multicraft 2.0? Any reason we should continue to support the old API?

Most likely you want /app/views/client/bootstrap/structure.pdt which is the header/footer file for the client area.

Are you using Multicraft 2.0? Per Multicraft, you need to enable legacy API support under Settings > Panel Configuration. We are going to update the module soon to use the new API for v2.0.

Our official Braintree gateway does not yet support Vault or token based storage, so the CVV is not sent to Braintree unless you are submitting payment at the same time. We have a task to add support for vault/offsite storage of CC data, but it has not yet been completed. So, the best way to proceed for now is to disable Braintree's CVV requirement. The option you provided "does not match when provided" may be sufficient for the interim. I would highly recommend utilizing the fraud tools we have available at the moment and be on the watch for fraud, which I would suggest even if you could use restrictive CVV rules with Braintree. On the black market, hackers often purchase CVV data with the card data.

Merry Christmas, Happy Holidays, and a Happy New Year to all.

CVV data is only passed along if making a payment by entering new card details. If you save a Payment Account and subsequently use it, the CVV is not sent because it is not stored. It's not stored because it is against merchant rules to do so and would result in non-PCI compliance, and termination of your merchant account. In order to process recurring payments in Blesta with Braintree, you should disable the CVV requirement with them.

Please see CORE-2007 I added this to our "Short Term" bucket, and placed it near the top of the backlog. While it is not planned for 4.0, we may have time to squeeze it in, especially since it is not overly complex.

If there is a vulnerability, chances are it won't even need exec perms to be exploited. If it's a big concern, you'll want to use an alternative tool to back up your database. R1Soft works very well, and I would highly recommend it. It's also a good idea to run Blesta on a private server.

Was the order approved? (Billing > Overview: Orders widget) Did you set up your cron job? Paid pending orders are provisioned by the cron.

Just to add: If this is not the 1st server the customer ordered, the Multicraft User/Pass will not be included.