Paul

You can sort packages within groups by dragging and dropping them with the group expanded. This will affect how they are displayed here, and on order forms. Package group sorting would be really nice.

If you go to Packages > Package Groups, you can click to expand each group to list its Packages. Is this organized more how you expect? We are planning to make some changes to the way Packages are edited and created, as well as the way they are listed.. however, I don't believe there is any such task for what you're suggesting. If you wouldn't mind mocking something up, that may be helpful in understanding how you think it should be displayed.

The blog post touches on some of the key changes, but there are a lot of minor changes. What module are you using? Usernames & passwords are module specific, so the module could create a management tab to display that differently. Have you made a feature request for it? With 4.0 out, we are planning to implement a lot of things people have been waiting for with smaller more frequent releases.

Domains will almost certainly remain as services but be given a designation as domains so they can be displayed a little differently. That seems to be the simplest way forward. There will still be a plugin, which will handle creating a pricing grid, syncing renew dates, whois etc. The idea with the pricing grid is that packages will have the ability to defer pricing to a plugin. So, the idea is you could create a single package and not set any pricing, and it will obtain pricing from the plugin/pricing matrix for all TLDs and register/renew/xfer. This is subject to change to some extent, but should give you some idea of where we are headed.

There's this https://www.blesta.com/forums/index.php?/topic/3180-plugin-announcement-released/ The latest post in the thread by the author suggests they are going to release an updated version.

You could try using https://www.blesta.com/demo/, but I don't recommend putting sensitive information into the system.

Is this the issue where contacts are unable to open or reply to tickets? We are unable to duplicate this after many hours of testing. https://dev.blesta.com/browse/CORE-2361 (Thanks @evolvewh) If you think it's still an issue, please do a fresh install of Blesta without any 3rd party extensions or modifications and try to duplicate. If you can, please provide exact steps.

Can anyone else replicate?

I spent some time trying to find the right API docs for this, but I might not be smart enough. A link to the API docs? Is it just "WHM API 1"? Do you know if they have released a PHP API Library for this version of the API? If so, where is it?

Have you added a redirect in your .htaccess file? Redirect 301 /modules/gateways/callback/paypal.php /callback/gw/1/paypal_payments_standard/ Replace the first path to that which your CE install uses, and the second is the one for Blesta. The "1" in the path denotes company ID 1. If you don't have any addon companies, then it's just 1. Assumes you have Blesta installed in the doc root / so if you have it in a sub-directory like /billing/, then prepend that to the path. Blesta will try to apply the payment by matching the email address to an account. If the email address does not match, it will not be able to apply the payment.

We aren't going to include the Support Manager Pro with our distribution, it's not compatible and there's a lot of features that we don't think were implemented in the best way. I moved this task to the top of the backlog. As we continue with development for 4.1, if there is time, it will be considered for 4.1.

How did the mass mailer work other than that for you? I'm assuming you didn't have any such rate limits on your mail server.

You probably want to look at the Invoices.add event, see https://docs.blesta.com/display/dev/Event+Handlers

I bumped it to the top of the backlog for further review. Did you ever experience the issue on 3.6?

It sounds like the package is using a module row that no longer exists. You should edit your package, and select a new module row. If you're using something like cPanel, the module row is the cPanel/WHM server. Once you update the package, you shouldn't get the error any longer.

If when editing an invoice, the Email option is unchecked, it won't be delivered or it was already delivered. Are you creating invoices manually, or are they being created automatically as services renew? Have you made any changes to the core, or are you running any 3rd party code or modifications?

Part of the issue is that Blesta doesn't actually reference the PayPal subscription ID. Each IPN call is unique to the client ID, which works fine except when importing from another system. So, if there is no client ID, Blesta tries to match the right account by email address. This works fine if the PayPal email is the same as the client email. The best solution would be if Blesta stores the PayPal subscription ID, and uses that as a reference.

If it works when you run the cron manually, but not when the cron runs automatically then something is happen when it runs automatically. Do you have SSH access? If so, temporarily disable your cron, then SSH in and run the command and observe the output. You may wish to enable error reporting in your /config/blesta.php config file first. Your CLI environment may be producing an error, whereas executing PHP via Apache is fine.

You can add that free month package to a package group that contains paid packages. If upgrades/downgrades are allowed for the package, they can upgrade to the paid one in the client area. The only problem is that they could also downgrade to the free one. We have a task to allow package switching for free trials. Order Package A, then after x days, switch the Package automatically to Package B. However, this is not done yet. The way you have it set up, it may be a manual process. As an admin, you can use the Reassign Pricing plugin to switch to another package outside the package group. You could do this after it's ordered and provisioned, and then it will simply renew at the new package price unless they cancel. Takes a little manual work.

The biggest question we tend to get is "I've installed Blesta, what now?" Configure settings, install gateway, install module, create package, create order form.. those steps are the most common after install.

Blesta has required this since 3.0. When we decided to require it, as with all requirements, we gave it considerable thought. I don't see this changing anytime soon. Mailparse is a good library and any reputable hosting provider shouldn't have any issue enabling it. It works well, and it's efficient.

I'm not aware of any reason this should have changed in v4 off the top of my head. The guys will need to dig into it further on Monday morning. Are you able to implement a workaround, or disable the event in the interim? Bummer.

I think because we started using namespaces in 4.0, ApiGen organizes everything differently. Most classes are under "None", see http://source-docs.blesta.com/class-Upload.html It's possible some things are still missing, but it's also possible they are just in a different location relative to 3.6 http://source-docs.blesta.com/3.6/class-Upload.html

Do you have only 1 company, no addon companies in Blesta? If not, then the ID 1 in there is correct. Did the call get logged, check Tools > Logs > Gateway tab. Click to expand. Normally the client ID is passed to PayPal and included in the callback IPN URL, so that each client has a unique IPN URL. This isn't possible for these pre-existing subscriptions, so Blesta will look for a client email address that matches the one in the IPN request. If the clients email and their PayPal email is not the same, it will not be able to find it.

There is a VestaCP module, it will be on Github soon.