Leaderboard

I have bumped this up in the backlog.

I'll see if I can take a look at your system this afternoon. As for the email address, yes, as Licensecart mentioned, Blesta does validate whether the email's domain address has a valid MX record.

It's not very difficult to implement deletions. The hard part is in understanding the conceptual ramifications of performing the action. We'd need to integrate better logging of actions like these, especially since deletions are unrecoverable.

What star? Are you referring to the sub navigation in the admin interface? That's not a bread crumb, but rather a set of sub navigation links. You set those in your plugin through plugin actions (i.e. the nav_secondary_staff action). If you indeed want bread crumbs, I would suggest taking a look at how the Support Manager knowledgebase builds its bread crumb links.

Yes, One of the greatest benefits of using haproxy is the ease of dealing with SSL. I use it as the front-end for all sites, and now I have only a single place I need to keep/update certs for all domains. The SNI support in haproxy seems to work flawlessly. I run my proxies on CoreOS/Docker containers, and use confd to add/remove certs and hosts. Updating or adding a cert is as simple as cat certificate.pem| etcdctl set /services/haproxy/ssl_certs/cert_name This new cert will get added to /etc/haproxy/ssl/certs.d/ on all required haproxy containers, and haproxy reloaded. Adding a new Blesta host is similar. I simply add the new hostname to my blesta_hosts file, then: cat blesta_hosts| etcdctl set /services/haproxy/blesta_hosts confd then creates a new file /etc/haproxy/blesta.hosts which is configured as an ACL in haproxy. This ACL is then used to route these requests to my blesta cluster: acl blesta hdr_dom(host) -i -f /etc/haproxy/blesta.hosts use_backend blesta-servers if blesta -Barry

I often find reading text to be a poor medium for communication. As 70% of communication is miscommunication, the lack of non-verbals, tone of voice, and propensity to read between the lines, the likelihood for miscommunication only increases and it can be easy to misinterpret the meaning of words to come to an alternate, and unfortunately mistaken, conclusion. I believe that is the case here, as I am not placing blame or fault on anyone. I am merely trying to gather information and offer possible solutions along with my reasoning behind them. You mentioned: I just tested the email template on a new Blesta installation, but sadly, was unable to experience this issue myself. If it is indeed an issue with the default template, we would like to fix it immediately. That said, I have not had anyone else come forward yet with the same problem, so I only have your information to work from. I wish you the best of luck with your new system.

What Licensecart described can work, by allowing you to re-run the upgrade script. However, there have been other database changes since that version, so you could end up encountering more SQL errors (e.g. attempting to add fields that already exist). What is the SQL error you encountered when running the upgrade? If you're not able to resolve the SQL issue, you may need to manually perform the database upgrades on your installation. i.e., look at the upgrade scripts from /components/upgrades/tasks/ and apply them manually to your database. Make sure to make a backup.

The release notes look great. I can't participate in the beta at the moment but I'm looking forward to the final release. Keep up the great work.

This is why I never rely on third-party plugins, mods and themes -- especially anything paid (and ESPECIALLY anything obfuscated). I learned that lesson a decade ago. The whole "not releasing it, hmpf" attitude is a major reason why. It reminds me of a child: "If I can't have it, nobody can!" So it's nice to see a developer realize that open-sourcing it is needed. Otherwise the dev is really just screwing over existing clients.