Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 03/03/2015 in all areas

  1. Today I'm really excited to announce our new blog; https://blog.cachethq.io As extra news, we've moved the demo instance of Cachet to https://demo.cachethq.io so that we can use https://status.cachethq.io ourselves
    1 point
  2. Tyson

    Cc In Ticket

    Who are you looking to CC/BCC in a ticket? Would you CC/BCC a particular ticket reply, or CC/BCC them for all ticket replies? Would they be included for informational purposes, or would they have the option of responding to the ticket via email (this would be more complicated)? The system already includes client contacts in CC automatically if they are involved in opening/replying to the ticket.
    1 point
  3. Chances are the {password_reset_url} tag in the "Password Reset" email template (found under [settings] -> -> -> (edit Password Reset)) is including a malformed or incorrect URL. It might be that your company hostname is incorrect. You can find and update the hostname under [settings] -> [system] -> [Companies] -> (edit). You could try to have a password reset email sent to you for your staff account to check if the link in that email is incorrect as well. It would be best to see what the URL of the link in the email is to determine the problem.
    1 point
  4. We can do it with the email address - would be great if we could also do it with the from name.
    1 point
  5. Michael

    Ticket Subject & Reference

    It should happen to new tickets customer side only. If you are doing the staff side you could do with: Licensecart {ticket.department_name} - Update to Ticket {ticket.code} - Priority: {ticket.priority}
    1 point
  6. Michael

    Ticket Subject & Reference

    The hash is a reference to the ticket, and the Ticket# number is the ticket number. I have: Licensecart {ticket.department_name} - Opened ticket #{ticket.code} [{ticket_hash_code}] And: Licensecart {ticket.department_name} - #{ticket.code} has been updated. [{ticket_hash_code}] Eg: Licensecart Sales Enquires - #123456 has been updated [-ab43-]
    1 point
  7. Paul

    Delete Tickets

    Ok, pretty straight forward. So, what if we allow any staff assigned to the department to send a ticket to the trash bin, and then made a setting available to each staff so they can access and empty the trash bin? (This would probably apply to any/all tickets in the trash that belonged to departments for which they had access.) What does everyone think?
    1 point
  8. Jonathan

    Delete Tickets

    Kayako has a Trash Bin which is where when you click "delete" a ticket goes. From here within this folder there's an "empty trash" button. The ability to do these two things are controll be separate permissions assignable to staff/groups. This would be a pretty cool implementation for Blesta. I've attached a couple of screenshots.
    1 point
  9. Alk

    Change Paypal Buttons

    Would a moderator be able to move this topic to the feature requests forum please? I've been playing around with the buttons again, now that the order form page has been updated in 3.2. So now I'm using the following buttons: https://www.paypalobjects.com/webstatic/en_US/btn/btn_paynow_cc_144x47.png https://www.paypalobjects.com/webstatic/en_US/btn/btn_subscribe_cc_147x47.png Which results in the order form looking like: For comparison, it originally looked like: But what (in my opinion) previously looked so unprofessional was the pay invoice page: Now it looks like: (all the buttons match and line up) All I did was change the URLs to the images in /components/gateways/nonmerchant/paypal_payments_standard/views/default/process.pdt. Would Blesta consider making these buttons standard please, as my alternative PayPal buttons are neater and more helpful to users?
    1 point
×
×
  • Create New...