Paul

Some people asked similar questions, but I'm still not sure. If you're up for asking, that'd be cool. I have a backlog of tasks today to get through.

Yes, domain sync is necessary and would be handled by the plugin component.

I couldn't find which plan would apply, but say we wanted to include font awesome pro with Blesta. Which license would we need?

Oooh, nice. If I had a spare $2k to blow, we'd be getting a Blesta happy face icon.

The beta 2 distro was updated to build 107 from 105 because the build failed to encode the files. If you already downloaded beta 2, there's no need to re-download it, functionally it's the same. Also, I discovered an issue with package creation. We're working on a fix and I expect we will release either a hotfix or beta 3 next week.

What version of PHP? I did a fresh install and an upgrade in my testing without any issue. I tested using PHP 5.4.

Oh, be sure to run ~/admin/upgrade guys, there's database migrations that need to run.

Blesta version 4.0.0-b2 (BETA 2) is now available. You can download it from right here (Client Area Login Required). If you haven't seen the blog post announcement for 4.0.0 BETA 1, you can read it here. This is a BETA release. Beta releases are not considered stable enough for production use, and are UNSUPPORTED. DO NOT INSTALL IN A PRODUCTION ENVIRONMENT. Please report any bugs you find in the v4 beta bug forum. Installing Blesta See Installing Blesta in the User Manual for instructions. Upgrading Blesta See Upgrading Blesta in the User Manual for instructions. Release Notes See Blesta Core - Version 4.0.0-b1 and b2. SEE BETA2 ONLY For older releases see all Change Logs. What to Test! 1. New The SSL Store Module and Plugin. Please test the module and plugin. The module allows you to automatically create a package for all of The SSL Store's SSL products. When doing this, please create a new Package Group first, and select this as the Packages will be placed in this group automatically. If you don't have an account with The SSL Store, create one here. 2. Void unpaid invoices when cancelling a service 3. Multicraft, which contains 2 fixes. Plus misc. other bugfixes from beta1. See the changelog. 4. Test everything! Version 4 is a major release.

Blesta doesn't currently ship with a composer.json file, we remove it when we do our builds. So, I think you'll be fine. We may include it in the future, as we maintain our own composer repository here - https://composer.blesta.com/

I don't think so, but I could be wrong. You could try the same vars that are available to invoices like {year} {month} {day}, it might work, not sure as it's not documented.

There's no built in way to randomize them. However, you could prepend and/or append other information, or have them increment every X. For example, the following would be possible: ABC-1500 ABC-1505 ABC-1510 (Starts with ABC, and also increments by 5 at a time) This cannot be changed in the UI, but can be changed in the database. Look for company_settings.clients_format and company_settings.clients_increment where company_settings.company_id=1 (Or your company ID if multiple companies) company_settings.clients_format must contain the {num} tag in there someplace. So, not random, but you may wish to increment by more than 1. clients_increment contains the increment value (default 1)

I suggest creating a new stylesheet called something like overrides.css, and include that in structure.pdt at the end. This way your custom styles overwrite the originals and your overrides.css file won't be overwritten on upgrade. (You'll just have to add back the include in structure)

Is the config.json properly json formatted like Mike's example? What is the name of your template directory? Compare it with the bootstrap directory, the directory structure should be identical.

Nice doc Mike. Yes, enabling legacy passwords will allow MD5 passwords to work. However, once a client logs in with the MD5 password, it will be changed to a bcrypt HMAC SHA-256 hash.

https://haveibeenpwned.com/ Just stumbled across this site, let's you enter your email or username and find out if your account details were leaked in any known breaches. Turns out my details were stolen from Adobe, LinkedIn, and vBulletin. Fun. Good idea to subscribe to notifications if your details show up in any new dumps, since not all companies notify their user bases.

It would be nice if the common fields were standardized.

I don't see how it's possible to login and access a different customer account. The username must be unique, and when you select "Use email as username", Blesta just saves the email address you entered as the username. Usernames are all stored in the same location, and you must authenticate with the username, not the email address. Now, back to the topic. Quite a few people have asked for the ability to restrict additional signups using the same email address. This would go hand-in-hand with a setting to force email addresses as the username, and effectively remove the option to specify a different username. Now, as is the case with us, we have customers who have multiple accounts as a matter of necessity. The same person manages the accounts, but the accounts are for different entities. So, for us this restriction would be detrimental. We created a task for this as part of CORE-1387.

Some people will consider the confirmation link an unnecessary hassle for the vast majority of ticket requests. However, I do think showing the method by which the ticket was created would be useful in helping staff determine how to proceed. The link would need to be a setting, and is more complicated to implement, so I'm thinking mainly shorter term. Sound good? Any suggestions of where we would want to show how the ticket was opened?

Yes, if you purchase a license for production you can use a separate license (trial or dev) for a separate install of 4.0 beta.

Probably not. If you upgrade the 3.6.2 install to 4.0 beta 1, then it'll work.

I don't have an ETA unfortunately.

Is it configured properly? I'm not aware of any other reports. LicenseCart has been accepting payments with BitPay, and so have we.

Where did you get the logo? Something that mixes the idea of chemical and servers together would make more sense. For example, a test tube coming out of a rectangular box or something. Still, better than the old one

Right now it's mostly geared toward plugin, module, gateway development. If we open it up to theme integrations as well I'll add you then. Cheers

Overall I like it, but Mike's right a nice logo will do wonders.