Paul

Nice contribution Mike! It's always good to recommend good security practices. I'd probably go with the Warning / Yellow/Orange color instead of Red personally, but I like it!

I don't think there are any guarantees in life, but I get what you're saying sure. If I remember correctly, they gave us the rights to the module, so they did the right thing there. I don't know if they can speak publicly with much detail about the events of the past, but they are welcome to do so if they want. I think it had less to do with MG and more to do with our competition trying to put the squeeze on us. Whatever the case, I have confidence in MG, and it's good news for Blesta users. Time to bury the hatchet and move forward. The more 3rd party extensions available the better, and MG is certainly capable of turning them out.

That looks very very close, nice work! I promise to have a status update on the beta very soon. This minPHP 1.0 upgrade has been giving us some major grief.

ModulesGarden is probably the largest, most widely used source for extensions and custom development in the hosting industry. We see this as a great opportunity for our customers and Blesta overall. If you can use any of the modules they've released for Blesta, I would encourage you to buy them! Let's show them our support, and give them a good reason to make a lot more extensions for Blesta. Plus, I mean, they have a 50% coupon right now.

Looks familiar. The more the better!

I commented on some of your changes in your pull request.. I'll ask Tyson to review also, so there may be more. Thanks!

Your problem is probably PHP 7. Blesta 3.6 will not run on PHP 7. PHP 5.6, and you should be fine.

Hi Henry, As a staff member, you would record these using the "Record Payment" option under Actions on the clients's profile page. There is an Offline payment gateway (Under Settings > Company > Payment Gateways > Non Merchant > Available) that you can install that will allow you to provide instructions for making a payment offline during checkout. It will however, not actually record any payments. That's up to you, once the payment comes in.

Nice work! Never heard of these two you released plugins today for, seems like there are a lot of nice options for Live Chat lately. We started using tawk.to for blesta.com recently, it's completely free and seems to work pretty well.

Do you know why it's incompatible with 3.4+? I'm not aware of any backwards incompatible changes in the module system. Unless, perhaps, the module is doing something out of the ordinary. The best way forward is to fix this existing module. @timnboys do you know what the compatibility issue is with 3.4+? We are slammed with 4.0. I'll donate $50 for a pull request that resolves the issue. (Please test test test before submitting)

I don't see any possible way a suspend action would result in a cancel request. The only thing I can think of is that you may have selected Cancel by mistake. If you think this is a bug, we would need steps to duplicate. The content of your module logs may be helpful, but I suspect they will look like a normal cancellation request.

We use Slack internally and most of our systems tie into it so everyone can stay up to date on the progress of tasks, pull requests, etc. I'd love to get some Slack integration into Blesta.

Companies do care about the image of their brand. They want to portray a particular image, consistently. Not sure why this thread has turned controversial.

We have a Mumble server we host and use when we play games, that we could potentially open up. Tried Discord, seems interesting, but it never caught on in our circles.

Thanks, I'll consider changing it. WordPress just feels wrong to me though, maybe it's their fault for not being more consistent historically.

CORE-450 Custom fields with encryption option. This would be perfect for customers submitting server passwords or other sensitive information. Of course, this is planned for the official support manager. Not all data needs to be or should be encrypted. Remember, encrypted data cannot be searched, and there is some overhead with decrypting it. Also AES does not use public/private key pairs like RSA, so the same key is used to encrypt and decrypt. This means that if an attacker got access to your database *and* your files, they could decrypt the data anyway. In contrast, if you were using Blesta's batch processing for charging credit cards, the private RSA keys used to decrypt cards would be encrypted with AES using a passphrase that is not stored anywhere and has to be manually entered. This method could be done elsewhere, and might be a good idea for sensitive ticket information, but the data would not be decrypted automatically and staff would have to enter a passphrase unknown by Blesta before it could be decrypted.

Blesta will send along the correct IPN URL when a payment is made from Blesta. Setting the IPN URL in PayPal seems to the the only way to RE-ENABLE IPN, if PayPal disables it from failed attempts. So, the question is: Is the customer making payment through Blesta? ie, clicking the PayPal button to pay during checkout? And if so, is IPN enabled in PayPal? Lastly, you might check your HTTP logs to see if there are any POST requests from PayPal's IPN, and look at the gateway log in Blesta - Tools > Logs > Gateway.

Great! I will add that some people have requested being able to maintain a cart across different order forms. This is something we'll look into in the future.

Do you have SSL and hosting in the same order form? If so, it should work as you expect. However, order forms are separate from one another and items cannot be ordered across them at the same time. So, a Package Group for SSL, and a Package Group for Hosting assigned to the same order form should work. Just not 2 separate order forms.

Nginx will work, but it's not fully supported. Because Blesta ships with a .htaccess file with mod_rewrite rules that are incompatible with Nginx, in order to get pretty URLs you'll need to make some configuration changes. There are community provided rules at https://github.com/cloudrck/blesta-nginx that you should find useful. Otherwise, all URLs will have /index.php/ prepended.

Part of the requirements for installation is that your VPS be ready for Blesta, which includes having a web server installed and configured that meets the system requirements. If you want to dump a freshly installed OS in our laps, we can install and configure the necessary dependencies on a CentOS 7 image, but this would include Apache as the web server and would cost extra.

I can't find the task at the moment, but we have plans to allow more customization of the client area. The idea is to be able to order the widgets the way you want them to appear, or toggle them off, or have them appear on their own page instead of as a widget. What you are asking to do now can be done, but it's a little more complex than editing the templates.

What does myplugin_controller.php look like? Assuming you were going through the docs here https://docs.blesta.com/display/dev/Creating+a+Plugin

Hi Mack, welcome and thanks for your patience. v4 beta 1 is expected out very soon, we're working on resolving a few remaining issues now. I'm happy to schedule a 15-20 min call to go over any questions you may have if you'd like to chat.

class MypluginPlugin extends Plugin {