Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

10 Good

About luigidelgado

  • Rank
  1. 1. Well.... Those fields should be at least greyed out in those two emails, so we WHMCS Admins dont loose our head for hours or days trying to find out why our changes are not being saved.... For the sake of UX. 2. I tested that, ticket_tid wont work on the emails sent to the clients, with or without mask you must always use ticket_id. For emails sent to the Admins both of them work so if you are using a mask you must use ticket_tid if not, use ticket_id... No documentation on this, you have to find out by yourself. Again for the sake of UX there should be some documentation about it.
  2. I have tested and I found some things, please let me know if this is correct: 1. For Tickets Opened and Tickets Reply emails for client side, the structure is always [Ticket ID: {$ticket_tid}] - {$ticket_subject} so whatever I place on those two email templates subjects makes nothing at all. If this is correct, the Subject Field for those two emails should simply be grayed out or something like that and make us WHMCS Administrators understand this. Documentation does not say this either. 2. The mask thing does not work in the Support Mail Templates WHMCS sends to users. I have to use {$ticket_id} otherwise the field will show balnk on mails. This should also be explicity said somewhere in the documentation. It will only work on the Admin Email Tickets for Admins. In those emails both variables show, the {$ticket_tid} shows the masked Ticket and {$ticket_id} the real Ticket ID on database. Makes nonsense for me to use one method in the clients side and the other in the Admins side, makes it very confusing.
  3. luigidelgado

    Email Templates Variables List

    For all of you (like me) who are looking for or simply just would like to have a List of all Email Templates Variables Available when designing your email templates, my 2 cents: Client Related ID {$client_id} Client Name {$client_name} First Name {$client_first_name} Last Name {$client_last_name} Company Name {$client_company_name} Email Address {$client_email} Address 1 {$client_address1} Address 2 {$client_address2} City {$client_city} State/Region {$client_state} Postcode {$client_postcode} Country {$client_country} Phone Number {$client_phonenumber} Password {$client_password} Signup Date {$client_signup_date} Credit Balance {$client_credit} Card Type {$client_cc_type} Card Last 4 {$client_cc_number} Expiry Date {$client_cc_expiry} Remote Gateway Token {$client_gateway_id} Client Group ID {$client_group_id} Client Group Name {$client_group_name} Total Due Invoices Balance {$client_due_invoices_balance} Custom Fields (Array) {$client_custom_fields.1} Status {$client_status} Product/Service Related Order ID {$service_order_id} ID {$service_id} Signup Date {$service_reg_date} Product Name {$service_product_name} Product Description {$service_product_description} Domain {$service_domain} Config. Options {$service_config_options} Server Name {$service_server_name} Server Hostname {$service_server_hostname} Server IP {$service_server_ip} Dedicated IP {$service_dedicated_ip} Assigned IPs {$service_assigned_ips} Nameserver 1 {$service_ns1} Nameserver 2 {$service_ns2} Nameserver 3 {$service_ns3} Nameserver 4 {$service_ns4} Nameserver 1 IP {$service_ns1_ip} Nameserver 2 IP {$service_ns2_ip} Nameserver 3 IP {$service_ns3_ip} Nameserver 4 IP {$service_ns4_ip} Payment Method {$service_payment_method} First Payment Amount {$service_first_payment_amount} Recurring Payment {$service_recurring_amount} Billing Cycle {$service_billing_cycle} Next Due Date {$service_next_due_date} Status {$service_status} Suspend Reason {$service_suspension_reason} Cancellation Type {$service_cancellation_type} Username {$service_username} Password {$service_password} Custom Fields (Array) {$service_custom_fields.1} Domain Related Order ID {$domain_order_id} Signup Date {$domain_reg_date} Domain {$domain_name} SLD (yourdomain) {$domain_sld} TLD (com) {$domain_tld} Reg Period {$domain_reg_period} First Payment Amount {$domain_first_payment_amount} Recurring Amount {$domain_recurring_amount} Next Due Date {$domain_next_due_date} Expiry Date {$domain_expiry_date} Registrar {$domain_registrar} 'Days Until Expiry' and 'Days Until Next Due' will show 0 if the date has passed. 'Days After Expiry' and 'Days After Next Due' should be used if the date has passed. Days Until Expiry {$domain_days_until_expiry} Days Until Next Due {$domain_days_until_nextdue} 'Days After Expiry' and 'Days After Next Due' will only be defined if the date has passed. Days After Expiry {$domain_days_after_expiry} Days After Next Due {$domain_days_after_nextdue} Status {$domain_status} DNS Management {$domain_dns_management} Email Forwarding {$domain_email_forwarding} ID Protection {$domain_id_protection} Auto Renew Disabled {$domain_do_not_renew} Support Ticket Related ID {$ticket_id} Department {$ticket_department} Date Opened {$ticket_date_opened} Subject {$ticket_subject} Message {$ticket_message} Status {$ticket_status} Priority {$ticket_priority} Ticket URL {$ticket_url} Ticket Link {$ticket_link} Auto Close Time {$ticket_auto_close_time} Knowledgebase Auto Suggestions {$ticket_kb_auto_suggestions} Invoice Related Invoice ID {$invoice_id} Invoice # {$invoice_num} Date Created {$invoice_date_created} Due Date {$invoice_date_due} Date Paid {$invoice_date_paid} Invoice Items (Array) {$invoice_items} Invoice Items HTML {$invoice_html_contents} Sub Total {$invoice_subtotal} Tax {$invoice_tax} Tax Rate {$invoice_tax_rate} Credit {$invoice_credit} Total {$invoice_total} Amount Paid {$invoice_amount_paid} Balance {$invoice_balance} Last Payment Amount {$invoice_last_payment_amount} Last Payment Trans ID {$invoice_last_payment_transid} Payment Method {$invoice_payment_method} Payment Link {$invoice_payment_link} Subscription ID {$invoice_subscription_id} Status {$invoice_status} Invoice Link {$invoice_link} Previous Balance {$invoice_previous_balance} Total Due Invoices Balance {$invoice_total_balance_due} Notes {$invoice_notes} Other Company Name {$company_name} Domain {$company_domain} Logo URL {$company_logo_url} WHMCS URL {$whmcs_url} WHMCS Link {$whmcs_link} WHMCS Admin URL {$whmcs_admin_url} WHMCS Admin Link {$whmcs_admin_link} Marketing Unsubscribe URL {$unsubscribe_url} Signature {$signature} Full Sending Date {$date} Full Sending Time {$time} Conditional Display You can use conditionals to display text based on other values - for example: {if $ticket_department eq "Sales"} Sales only operates Monday-Friday 9am-5pm {else} Your ticket has been received and will be answered shortly {/if} Looping through data A foreach loop can be used to cycle through values like invoice items: {foreach from=$array_data item=data} {$data.option}: {$data.value} {/foreach}
  4. Hello. Does anybody know about an addon/plugin/etc where I can preload certain amount of hours each month to my clients every month and keep track of the time used? and resets every month.
  5. And by the way. The plugin is expensive conpared to all other plguins in service. 120 USD is too much.
  6. Hi.Im interested. But there's a feature I dont see... What if I charge in advance to my clients? This is very common as some clients will never pay once you have give them the support so... We charge for a package of support hours in advance. Is there a way to manage this? a Preapid fromat? where I can remove hours/credits from their account? That would really solve this issue to me thank you.
  7. luigidelgado

    Invalid Token Error

    Any Ideas? Im having the same issue now...
  8. luigidelgado

    any addons can do this

    May be simplier than what you think... Obviously WHMCS should think in somving this easyly with a variable in the meta "refres"... its pretty easy... in viewticket.tpl add: <meta http-equiv="refresh" content="REFRESH TIME HERE" >
  9. luigidelgado

    EPP Registry Registrar Module

    Hi Benoit, Im interested in the .MX NIc module. Can you help me give more details? How does it integrate to NIC.MX? Thanks!
  10. luigidelgado

    Integrar WHMCS con NIC Mexico como un Registry

    Yo les recomendaría checar con NIC.mx la factibilidad nuevamente antes de hacer el modulo... Por lo menos a lo que a mi respecta me mandaron por un tubo olimpicamente, poniendome "N" cantidad de papeleo y tramites y requisitos para ser Registrar autorizado y poder integrarme con ellos. Enom tiene integración al 100% con WHMCS el modulo y todo lo que necesiten, sin costos adicionales, tienen dominios de todos lados y el precio es ligeramente más elevado que con NIC para los TLD's mexicanos. Chequenlo, enom.com el Registry No. 1 en USA (despues de GoDaddy) asi que no van a tener problemas con ellos, tambien te integran de pasada SSL's y otros productos y te dan precio de distribuidor por estar en WHMCS. PEro bueno si alguien tiene la SUERTE y POSIBILIDAD de encontrar una solución despues de dos años del primer post de este hilo... compartanlo por favor, gracias!
  11. luigidelgado

    Admin Spanish Translation

    Les porporciono la traducción al 95% del WHMCS Administrador 4.5.2. si alguien lo quiere terminar y repostear se va a agradecer, saludos. spanish.zip
  12. luigidelgado

    Integrar WHMCS con NIC Mexico como un Registry

    Hay alguna novedad con lo expuesto en este post?

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated