Paul

Alright, I don't normally do this but I'm going to close this thread. No offence to the @jassdesi, and I hope my response was informative. I hope everyone has a good week.

We're about to start development on the new Domain Manager system. To be perfectly honest, v4 took way longer than we expected. It was much more involved than we thought it would be, and it pushed off domains. We're taking a hard look right now at all of the discussions about domains, and it looks like we're going to stick with the KISS principle. (Keep It Simple Stupid). Even so, improving domain support is a big deal and we're not going to let it prevent us from coming out with other releases while we work on it. It's likely that the domain system will be implemented almost entirely as a plugin, though there are some core changes that are necessary like packages being able to defer their pricing to plugins. Aside from any core dependencies, the domain plugin may be able to be released as a beta on its own where we look forward to getting more feedback from the community. Since there are also other important things that need to be done as well, we are going to work on those things simultaneously and reduce the time to release. Domains will be included when it is ready, but we aren't going to hold back releases as a result. I hope that makes sense, and I understand how frustrating it is not to already have better support for domains. Just know that we're working on it, alongside other things, and will release it to the community when we have something ready to test.

Have you made any changes to the order plugin? At first I thought you meant you created a custom order form and that caused the issue, but it sounds like maybe it's all original code? It might be possible that some of the order plugin is missing, I would try re-uploading. Then, try enabling system debug and error reporting in your /config/blesta.php config file. Error reporting from 0 to -1 and system.debug true

You need some new flat v4 inspired themes

Sounds like this is pretty solid, but here's my 2c anyways. If you know how to do it, I recommend a manual install. That way you know exactly what's happening, and you'll be more familiar with the process in case anything comes up. Softaculous is great, but if you have the technical know how I would install it yourself. It's still pretty easy, but yeah, will take a few more minutes that using Softaculous.

If you do it manually, existing subscriptions will need the redirect but new subscriptions would not. It's just a single line you'd add to your .htaccess file. It works with whimps, but I have not tested it on CE, but I don't see why it wouldn't work so long as you replace the beginning path with that which CE uses.

If you sound out whmcs, it comes out whimps, it's just easier to say. Regarding PayPal Subscriptions, you may need to add a rewrite rule to your .htaccess file in Blesta to remap the URL. Per https://docs.blesta.com/display/user/WHMCS+5.2:(But you should replace with whatever CE is) Redirect 301 /modules/gateways/callback/paypal.php /callback/gw/1/paypal_payments_standard/

To clear the cache you can also simply re-save your staff group without making any changes. Settings > System > Staff > Staff Groups. Edit Group, click Save.

We will consider building a CE importer, we've had quite a few requests for it recently. In the meantime, you can take advantage of the whimps 30-day money back guarantee. Get a monthly license, do the migration, then cancel and get a refund.

mobiledetect looks great, will have to check it out

We don't allow testing of any kind in our live environment. If you want to test Blesta out, please download and install the 30-day free trial.

Version 4.0.0 is now available. You can download directly right here. Installing Blesta See Installing Blesta in the User Manual for instructions. Upgrading Blesta See Upgrading Blesta in the User Manual for instructions. Migrating to Blesta See Migrating to Blesta in the User Manual for instructions. Overview PHP 7 is now supported. Major codebase upgrade to new version of the minPHP framework. Mass Mailer plugin lets you send email to specific customers, or export the data. Clean new FOUR staff and client area themes, and new dropdown staff menu. Fantastic looking interactive graphs let you see a breakdown of revenue by payment type. New client order link and permissions based order form listing page. Many order form improvements like reCAPTCHA 2, GeoIP state/province selection & more. Fantastic new The SSL Store module and plugin. Create an account and start selling now. Blesta License Module is now included with Blesta for Blesta resellers. Tons more... Directories Removed in 4.0 The following directories are not in the 4.0 distribution, but were in 3.x. If upgrading, you may remove them. ~/helpers/date ~/helpers/form ~/helpers/html ~/helpers/javascript ~/helpers/pagination ~/helpers/xml Release Notes See Blesta Core - Version 4.0.0. For older releases see all Change Logs.

It's possible it tries to run the card anyway, until it fails and auto debit is disabled. It probably wouldn't be a bad idea to skip it if the expiration date has passed, but I'm pretty sure it's always worked this way. On one sense, the customer gets a notice that the payment failed and that may prompt them to update it. On the other hand, it's expired so it's going to fail.

Version 4? Yeah, really, very, super, soon. Version 5 though? Probably not for a while

Nope. You should be on Beta 6.

It just occurred to me that this error is displayed if a client tries to log into the wrong company. Are you using multi-company? Is the client logging in at the right URL for the company they belong to?

The System Overview widget should probably be updated to include Contact logins. Contact Login feature was added after this widget was created, so it may have been an oversight. https://requests.blesta.com

@Internetport just a quick note as well. A different process creates invoices as emails them out. So, sending email will not inhibit the creation of invoices in any way. When they are sent, they are marked as sent as they go out. So, if for some reason some do not go out due to an error or otherwise, they will be tried again later.

I suggest using a transactional email service like Mailgun for SMTP mail in Blesta. It's fast and there would no need to rate limit. The issue with rate limits is, of course, that people with a large number of recipients may not see all the email go out for a very long time. Blesta does start a new SMTP connection after a certain number of recipients as well, so this does slow it down some. I don't think we've heard from anybody that had an actual issue from too many emails. We are open to setting rate limits in the Mass Mailer plugin in a future release, but I'm curious to see how many people ask for it.

Yes, that's correct. CSRF is still enabled everywhere else.

Done and tagged as version 1.3 on Github, and will be included in 4.0 final.

Most CSRF attacks are to perform actions as an authenticated user. For example, the form that creates a new admin in Blesta would be a good target for a CSRF attack, but you'd have to be logged in and CSRF disabled for it to work. If I had to pick a page to disable CSRF for, it'd be an unauthenticated page, like the login form. It might be possible by modifying the code, I don't have an example off the top of my head for you though, and I probably wouldn't recommend changing the core. Might be a good feature request though, to be able to set where the user is directed after a log out.

It depends on your backup. If you follow this guide though, you should do well - https://docs.blesta.com/display/user/Moving+Blesta If your backup has all of your Blesta installation files and your MySQL database, then your backup should have all you need, but it could be a little out dated depending on when your backup was performed.

It looks like the 1st item in the list is using a private IP 10.128.x.x, which is mapped to a public IP 35.184.x.x? Is the public IP address a shared IP? If it's a shared IP, shouldn't it show the default page? Sorry if I'm not understanding, I'm assuming that by default page you mean the standard page that's show when accessing the IP address in a browser rather than the website's content that's usually displayed when accessing a shared IP rather than a dedicated IP. Or is that public IP address a dedicated IP? If it's a dedicated IP, and it only maps to 1 local IP, there may be some other issue going on with Plesk.

Teamspeak is supported through this new TCAdmin 2 module -