evolvewh

I just received this email from Authorize.net today and it appears an update needs to be made but I'm not a skilled enough coder: Dear Authorize.Net Merchant: As you may be aware, new PCI DSS requirements state that all payment systems must disable earlier versions of TLS protocols. These older protocols, TLS 1.0 and TLS 1.1, are highly vulnerable to security breaches and will be disabled by Authorize.Net on February 28, 2018. To help you identify if you’re using one of the older TLS protocols, Authorize.Net will temporarily disable those connections for a few hours on January 30, 2018 and then again on February 8, 2018. Please refer to our TLS FAQs for important details. Based on the API connection you are using, on either one of these two days you will not be able to process transactions for a short period of time. If you don’t know which API you’re using, your solution provider or development partner might be a good resource to help identify it. This disablement will occur on one of the following dates and time: Akamai-enabled API connections will occur on January 30, 2018 between 9:00 AM and 1:00 PM Pacific time. All other API connections will occur on February 8, 2018 between 11:00 AM and 1:00 PM Pacific time. Merchants using TLS 1.2 by these dates will not be affected by the temporary disablement. We strongly recommend that connections still using TLS 1.0 or TLS 1.1 be updated as soon as possible to the stronger TLS 1.2 protocol. If your current Virtual Point of Sale (VPOS) is an Authorize.Net product, please call Authorize.Net Customer Support at 1.877.447.3938 for assistance in updating to TLS 1.2. Note: If you are not using a current version of a web browser, please take a few moments to upgrade it now. Browsers released prior to 2014 may not support TLS 1.2. You can check your browser's TLS support by visiting https://www.howsmyssl.com/. If you have any questions about this email or the upcoming TLS disablement, please refer to our TLS FAQs. Thank you for your attention to this matter and for being an Authorize.Net merchant. Is anyone else receiving this email?

Expanding on this at some point would be nice but I still personally think the domain manager is a bigger priority.

By default, there's nothing else you can do. While the support system does work overall, it's very light in terms of efficiency features.

That makes more sense and thanks for that explanation. I would have thought that 'invoiced this month' would not include pending invoices until they actually got sent out and it doesn't include recurring invoices. We do have pending invoices for later this month.

@Tyson 1) Server time is MST where we are located 2) I'm not sure how I could have existing invoices with a bill date between Jan 2 and Jan 31 when the screenshot was taken on Jan 1. HowCan you explain that more?

If I get a chance to go through all of that. It's picking something up from the last 2-3 days of 2017

The difference is $647.46 - $87.40 at the time that screenshot was taken so it was $560.06 too high under 'invoiced this month'

Today, we show a significant difference between 'invoiced this month' and 'invoiced today'. Blesta v4.2.0 and no modifications made to billing / invoices.

Uploading the license.php file in the php7 hotfix folder won't prompt you to do a new install. Is your config/blesta.php file present with all of your database credentials and the system key? Also, if you haven't yet, I would suggest doing the upgrade on a copy of your database and have the latest files uploaded in a new folder to test everything out first.

Sorry but I still don't know what development work you actually need done. You'd need to show someone what you have in place already.

What are you looking to have completed?

I ran that query and no results were returned. I will have to look closer and see if I can find any domains that don't have valid DNS / MX records but that same email address receives other invoices and support ticket notifications.

Logicboxes had no issues but we've seen it 3 days in a row with cPanel now. Tyson is looking into this as well.

Thanks Tyson. The clients email is valid and they do not have any invoices created that haven't been delivered. They have a couple of pending invoices for February and further out and one recurring invoice that doesn't go out until next Summer.

I found this in the cron log today for invoice deliveries: Attempting to deliver invoices scheduled for delivery. Unable to deliver 15 invoices to client #73 via Email due to error: At least one of the email To addresses provided is not a valid email address. The deliver invoices task has completed. This client doesn't have any services due in 7 days (our Invoice days before renewal setting) so I'm not sure why it was even trying to create any invoices for them today. It's in the log multiple times. This is v4.2.0 Blesta

I need to know how to stop this ASAP. We upgraded to v4.2 and all invoices today billed for 2 months of service when they should be monthly only. How do we downgrade Blesta or get a patch as quick as possible? For us, this has happened with cPanel related services only so far. Can anyone else confirm?

If you have may significant changes, you may want to look into programs that are far superior to Dreamweaver. Some examples include Github, Diff Merge (Mac Program), Win Merge (Windows Program). A quick Google search will turn up plenty of results for you.

If you write down the files you changed and the line numbers, you can manually apply your changes to each release in less than 5 hours. Our install has a lot of changes too and it takes us less than an hour by having the files and line numbers documented. There are many ways to do this and it's just a matter of figuring out what works best for your case.

There are a LOT of files changed since this was a major release. Personally I think you're better off documenting the changes you have made and then you can apply them to each upgrade in the future.

You can use PHP 7 or 7.1 with 4.2.0. There is a folder for the 7 and 7.1 Hotfix and you need to apply one or the other. This was a big release so there isn't a patch version. You'll want to use a program like Diff Merge (on a Mac) or something similar on the Windows side to figure out what changes you made and get them merged into 4.2 Someone else probably has alternate ways to do this and hopefully they will chime in @BlestaStore

It would be in public_html/config/

What is the progress on this? Is this something that can be sponsored to speed up development or is it likely to become available in 2018?

Please add the ability to re send welcome emails to clients as part of the core.

Adding something to the core would be great. Looking at Squidix's code, it's only about 15-20 lines of code and would be nice to see Blesta add something similar even if it's tweaked a little bit. It's getting harder to upgrade with the more customization added.

I am seeing a small issue with this though. When the service is initially added and the welcome email is sent, the customer gets 2 emails. I have not seen this before I added this code either. The actual process of going back and resending the email later works just fine.