Jump to content

wfitg

Members
  • Posts

    205
  • Joined

  • Last visited

  • Days Won

    2

wfitg last won the day on January 2 2016

wfitg had the most liked content!

Contact Methods

  • Website URL
    http://wfitg.com

Profile Information

  • Gender
    Male
  • Location
    Deep In The Delta Quadrant
  • Interests
    Are you kidding?

wfitg's Achievements

  1. wfitg

    Reset Password

    How can I remobe the "Reset My Password" link on the staff login box?
  2. I see the need for some businesses to keep emails on file. In some cases it is a legal requirement. I like the idea of having the option to truncate.
  3. I like the clustering and the truncating ideas. However, I think I will first try a seperate database to store email.
  4. I have not found a way to encrypt only the emails. There is a way to encrypt specific lines of an database. Why couldn't these emails be forked to a seperate "email database"? This way there would be no need to archive them. They could be kept on file forever.
  5. Saving the welcome email is good. Saving the welcome email with the password in plain text is not good. The welcome email should not include the variable {password} by default. It is too easy to overlook when doing the initial Blesta setup. IMHO - It would be better to archive any emails older than 6 months or a year rather then have the database grow huge. 100 clients getting an average of 2 emails or more per month is 2400 or more emails in the database over the course of 1 year. The emails are stored in plain text. That personal information could be a gold mind if the database got hacked. Time for some individual encryption, But, can only the mail be encrypted in the DB without having to encrypt the entire sql> ?
  6. I certainly see the need to keep emails on file for 6 months or even a year. And you make a good point. Personally, I would rather have the ability to archive them, or delete them after so many months.
  7. wfitg

    Release 3.3.0

    So how is the new version? Anyone care to share likes and dislikes?
  8. Exactly. I went in and removed the pass from each of the emails. But if the emails do not rotate the database could get huge. We need a way to archive them or delete them. The variable {password} should not be included in the welcome email by default. It should be an option that comes with a warning, or not available at all. I don't know anyone that sends the user name and pass in plain text email these days.
  9. My suggestion is having a delete button next to the email when we "view client email". Otherwise the log could get huge.
  10. I found the rotation settings. Here is my concern: The "Welcome Email" sends the user name and password by default. {username} {password} variables. I have changed that to say password: "the password you used when signing up" However, the old email with the user's name and password is being stored in the database in plain text. There is no way to delete it without manually changing the database.
  11. We need a way to clear the logs. In paticular, the email log that can be viewed for each client.
  12. I have spaced out the time intervals under settings/automation. I had several settings running every 5 minuets. I noticed there was a spike at around 3pm. This is when the load was the heaviest. I set this to run overnight instead of 3pm. Hopefully changing the settings for each task will reduce the memory being used
  13. *LOAD* 5 minute load average is 7.65
×
×
  • Create New...