Paul

Very nice! Do you need an account with UptimeRobot from here? https://uptimerobot.com/

That reminds me, I need to update the demo. We cannot provide the database for the demo, it wouldn't work without modification anyway, and it's a bit out dated. It's likely we will be populating the demo automatically using a utility to seed in artificial, but realistic data. This utility would likely be available to the public.

An option is coming that will allow you to disable combining of services on invoices that renew on the same day.. this would result in a new invoice for every renewing service.

That sounds like far more work. Thanks for the use case though, it does make sense.

Can you tell us more about how you use the feature? I've personally never needed it, so I'm interested in knowing about the business case for it. Do you need to split invoices often, and if so, why?

@Carl did you modify any of the templates? If not, what OS and browser/version are you running?

To be honest, invoice splitting has not been a big request. In many places, modifying an invoice after it has been created is a big no-no as well. Is splitting invoices something you find yourself needing to do often? If so, we'd love to hear more about the business case for it. This seems like a nice to have feature, but nice to haves are not very high on the priority list.

Any extensions that have any modifications are included in full in patches. This is because extensions are contained in their own repositories (externals). Our build process checks out the extensions we want to include with Blesta during the build, and wraps it all up in a nice little zip file. This means the build checks out a full version of the extension.

They probably fell off the planet. I would suggest filing a complaint with your credit card company, or paypal, or whatever you used to pay and find another Minecraft server company to place a new order with. Best of luck!

Ah, you'll need to contact them directly. They are just using our software. Also, they had a trial license, which expired in Feb so maybe they just can't login to approve your order? Or, they pirated our software. You might bring that up when you contact them.

Right. It almost sounds like the OP purchased a Minecraft server from someone else using Blesta. OP, are you using Blesta yourself?

There's currently no option to split an invoice into multiple invoices, might be a good feature request. You could do so manually. Open a new window to create a new invoice. Copy line items across from the current invoice to the new one, and delete them from the current.. Save both.

In most cases I can find your server is unable to resolve hostnames. Check your /etc/resolv.conf file and make sure you have some caching servers listed. If you don't you can use Google public DNS by entering the following 2 lines into the file: 8.8.8.8 8.8.4.4 If your server can resolve hostnames, check your PHP for any disabled_functions. This is an issue with your server.

Inactive packages cannot be ordered, but staff can still put people on them if they like, without having to grant the client access to a restricted package. The way I see it we could do one of the following: 1. Leave it as-is. 2. Create a "soft delete" option for Packages, to make them disappear forever. 3. Hide all inactive packages (unless/except the client is using that one and you are editing the service) 4. Add a setting whether to display inactive packages or not. Given that much of the conversation lately around Blesta has been to open things up so that staff have more control, and not less control, I'd go with #1 or #2. #2 if the goal is to remove packages from ever being seen again.

Version 1.0.1 of the Blesta License reseller module has been released. Please use this version instead, the original release had a bug that could cause multiple licenses to be created over the API unintentionally.

Yes, it would need to be by staff group.

I can see how a whitelist for bypassing 2FA would be convenient, but it makes me nervous. I want to be 100% sure nobody is logging in as me without entering my OTP. If plugins can't alter this process, maybe they should be able to, a plugin may be more suitable. I'm totally on board with a whitelist for "Only allow staff from group xyz to login from these CIDR's" though.

We have discussed adding the ability to set an override price for a service at the time of order to match that of the package. Then, changing the package price would have no affect on the price of those service. I'm curious though, what do you do now if you need to raise the price for say, everyone on a particular plan?

Blesta needs full access to its database. During upgrades or plugin installation, it may need to alter the database. It shouldn't need permissions to server administration type of privileges though like CREATE USER for example. https://dev.mysql.com/doc/refman/5.1/en/privileges-provided.html Cody or Tyson may be able to offer more details on exactly what privileges are required, but I think you're safe with everything on that list above ALTER ROUTINE.

I'm pretty sure the order-id's can be added by clicking to Manage the service.

If you are seeing a blank page when browsing available modules, there is likely an error. Enable error reporting in your /config/blesta.php config file. Set Configure::error_reporting(-1);

I agree that it should attempt to create the directory again, if it does not exist, when attempting to write an attachment to disk. I've added CORE-1753 to address that. Regarding the error message, I'm not so sure. While including the directory path would be beneficial to admins, displaying such an error to clients would leak the server path to them which could be considered a security issue.

You should have some directories within your "uploads" directory as defined in your screenshot, including: 1/ 1/support_manager_files/ system/ All of these should be writable, and the support_manager_files directory should be writable by your web server, cron user, and your email server username if mail is being piped in.

30 days is a reasonable time. The logs can get fairly large, so if that's a concern you may want to lower it.

http://dev.blesta.com/browse/CORE-1749 (see comments for hotfix, this will be included in 3.5.2) Please note that staff should be aware that you can void a transaction same day only BEFORE it settles. If it's after the settlement time or day, then they must issue a refund instead.