Paul

That looks pretty cool. Cody and I were actually discussing the possibility of supporting file based HTML email templates in the future. This would add a drop down on the email template page that would let you select a pre-made email template. The template would contain the header and footer, and then anything you enter into the WYSIWYG editor would appear in the content section. While HTML can be used in the templates now, through the editor, this would simplify things dramatically when supporting rich designs, give people that flexibility, and allow a market to open up for email template designs.

We are planning to add the ability to update directly from within Blesta. There will be options for stable release, or beta. It's not a super high priority right now, because there are other features more heavily requested. It's also not something we want to screw up.

Just attempting to populate some data into their system, we found a lot of weird bugs. I think there was one where you can add events to the calendar, but they don't appear on the calendar. Are you experiencing that one too? We checked the database and they were in there, so we know how to import them at least -- and they should then appear on the Blesta calendar.

Never heard of it, looks pretty interesting though. Curious what you think of it after you give it a spin!

The one in Yosemite? 350 miles from here, can't tell there's a fire but it looks pretty crazy on the news.

This belongs to CORE-621. No official ETA, but it is planned. You can use HTML, but no pre-selection of templates or a super robust interface like Campaign Monitor or Mailchimp. (We actually recommend these guys for mass email marketing, they have nice analytics)

We hope to have something for you to test pretty soon Dave. We will be reporting our security finds through the proper channels, in the proper way. I can only imagine what we would find if we were performing an actual security audit, and not just stumbling around like a normal user. We are extremely grateful when we are contacted privately about possible security issues in our software.

Nice work!

It's almost annoying how vulnerabilities jump out at him. I could hear gasps of shock at my desk as he went through it.

Is your server doing any caching of its own?

Yep, just click the "Manage" link next to your license, and check and save reissue under "Manage License".

None of the CSS should have changed in relation to that, and I'm not sure anything really changed since the beta. Very strange indeed. Have you tried on any other computers?

Looks pretty slick. What do you think of a "best theme" competition? People can create their best themes, then we can vote on them as a community.

I saw the video, looking good!

We will mention it someplace, yes. Probably a forum thread, with the files attached.

As needed patches. Let's not get ahead of ourselves now.

Are both showing tickets for their respective companies? When I tried this, ajax would refresh the ticket content and pull from the last company selected.

Nonmerchant gateways do not save any payment details in Payment Accounts, like merchant gateways do credit card and bank details. What gateways currently request these additional fields? If they have API documentation we can look at, it would be helpful.

Do you think the ability to enter a language definition in the terms field, which will pull from the custom language file is the way to go? Or, allow it to be entered in each language as with email templates? Curious what everyone thinks, and thanks for the suggestion!

My bet is Google becomes more and more hostile to the hosting industry, as they encroach further and further into it.

I do like Plesk, I'm just not too happy with their API. Thanks for the code contribution, glad you were able to get that to work in the interim and looking forward to CORE-622!

Nice tips, but not sure #2 will work, unless you use a different browser for each company.

The Universal Module will most likely work for you. The Universal Module allows you to create a "Product" with service fields that ask the customer the information you need. For example, you can create a service field in the Universal Module for the hostname, another drop down for the desired OS, etc.

/index.php/admin/upgrade is correct, if mod_rewrite is not being used. If that's the case, all URLs will have /index.php/ followed by the typical path structure. Of course, we recommend using mod_rewrite with the included .htaccess file, but some servers don't support it or don't have it installed.

Which were erased? This patch doesn't touch the database, so no module data should be erased.