Jump to content

Red warning banner on ticket reply screen for users with suspended services


Recommended Posts

It would be great to have a big red warning on the ticket screen when we are replying to a customer who has a suspended service. Sometines customers write because their emails are not working, we do not check at first and later we find all the problems are because the customer has his site suspended.




Link to comment
Share on other sites

Hi Cristian,


it's already possible to add this option to the ticket page in the Admin Area, you just need to modify the admin/viewticket.tpl template...


there is already a line that displays the time since the last reply...


<div class="ticketlastreply">{$_ADMINLANG.support.lastreply}: {$lastreply}</div>

below that, add the following code...


{foreach key=num item=suspservice from=$relatedservices}
{if $suspservice.status eq "Suspended"}
<span style="font-size: 14px; background-color: #F2D4CE; border: 1px solid #AE432E; color: #cc0000; -moz-border-radius: 5px; -webkit-border-radius: 5px; -o-border-radius: 5px; border-radius: 5px; padding: 1px 5px 1px 5px; min-height: 40px;">
{if $suspservice.domain} - {$suspservice.domain} {/if} is currently Suspended</span>{/if}

this will add a small red warning box for each service/product that is currently suspended for that client... it should tell you the service (and domain if used)...


you may need to play with the stylesheet and message for your own needs, but it should provide you with the basis of the solution you were asking about. :idea:

Link to comment
Share on other sites

Thanks, this is perfect and exactly what i need!

We can leave the templates outside the main folders to they don't get overwritten by updates?

potentially, it could get overwritten by an update - though I would only expect one or two more versions of v5.3 before v6 goes live - v6 will almost certainly overwrite it.


In theory, you could change the name of the admin template to prevent it being overwritten, but its possibly not worth the effort for such a small modification.


I did initially think of writing it as an action hook, which would have made it work without template modification, but that could have been broken by v6 anyway, so there was little to gain... it's probably just easier to make a note of the above code, and when you do your incremental updates, check the admin template folder or changelog first to see if there are any template changes... if so, add the code to the template again.


then once v6 is publicly available, you can see if this feature is available by default - if not, the above code might still work... if it doesn't, then it can probably be easily fixed.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...

Important Information

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