Paul

Beta soon. Many tasks. Much fun.

Is your "Close Tickets" task enabled and running? Settings > Company > Automation - Close Tickets I believe the default is to run every 6 hours. How long ago did it last run? Is it hung up?

Is the last person to respond to the ticket a staff member? Tickets are only closed if staff last replied as you may be waiting for a response from the client that never comes.

I moved this into our "short term" bucket, it's come up a few times. CORE-504

We are getting close to a 4.0 beta.

iDevAffiliate has a plugin for Blesta, and they have a very extensive affiliate system.. much more powerful than the one we have planned. Extensions that work for Blesta 3.6 should work fine for 4.0. The only issues that might arise would be strictly cosmetic. For example, v4 admin area uses bootstrap buttons.. so a plugin that uses the current buttons may look a bit out of place, but it'll still work. We recommend cloning the client template and making your changes to that. Select the template under Settings > Company > Look and Feel > Template. Then, do a diff between the normal client "bootstrap" template from your current version and the new version to see what files you may need to change. If you change prices on the package level, it will affect renewing services that do not have a price-override set. So, if you have a monthly term for Package A of $10, and you want to raise the price by 10%, you can edit the Package and change it to $11 and everyone who is using it will be billed $11 at the next cycle.

Closing thread

There are some changes in the client area, but it's not a complete rewrite. When I say almost all files have changed, I mean mostly for formatting. That may make running a diff a bit of a hassle, but the number of client side templates with code changes is fairly minimal.

Not all tags are listed, see https://docs.blesta.com/display/user/Support+Manager#SupportManager-SupportEmails for a more complete list of available tags.

Oh, it only supports TLS 1.0, that may be the issue. Plugins/Modules from v3.6 will work in 4.0. The new minPHP is backwards compatible.

Here's a direct link to v4 development - https://dev.blesta.com/projects/CORE/versions/10603 We must have a lot of tasks private, there's 282 but it shows 152 issues in the version publicly. We are aiming for a beta later this month. Almost every single file has been updated in v4.

Nice work! Just curious, are there any screenshots of this in action?

The goal is v4 beta this month, but we still have some work ahead of us. No official ETA, but also not a good idea to use beta 1 in production. Running a report and using another mailer is the best way to go for now. Maybe Cody or Tyson can chime in with the proper query you can use.

I mentioned this is the documentation, thanks!

I wonder if Blesta is unable to communicate with Stripe. Is port 443 egress open at the firewall? CURL SSL in your PHP? Looks like stripe's API supports SSLv3, TLSv1.0, TSLv1.1, TLSv1.2.. which is pretty surprising - should be able to connect if your server supports any of those.

Most likely it is failing while making an API call through one of your modules for a service it is trying to suspend. You can check Tools > Logs > Module or Cron log to see if you can get additional information. It may also be a good idea to try manually suspending some of those in Blesta. If you have trouble suspending them, then the cron would have trouble also. I would check the API URLs for each module, and make sure that the firewall is open for egress on those ports.

Yeah, I think there were issues using Google direct at the time it was implemented. Maybe we didn't like the fact that we have to parse out the answers from HTML rather than a proper API.

Like this? CORE-2158 See screenshot.

It's not a bug, the API we were using just no longer works. See CORE-1108. Looks like we may are making an effort to get it resolved in v4.

Where do you recommend this information be displayed? Off the top of my head, I'm thinking perhaps in the expandable area when you click the invoice row but I can't help but think there may be a better way to do it.

See CORE-2157. I agree, will make things easier.

I do miss this feature from v2.5. It's good for staff to be able to specify which server to use when manually provisioning. See CORE-2156

What if we tracked and displayed who created the invoice? ie System or Staff Name? That might be better, because if it's a manual invoice you will know who created it.

A service search will search the service label. I have bumped CORE-1061 into our "Short Term" bucket.

It is using Bootstrap for the drop down menu. Also, there is a background hover effect on the subnav link rows for some themes. I believe it uses a color from the gradient in the bar that contains the search. Since this FOUR theme does not use a gradient here, the hover background is the same color.