Jump to content

Paul

Blesta Developers
  • Posts

    6,581
  • Joined

  • Last visited

  • Days Won

    817

Everything posted by Paul

  1. Blesta uses different encryption and hashing algorithms for different purposes. Admin and client passwords are stored using bcrypt, computed from an HMAC-SHA-256 hash of the password. This is a one way, algorithm that is extremely difficult to brute force. User passwords are not reversible. Modules can store some or all of their meta data encrypted, and encryption is used throughout the system to securely store data that can be decrypted like credit card numbers, service meta data and more. I believe this is done through AES, and in the case of credit cards additionally an RSA public/private key pair. Cody can elaborate more on all of this and correct any errors in what I just said.
  2. Price overrides are something we have thought about and would consider, but this would be a feature request.
  3. CORE-746. On successful registration, redirect to the Dashboard and display a success message.
  4. I believe matching packages is much simpler to do than importing packages, in terms of development. We'll see what Cody says, but I think the goal was package matching first, and revisit for package importing. In terms of usability, importing the packages is preferred so I definitely want to see it in there. We want to make migrating as simple and complete as possible, but it is a challenge considering how different these two products actually are.
  5. I don't see how it would have come from the import, if these are newly created invoices. There was a directory path issue for sub directories that was corrected in 3.0.1 or 3.0.2, but it sounds like you may be running 3.0.2, so I'm not sure what's going on.
  6. Is it suppose to be my.hostingdifferent.com? Are you running 3.0.2, and is the path under Settings > System > General > Root Web Directory correct? And is the hostname correct under Settings > System > Companies?
  7. If the invoices were generated prior to the import, any payment URLs will be invalid. If the invoice was created in Blesta after the import, it should work. Email templates should not be imported.
  8. In the PDF? Can you provide an example?
  9. Paul

    Awbs

    We haven't had many requests for an AWBS importer, I doubt it's one we'll be building soon. The first link I clicked on their "Who's running AWBS" page was actually running WHMCS, which may have been a coincidence but it doesn't look like they are being used by many people. The latest news is from Feb 2011.
  10. Where are you seeing old URLs? Do you mean in the mail logs?
  11. Blesta is less annoying about those kinds of things, the biggest thing is the cron.. though I can see mentioning the uploads directory as people generally don't set that until they try and fail at uploading something.
  12. You could modify the invoice template file to remove the customer number. I believe the file you want is components/invoice_templates/default_invoice/defailt_invoice_pdf.php. Look at lines 409-413 in the drawInvoiceInfo() method.
  13. We are planning to add some overall ticket stats like average response time, average resolution time, etc in the admin area. Do you think these averages should be displayed to the customer so they have a rough idea of when they can expect a response? If so, how and where?
  14. Paul

    A New Member

    Welcome, good to have you!
  15. I would double check that port 465 egress is not being blocked at the firewall.
  16. You do realize that the original reply would have already been emailed to the client though? How does this affect, if at all, the need for editing replies?
  17. Are you using the currency format "1,234"? I wonder if we need to look at the currency format, and if the format does not support decimal, then we round the whole number.
  18. It currently ranks pretty low on the priority list, since the addresses can be updated. (In about 3 min for all templates) but it is a usability feature and I can see the advantage. It has been requested before and we are considering it.
  19. CORE-607 is in our tracker for adding the ability to split tickets. Splitting a ticket would create a new ticket and assign all replies after the split point to the new ticket. This is tentatively assigned to 3.1, but it's more likely to be released after 3.1.
  20. The HTML fields are not hidden for email templates if HTML is disabled because then you'd be unable to edit the templates and add HTML prior to enabling it.. it would result in some people receiving blank emails if no such content exists in HTML. Enabling HTML simply adds the HTML content to the email. If it's disabled, all email clients should see and render the text version only. If it's enabled and the HTML content is blank, HTML enabled mail clients will show a blank page.
  21. We are using SMTP and haven't experienced this issue. Are you saying that email delivery via SMTP fails all of the time, and that these emails are not properly logged? If so, there may be a bug in there with logging failed emails, however, if your mail always fails via SMTP I wonder if there is a configuration or firewall issue. It seems that would be the first item to resolve, with any logging issue being secondary.
  22. Beta forums will return when beta for 3.1 starts.
  23. I used this feature today and didn't have any trouble. If you are only sending text content, then it may appear blank until you click over to the text version. Additionally, the overview, before you hit resend shows the text version so if you only send HTML then this section might appear blank also.
  24. It is direct, and it was purchased in July. The license has support & upgrades through Aug 14, 2014.
×
×
  • Create New...