ClientlistAnywhere :: Free Ajax-Powered Smarty Clientlist Plugin

[rmccny]

This new add-on that I put together in the past hour allows you to add an ajax-powered client drop-down box to just about any WHMCS admin template. This simple plug-in requires no installation, no configuration, no license, and only a simple template edit to use. Installation and usage instructions included. This works even if you have the client drop-down turned off in admin.

 

Full source code included!

 

 

Example Usage:

 

{clientlist id="userid" clientid=$userid width="250px"}

Here's how easy it is to add a client drop-down to the support ticket view:

Open template admin/tempalates/v4/viewticket.tpl

   LOOK FOR

   <input type="text" name="userid" size="10" value="{$userid}" />


   REPLACE WITH

   {clientlist id="userid" clientid=$userid}


Close and save

Download (no registration required)

[BAJI26]

Do you have an example?

[rmccny]

I have included an example of how to use the plugin above. Those instructions will integrate the client drop-down into the support ticket options tab as the screenshot below shows. (I'm the client shown)

 

[j4m3s]

Very useful, thanks!

I found an error. When the customer's name have an accent, appears only as a letter before the accent. Example: Comércio, appears Com and the rest of the name disappears.

[rmccny]

Thanks for the bug report. I forgot about our international friends; the output has to first be converted to UTF8 before being passed to json_encode.

 

Here's the fix:

 

Find:

 

    $client_array[$client['id']] = $client['label'];

Replace With:

 

    $client_array[$client['id']] = utf8_encode($client['label']);

I have packaged the fix in the download; v1.0.2.

 

Thanks!

[j4m3s]

thanks mate !

[rmccny]

Unfortunately that broke the plugin for others. Arrgh! If WHMCS would standardize and require UTF8 encoding life would be much easier. The problem with that patch is that sites already using UTF8 wind up with double-encoding problems.

 

I've released version 1.0.3 of this plugin, if it's working fine for you there is no need to update, but if you're having character encoding problems this update is a must.

 

The patch detects the $mysql_charset setting set in WHMCS configuration.php, if it doesn't see utf8 encoding there it will encode the output, otherwise it just passes it through.

 

Sorry for the rapid succession of updates.