Paul

If the order was approved, and the service is "Pending", and the invoice has been paid, it will be provisioned the next time the cron runs. You should have the cron set up to run every 5 minutes. Look under Settings > System > Automation to see when it was last run, and what you should set up the cron job as. You may also run the cron manually here.

When you create a contact you can set permissions for the contact. Both staff, and clients creating sub-contacts. These are not the same as Staff ACLs, but should be sufficient for most cases. In this screenshot, the "Support" permission is from the Support Manager plugin, so you should be able to accomplish what you want with your Cerberus integration.

Sounds like an incomplete upgrade. Did you run ~/admin/upgrade? You can check the migration files for that table.field to see when that was added. I can look when I get to the office later this morning.

Most people won't know that it would break anything by changing the module. Most people won't write a new module with the same meta fields, and want to switch it over. I agree there should be a way to do this, disabling module changes was the simplest way to stop unaware people from making a change that would negatively impact their installation. If you're able to write a module, it shouldn't be too hard to write a query to update the packages to use the new module. In the future I'd like to create more separation from packages and services, and then we can safely allow the module to be changed.

Blesta version 4.0.0-b4 (BETA 4) is now available. You can download it from right here (Client Area Login Required). If you haven't seen the blog post announcement for 4.0.0 BETA 1, you can read it here. This is a BETA release. Beta releases are not considered stable enough for production use, and are UNSUPPORTED. DO NOT INSTALL IN A PRODUCTION ENVIRONMENT. Please report any bugs you find in the v4 beta bug forum. Installing Blesta See Installing Blesta in the User Manual for instructions. Upgrading Blesta See Upgrading Blesta in the User Manual for instructions. Release Notes See Blesta Core - Version 4.0.0-b1-b4. SEE BETA 4 ONLY For older releases see all Change Logs. What to Test! 1. PHP 7. The focus of this beta was largely PHP 7 support. Check change log for more. Known issues 1. An error is encountered when logging in or out with PHP 7, if errorReporting is enabled in /config/blesta.php

Safest option, set up some services so reminder should be sent out tomorrow, then wait until tomorrow. Tricking the system into running it again today requires removing the record of the run from the cron log today.

That's good, because doing so would break just about everything.

We have some docs on our shared login plugin here - https://docs.blesta.com/display/user/Shared+Login which may be a good starting point for any integration.

Looks like we have a lot more than that even, ha! This makes me wonder if there was a reason that cancelled or fraud orders do not have their "In Review" services deleted. My best guess is that there might be a need, on occasion, to figure out what the customer ordered and add it back. We've had to do this to fraud orders in the past, that ended up not being fraud. So, rather than deleting them immediately, I wonder if they should be part of a new setting that cleans up unpaid, cancelled, or fraudulent orders such that after X days, those "In-Review" services would be deleted. Thoughts?

All clients must belong to a client group. By default they go into the "General" group, which cannot be deleted. You do not need to create any others though, all clients can exist in this group.

Did you already disable Credit Card and ACH under Settings > Company > Billing/Payment > Accepted Payment Types? This should prevent them from being able to create a Payment Account at all, but it won't remove the nav link. Good to do this also if you haven't already, in case anyone stumbles on the URL.

What version of Blesta? Any customizations or 3rd party extensions installed? Anyone else able to duplicate this behavior?

1. Yes, I believe that's the issue. The path should include sub_folder/, as it's the full system path to support.mywebsite.com (right?) If you access Blesta via support.mywebsite.com, and not support.mywebsite.com/sub_folder/, then it should include sub_folder/ in the path for this setting. 2. No idea

In v4 there is an option under Packages > Order Forms > Settings tab for "Default Order Form" called "None - Show Listing". If this is selected, all order forms with Visibility set to "Public" will be listed here. The Visibility setting is a new option in v4 as well, and allows Public, Shared, and Client Only. Shared is via shared link, Client Only is for authenticated clients only. You may find this useful!

So Blesta is not installed in a sub-directory? Make sure your "Root Web Directory" path is set correctly, under Settings > System > General > Basic Setup. This should match your document root, the path that is loaded when accessing support.mywebsite.com, regardless if Blesta is installed in a sub-folder or not.

In review services are deleted when the order is marked as fraud or cancelled. If it still exists, first make sure it's the same service from this order. You can manually delete it there. If it continues to happen, it may be a bug and we would need more details on how to reproduce.

Changing the module for a package would break services that were already issued based on the package. Those services would not have the same meta data as those created after the module change because that meta data is defined by the module. Being able to safely change the module would require making some changes to the way that data is handled to de-couple services further from the package. Until this is done, the safer scenario is to prevent the module from being changed.

You need the cron set up for POP/IMAP importing of tickets. It runs via the same single system cron, so if you set up your cron originally, then you're good to go. For piping, you need to configure your mail server to pipe email to Blesta for your department email addresses. Take a look at https://docs.blesta.com/display/user/Support+Manager#SupportManager-email-pipingEmailPiping for email piping information. There are 2 methods shown, I suggest piping directly to ~/plugins/support_manager/pipe.php (Follow the docs) How you set up your piping/forwarders to send mail to pipe.php depends on your server and whether you have a control panel. Most control panels like cPanel allow you to do this in cPanel directly.

@Blesta Addons may be able to do this for you for a fee, I'd definitely recommend him. If not, there are others that can.

~/components/gateways/nonmerchant/paypal_payments_standard/views/default/process.pdt contains a both buttons. For recurring, and non-recurring. Simply update the URLs to the new buttons.

If you want to manually add a credit into their account that they can use that will not automatically be applied to any invoices then you should: Go to Settings > Company > Billing/Payment. Uncheck and save "Automatically apply loose credits". You may need to do this under Settings > Company > Client Groups also, if your Client Group settings are overriding your Company Settings. On the client profile page, under Actions, click "Record Payment". Enter the amount, select "In House Credit", and do not select any invoices that may be displayed. Regarding your 1st screenshot, when recording a payment for a specific invoice, you can change the amount and pay less or more than the invoice is for. This will result in a partial payment, full payment, or full payment + credit.

Multicraft does not automatically assign the 25565 port number to dedicated IPs. So, we have updated the module for 4.0 to allow the port to be specified when adding dedicated IPs to the module. When you ordered the dedicated IP, did it assign the shared IP instead? Is the IP address available to the server, and the daemon ID correct? It may make sense to test on the latest beta.

You can use the "Record Payment" option as an admin to apply loose credits to invoices. The default option is for Blesta to apply loose credits to invoices automatically when the cron runs, starting with the oldest invoice.

Shorten your terms.