Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Kal last won the day on November 25 2019

Kal had the most liked content!

About Kal

  • Rank

Profile Information

  • Gender
  • Location
  1. Perfect!! While I'm saying thank you, thanks for all the great new features in 4.11 too. I especially appreciate the ability to enforce email address usernames—something I switched on straight away. 🙂
  2. I had wondered if structure.pdt would get overwritten with an update. Indeed it does. This also makes the official instructions for Removing Branding a temporary fix, which isn't mentioned in the docs. Since that feature is advertised on Blesta's pricing page, I'd have hoped for a more robust method. DirectAdmin has a feature where customised config files can be placed within 'custom' subdirectories to protect them from being overwritten. Maybe something like that could work for Blesta? Adding these features to the UI would be even better though. @Paul, you mentioned above that style overrides were coming to themes, and there was talk on this thread of possibly removing branding automatically from unbranded licenses in the future. Are those features still on the roadmap?
  3. @turner2f Did you end up writing that post? This is exactly what I'm looking for, but this is the only thread I can find on the topic.
  4. Emoji support would be good. I'm surprised this hasn't come up before—I just assume many people would try inserting emoji, so I tested it. Failing that, could you just strip out any non-recognised characters so that the message still goes through?
  5. Yes, when I said 'departments', I wasn't specifically referring to Blesta's feature for categorising support tickets—rather the actual departments they refer to in your business. They are the common link aren't they, between these currently unconnected elements in Blesta? A simple table of corporate departments could contain the email address, signature and even the support category (Department) for each one. While I suppose you're right—it doesn't take that long to go through and change each template—wouldn't this still be an improvement? Is there a good reason to leave it as is, and require the user to update the same email address repeatedly throughout the system? That approach invariably leads to human error, as illustrated by one or two inconsistencies in Blesta's own default templates. This is what relational databases are supposed to save us from, no? Perhaps my suggested feature would break things for existing users. If that's the case, sure, giving users the ability to simply change the domain used for email addresses would be an improvement. You could even make it recognise subdomains and choose the main domain by default, since probably 99%+ of users are going to use email addresses like [email protected], not [email protected] Edit: I just noticed that this was requested here: Update Global Email Address.
  6. Entering an emoji into a support ticket message (by either client or staff) causes the Reply/Update to fail. There is no error given—just a blank screen. (I'm testing on macOS, using the standard character panel to insert emoji.)
  7. The email templating system pre-populates the 'From Email' fields with addresses like [email protected] and [email protected] If you install Blesta on a subdomain, you'll get email addresses that look something like [email protected], when you probably want [email protected] Or maybe you want something different, like [email protected] Either way, the only way to fix this appears to be to manually edit the From address in each and every template. (See where others have asked about this: From emails how to change?, Problem With Sending From Email Address and Wrong Email.) Could Blesta not store an email address for each department (admin, billing, sales, support), much like it stores email signatures? It might also make sense to link a default 'From Name' and Signature to each department, so you only have to specify the address (or the department) and everything matches up automatically. (As if to illustrate the potential for mistakes, when these details aren't linked, the default Account Registration template is from Sales, but the From Name is set to 'Billing Department'.)
  8. Did this ever happen? I'd like to lose the drop shadows too. 🙂 Edit: I worked around it by creating a custom CSS file in app/views/client/bootstrap/css/: .nav-content .navbar-default .navbar-nav > li > a { text-shadow: none !important; } Then I linked to it from app/views/client/bootstrap/structure.pdt. It works, but is there a better way to do it?
  9. No worries! I was just checking out Blesta as I consider whether to automate my billing (for a small number of clients), and signed up to the forum when I saw this discussion, as I thought the Rack911 audit could help others here. (Blesta looks great BTW.) Yeah, sounds like everyone (Rack911 included) had high hopes for it! What a shame they developed it without the necessary security focus or knowledge. For me, this means paying license fees I thought I could save by moving away from cPanel… 😞 but I figure it's just not worth compromising on security with web servers.
  10. One factor not mentioned here so far is security. RACK911 Labs just did a security audit of alternative control panels and the results are enlightening! I was thinking about going with CWP or CyberPanel before I read this. After reading it, I decided to go with DirectAdmin instead. (I can't comment on it beyond that, as I haven't switched yet.)
  • Create New...