Paul

I wont hold it against you. You use to be able to disable the address bar in Safari, which was fantastic for recording videos. They removed the ability to do that, because of "security reasons", meaning that people might not be able to see the address bar and more easily fall for spoofed sites. So, I'm not feeling much love for Safari either. They did fix a bug though, that would cause the check boxes in the graphs not to appear at all.

If you create a single feature request for 20 features it's pretty much guaranteed to be ignored. When we consider a request, and change it's status to "Planned", for example, it means we are planning to do what the task describes. If there are 20 things in the task, and we only plan to do 5 of them, well, you can see the problem. Now, if the feature request is something like "Add an Affiliate System", we don't expect that to be broken down into every feature of the affiliate system in separate requests. That would be ridiculous. While there may be many parts to an affiliate system, it's a single new feature. Making 20 changes to an existing feature isn't a single request, it's 20. And that's what we're talking about when we're talking about adding improvements to the Support Manager. For example, this request - https://requests.blesta.com/topic/support-tickets-add-a-from-column-on-ticket-list-page is very specific, and concise, and it has already been scheduled for development. This is a good example of a feature request. Thinking about it this way makes it easier for us to look at a request, approve it, create a task for it in Jira, and follow it through to completion.

I only really use Safari on my Mac, and I don't use my Macbook every day. I suspect it's a possible bug in the NVD3 Library, or the browser, or a combination of both. I'd suggest trying Safari and see if you experience the same thing with it on your Mac. It may be helpful.

Not a clue, but glad that did it for you!

If you use a coupon for the initial order, you can link directly to it to automatically apply the coupon. From https://docs.blesta.com/display/user/Order+System: /order/main/index/label/?coupon=CPN123

I've never seen the graph bleed out into another graph. I've only experience a blank graph, and not all that often. What browser are you using? Have you tried using a different browser to see if it makes a difference?

Version 4.0.1 is now available. Please see the announcement. This is a patch release that corrects issues with 4.0.0. Patching Blesta See Patching Blesta in the User Manual for instructions. Release Notes See Blesta Core - Version 4.0.1. See all Change Logs.

FYI, http://source-docs.blesta.com/ was updated with our 4.0.1 build, and we modified how the docs were built slightly to improve it.

Fantastic! Some people have been asking for something like this.

There is a bug in 4.0.0 where a module row that isn't in a group may not populate options when selected. We've implemented a fix for 4.0.1, and we have a build running now for QA.

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.