Paul

Packages > Order Forms > Edit. What is the "Name" of your order form? This is used on the order form.

Normally the module handles this. For example, cPanel creates this field if selling cPanel hosting. If you are manually provisioning and do not need to use a provisioning module then you can use the Universal Module and create a Service field for your Universal Module Product for this. Alternatively, if using no module or some other module that does not request the field and you want to ask for it, you can create a configurable option of the type text for this. Packages > Configurable Options. Assign your Option to an Option Group, and this Option Group would be assigned to your Package.

The automation task only provisions paid pending services. This means: The order is approved, which makes the service go from "In Review" to "Pending" The service is paid (or the invoice does not exist, was voided, or "unlinked" from the service). The "Provision Paid Pending" automation task will run and activate services that meet these requirements. Alternatively, staff can manually provision pending services, whether paid or not. But, if a client places an order, does not pay the invoice, and no other action is taken, the service should not be provisioned. Probably something interjected in there some place.

You probably want a custom plugin that will create a 2nd invoice for the second amount. Order, pay $50.. plugin automation task creates a 2nd invoice for second $50 x days later and links it to the service. The plugin would create an automation task / cron that would run say once per day and check for services created X days ago (or renewed x days ago if for a renewal) that match and invoice them for that second amount. Service would be for 1 year, the client would see $50 and pay $50 during checkout and then later get another invoice for $50 per the plugin above. This could present a challenge to the clients expectations during checkout, unless you show the total in the description or someplace.

Version 4.4.1 is now available, please see the release announcement. Patching Blesta See Patching Blesta in the User Manual for instructions. Installing Blesta See Installing Blesta in the User Manual for instructions. Upgrading Blesta See Upgrading Blesta in the User Manual for instructions. Migrating to Blesta See Migrating to Blesta in the User Manual for instructions. Release Notes See Blesta Core - Version 4.4.1. For older releases see all Change Logs.

Under Billing > Orders widget do you see the cog/gear icon in the upper right of that Orders widget? Click it. You can subscribe to order emails. Every admin that should get these emails must go here to set this up.

Screenshot?

CORE-2779 has been created for this, but the vulnerability described does not impact Blesta as implemented. There are a number of issues that must be resolved for compatibility with the latest jQuery and we're working on it. (Simply updating jQuery will break the software) For now I would suggest contesting the item with something along the lines of: The software is implemented securely, and in such a way that it is unaffected by this jQuery vulnerability. We are waiting on a software update from our vendor an will update as soon as it's available.

I believe we got you taken care of this morning. If there's anything else we can do please let us know.

Is this for Ticket #5175551? Looks like I resolved this for you this morning. You opened the ticket Wednesday night, and Thursday was a national holiday.

Blesta Owned Unbranded 40% off with coupon code: blackfriday2018 Addon Companies for Owned Licenses 50% off with coupon code: blackfridayaddon You can purchase these inside the client area by clicking Manage next to your license Expires Nov 26th. Don't miss out.

What's the tl;dr? Set reseller options on the Package in Blesta?

We appreciate that!

Is this Input? Is there no Output? 192.168.1.15 is a non-routable IP address. Go Cardless will not be able to post the transaction status back to Blesta. The "refresh" occurs because your credentials are wrong, or Blesta is unable to communicate with Go Cardless. This could be because of a firewall, your non-public IP/hostname, or inability to negotiate modern SSL/TLS. I have tested the Go Cardless gateway in 4.4.0 myself today without issue.

If you are running a custom or modified PDF invoice template, you will almost certainly have to update it due to the update to TCPDF. We had to make modifications to the templates to get them to work properly. I would suggest testing with one of the included templates to see if that resolves the issue. You should also check the logs, typically at ../logs_blesta/ (but defined under Settings > System > General) to see if any errors are written at the time of the cron task running. Any errors would be very helpful in determining the issue.

Good idea, we will soon be supporting only PHP 5.6+ as well, so I would highly recommend everyone running an older version of PHP upgrade as soon as possible.

Yes, unless we raise the minimum requirements so that it does not matter.

Looking good! Nice work!

Why not use the whmcs importer? Do you only want to import clients but nothing else? If so, check your CSV file for issues. You can also try importing a smaller set of clients at a time, say 10 at a time. That way you can narrow down which records are a problem. Then, if you like, you can PM me a copy of the problem records and I may be able to help.

We will likely be changing the encoder for the default files soon for PHP 7. I'm surprised that the hotfix-php7 files are working for you on PHP 7.1 or 7.2, that was not our experience and why we ship a hotfix-php71 directory for 7.1 & 7.2.

Under Settings > Company > Billing/Payment and Client Groups there's an option called "Queue Service Changes Until Paid". If this is checked, then the plan upgrade will not occur until it's paid and the cron next runs. You may prefer this, rather than doing the upgrade in advance of payment.

Thanks for the update, glad you got it working! A common mistake people make (posting this not for you, but just in case anyone else sees this thread) is to add the IP for your Blesta host and not the server itself. The primary IP address of the server running Blesta is usually the one that API requests originate, and is the one that should be added to Enom.

Sorry for jumping in.. but maybe this will be helpful. GoCardless is implemented similarly to PayPal (Which supports PayPal Subscriptions). So, clients can set up a recurring payment the first time, which will recur automatically. Docs at https://docs.blesta.com/display/user/GoCardless Take a look at this screenshot - https://docs.blesta.com/display/user/GoCardless?preview=/10551346/10551350/gocardless-installed.png Most people will want "One time and subscription payments when possible". Alternatively you can select "Subscription Payments Only". However, it's important to note that if the client is selecting to pay an invoice that does not have only recurring items, they will not be able to make a recurring subscription payment. So, giving the client the option (one time or subscription) you give the client control without risking a one-time invoice being unpayable.

That's correct.. Here's a screenshot of the GoCardless config in Blesta https://docs.blesta.com/display/user/GoCardless?preview=/10551346/10551350/gocardless-installed.png You probably want to select "One time and subscription payments when possible". If the invoice has recurring items only, then it will allow them to set up a subscription for it, and the recurring payments will be sent to Blesta automatically.

Sounds like your CSV file has issues. There is no state called '\xC1', maybe this is the issue? Double check that all the data in your CSV is correct.