Jump to content

John

Moderators
  • Posts

    217
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by John

  1. There's 2 or 3 that actually need to get done for beta. We're working on it, will be done soon. Updating minPHP and a couple other tasks were really involved, and required some refactoring and creation of new libraries. So, taking longer than expected, but almost there :)

    Oh, cool!

     

    One other question: I remember you saying somewhere that you are going to raise the minimum PHP requirements, but will you be supporting 5.6 or 7.0? Not sure what you are supporting right now, but I am guessing only up to 5.5?

     

    Thank you

  2. The goal is v4 beta this month, but we still have some work ahead of us. No official ETA, but also not a good idea to use beta 1 in production. Running a report and using another mailer is the best way to go for now. Maybe Cody or Tyson can chime in with the proper query you can use.

    Hi Paul,

     

    Just wondering what the current status is on 4.0. It currently shows you have 12 tasks left (probably excluding hidden).

     

    Just so I can plan ahead, when can we expect a beta now?

     

    Thank you!  :blesta:

  3. Hello All,

     

    This is a feature request I hope no one will have to use.

     

    When a database gets breached, or there is a flaw in the security of Blesta, we might need to require all clients to change their passwords (and two factor auth tokens). Currently, there is no way to do this.

     

    Most sites just make you login, and then you can change your password. While this is very convenient for users, it is also extremely convenient for the person who managed to dump the database. Therefore, I recommend that after the user logs in, they get sent an email with a PIN number, which they have to put in to the webpage. Then, it will allow them to reset their password. If they do not enter the PIN, then staff would get an alert, because this could mean that the clients account is breached.

     

    While the Blesta team is very good at securing their product, this important feature is missing. I view it as a must-have. Right now, if a database were to get dumped we would have to manually reset clients passwords. (VERY time consuming)

     

    John

  4. You would need to update the staff member's configured setting for receiving order emails in order to disable it. This is only possible when logged in as that particular staff member and going to the Orders widget. Alternatively, you could update the database to remove them from the list in the interim: under the `order_staff_settings` table, you can find records for that staff member by his staff ID, then update the `value` column to "never" for the `key`s "email_notice" and "mobile_notice".

     

    This issue will be resolved in CORE-1905.

    Thank you. Glad to see that it is in your system.

  5.  

    yeah I use the priority tags for staff emails:

    Licensecart {ticket.department_name} - Update to Ticket {ticket.code} - Priority: {ticket.priority}
    

    That is a different priority than we are talking about. That is the ticket priority, and we are talking about the email priority. Check my reply above to see what I am talking about.

     

    There are basically three types of priorities: low, normal, high. I think an option to select any of the three would be best. However, the X-Priority email header that would be sent to indicate this priority can be interpreted to be spam by some spam services.

    Did not think of that. I do like the low/normal/high selection. I have never heard of SPAM filters not liking this.

     

    At this point it is nothing more than a thought, I just brought it up because it would be a good way to send suspension emails, etc. What about integrating it with the ticket system? That way, if a ticket gets sent out as "Emergency", it will get marked as high priority for emails that get sent out through it?

  6. The order system can be configured to send out emails to staff when a new order is received. The issue we are having is that when a staff account is disabled, the emails are still getting sent out to the disabled staff member.

     

    Is there a way to set it up so that when a staff account is disabled, or no longer has access to view the order system, the emails automatically switch off?

  7. Not sure people have complained to me and it's the same as you could just copy and paste.

    But it also helps with traffic from Google and I've had Site5 link to articles.

    I understand that people may have not complained, but it's not what we (as a company) want to be sending to customers. Additionally, we have to open tickets for things like abuse, and linking to the KB is definitely not desired in these situations. I'm sure you understand that we don't want every single one of our canned responses on our KB. It is a valuable tool, but it is not made for that.

     

    I am just asking that the system work how it was supposed to from the beginning. I understand this was an oversight, but let's see what we can do to fix the underlying cause, and not just have a temporary work-around.

     

    I'm not sure I understand how linking to something in an email (ticket) helps with rankings on search engines.

  8. Hello,

     

    I think that a great feature would be the option to specify the email priority for template emails. A service suspension/credit card expiring/payment declined email is high priority, so there maybe should be a check box, saying "Send as high priority" This would mark the email in the clients inbox as having a high priority.

     

    What is everyone's thoughts about this feature request?

  9. I believe the signature is set in the ticket reply by default. A predefined response would be appended to the ticket reply making it appear at the end. I think this behavior is normal for most cases, but may be inconvenient if you are using a signature, and would require you to move the text to a more appropriate place.

     

    When you click to add a predefined response, it can be added either at the beginning or end of the reply text, and we opted for the end. Without more information (such as adding a second step), we couldn't choose a particular place in the reply text to insert the predefined response.

    Maybe there could be an option in the settings for this? That way, the administrator could choose either the beginning or the end. If you force it to be one way, then only half of the people are happy.

     

    Is there a way to modify this temporarily, so that we can get this to work right for us?

     

    We spoke about this before and the Support Manager Pro does it at the top now.

    I personally moved all our responses to articles in the KB and just link to it.

    While linking to the knowledgebase may be a good temporary fix, it really takes out the human contact.

  10. Hello,

     

    We are trying to set up predefined responses, and we have noticed a bug when we try and use it with a predefined signature.

     

    What happens is the system puts the agents signature before the predefined response, so the end result looks something like this:

     

     

    Thanks,

    John Smith

    FunCorp, IncHello,

    I have made the change requested. Please allow up to 24 hours for the system to process the new addition.

    If you have anything else you need help with, please let us know!

     

    Can anyone else confirm this?

  11. With 3.6, I understand that only transactions counted as 'income' are calculated for the Billing at a Glance plugin. My concern is that for us, we have to manually enter in PayPal payments. This means going under Record Payment, and choosing "Other -> PayPal Payments Standard". It looks like this is not being counted as income.

     

    Can anyone else confirm this?

  12. Hello!

     

    We support both IPv4 and IPv6 on our services. Each client is assigned one /64 of IPv6, and one IPv4 address by default.

     

    The issue comes into play when a client wants an additional IPv4 address. We add it through the configurable options, and everything goes well, until it is provisioned.

     

    Instead of provisioning a new IPv4 address, Blesta counts the IPv6 space! This results in the client getting one less IPv4 address than what they paid for. (See the screenshot as an example)

     

    Anyone else having this issue?

    post-37-0-99349800-1440423569_thumb.png

×
×
  • Create New...