Paul

We suggest the default settings for both of those fields, 80 to reject and 10 to review. The defaults are pretty conservative and unlikely to reject or require review for non-fraud orders. If you aren't sure, leave as-is and adjust as necessary once you get a feel for the scores.

Nice! How's the printing, come out good?

Do you find most attacks originate from the same location or email address? I can see an internal blacklist being useful for that 1 pesky person who won't stop opening tickets or placing fraudulent orders but most of the time the stuff we see is distributed.

Thanks for the suggestions, most of these we will definitely be implementing. Our development process is iterative, and we often circle back around and improve existing features. I don't have an ETA for these changes, but I'm curious what the community thinks in terms of priority.. which of these items are most important?

You can add a Tax ID/VATIN under Settings > Company > Taxes > Basic Tax Settings.

It changes with each new session. In config/blesta.php look for this line: Configure::set("Blesta.csrf_bypass", array()); You can add controllers and actions to this array to bypass CSRF checks, for the client login it should be array('client_login::index') so the following should work: Configure::set("Blesta.csrf_bypass", array('client_login::index'));

Anyone else experiencing this? Do you also have Blesta installed in a sub-directory?

I'm pretty sure you will need to disable csrf tokens for the login page in the config file.

UK, Canada, Australia all use Celsius for temp right? I'm finding myself using Google to convert these to Fahrenheit so I can make sense of it!

That's a good reason. I actually get a reminder about auto-renews a week or so in advance so have the opportunity to cancel the auto renew, which I often do for domains I later realize I will never use.

Yeah, it's good through May 30, 2023, don't have to worry about that expiring anytime soon. I wonder what their reason is for capping it to 10 years.

I always have domains set to auto renew, and important domains I usually renew out far in advance.

I think that's a pretty common practice nowadays, especially for domains that have any kind of significant traffic.

It's still a work in progress, I wanted to finish up a little more before I put it up. Shouldn't be long, and it won't be 100% done but would be nice to get some feedback.

Which layout? The website?

This is sort of in-progress but it's unlikely to make it in the 3.0 release.

Looks good! Are those the same colors as the blesta logo?

I'm not no, back on Monday.

That's the way to do it, makes it easy if the website is pulling the pricing directly.

Hey nice! I don't think we got any of the hoodies, let me know how it turns out.

https://160693.spreadshirt.com/ The "Mens Blesta Shirt", I think the navy blue one is what Cody wore to HostingCon. Available in navy blue, green, and black.

If I have time today I'll upload it

Just a note on this in terms of PCI -- Blesta logs all credit card accesses by staff under "/admin/tools/logs/accountaccess/", as well as all contact changes, and much more. You can always see when a staff member accesses a credit card, and only those staff members who have the key can view them anyway.

The new website is built on Wordpress, it makes it easy for us to keep it updated and import all blog posts from the current website which runs Wordpress also. I basically just created a whole new WP theme, and re-built all the pages and content.

At HostingCon this year Cody and I went to a session by Douglas Hanna from A Small Orange titled "Making a Remote Workforce Happen". I was interested to know how you can be sure your remote staff is working (Even though we have no remote staff). His answer was that you pretty much just know. Of course, you have to be paying attention but at the end of the day, check on productivity.. did they get anything done? How much?