Open Script Solution» content

How to Avoid Duplicate Ticket Content Saved in HESK v2.1

Masino Sinaga — Wed, 16 Dec 2009 16:51:12 +0000

Actually, this modification I created was being intended for a friend of mine who implemented HESK for his department. I was interested with its interface, so I tried to create a new ticket and tested after submitting the ticket, I reload the “thank-you” page. In fact, a new ticket then would be created, the same condition that occured in osTicket, which I have created the modification regarding it to fix the same problem.

Open your submit_ticket.php file, and find this code:

192	hesk_dbConnect();

then after that line, please insert this following code:

/* MOD: Avoid duplicate ticket (identified by its Subject & Message) */
/* modified by Masino Sinaga, November 30, 2009 */
$sqlcek = "SELECT `subject`,`message` FROM `".hesk_dbEscape($hesk_settings['db_pfix'])."tickets` 
        WHERE `subject`='".hesk_dbEscape($subject)."' AND `message`='".hesk_dbEscape($message)."'";
$rescek = hesk_dbQuery($sqlcek);
if (hesk_dbNumRows($rescek) > 0) {
    //header('Location: index.php?a=add');
    header('Location: sorry.php');
    echo "This ticket content already exists in database!";
    exit();	
}
/* MOD: Avoid duplicate ticket (identified by its Subject & Message) */

Create a new php file, and name it with sorry.php, copy and paste this code below, and put this file to your HESK’s root directory:


 
/* Created by Masino Sinaga, http://www.openscriptsolution.com, November 30, 2009 */
 
define('IN_SCRIPT',1);
define('HESK_PATH','');
 
/* Get all the required files and functions */
require(HESK_PATH . 'hesk_settings.inc.php');
require(HESK_PATH . 'inc/common.inc.php');
 
/* Print header */
require_once(HESK_PATH . 'inc/header.inc.php');
?>
 



 hesk_showTopBar($hesklang['invalid_action']); ?>



 


 echo $hesk_settings['site_url']; ?>" class="smaller"> echo $hesk_settings['site_title']; ?> >
 echo $hesk_settings['hesk_url']; ?>" class="smaller"> echo $hesk_settings['hesk_title']; ?>
>  echo $hesklang['invalid_action']; ?>

echo "Sorry, the ticket you have just sent already exists in our database."; ?>

echo $hesk_settings['hesk_url']; ?>"> echo $hesk_settings['hesk_title']; ?>

require_once(HESK_PATH . 'inc/footer.inc.php'); exit();

How to Know The Duplicate Records Based on The Same Value in a Field in MySQL Database

Masino Sinaga — Sat, 28 Nov 2009 08:10:38 +0000

Have you ever wanted to know which record has duplicate content based on the same content in a field in MySQL database? This information will be get after you select the records and display them which one have the same content by groupping them by that field. Well, here is the script how you can do that.

Suppose we have a table named mytable which has these following records inside:

+----+-------+
| id | name  |
+----+-------+
|  1 | One   |
|  2 | One   |
|  3 | Two   |
|  4 | Two   |
|  5 | Two   |
|  6 | Three |
|  7 | Three |
|  8 | Three |
|  9 | Three |
| 10 | Four  |
| 11 | Five  |
+----+-------+
11 rows in set (0.00 sec)

and you want to display which one has the duplicate content in the name filed become like this:

+-------+---------+
| name  | howmany |
+-------+---------+
| Three |       4 |
| Two   |       3 |
| One   |       2 |
+-------+---------+
3 rows in set (0.00 sec)

In the other words, we will display the value in name field which have more than one records, whereas, the records which do not the duplicate content, will be avoided (in this case the record which have the value in field name-nya: Four and Five).

Well, here is the SQL script to do make it came true:

SELECT name, COUNT(name) AS howmany 
FROM `my_table`
GROUP BY name 
HAVING howmany > 1
ORDER BY howmany DESC;

How to Avoid Duplicate Ticket Content in osTicket System

Masino Sinaga — Thu, 03 Sep 2009 14:23:58 +0000

In osTicket System, when a new ticket created, it executes INSERT INTO SQL, and then displaying the “Thank You” page afterwards. Unfortunately, when client reload or refresh that page, then it will re-execute that SQL again, since the primary key for the ticket table is an ID of the ticket which has the auto-number field. That is why the duplicate ticket content could be saved many times to the database, and it will look like a spam ticket for you. So here is the solution to avoid duplicate ticket content saved in database in osTicket System. You can apply this code for 1.6 RC4, 1.6 RC5, or 1.6 ST version.

First of all, open the \include\class.ticket.php file, and find this following code if your osTicket version is 1.6 RC4:

  //Any error above is fatal.
  if($errors) { return 0; }

or find this code if your osTicket version is 1.6 RC5 or 1.6 ST:

$ipaddress=$var['ip']?$var['ip']:$_SERVER['REMOTE_ADDR'];

after that code, then add the following code:

  // Added by Masino Sinaga, April 13, 2009
  // This code to avoid duplicate ticket-content saved in database
  //
  // For example: In existing condition, If user refresh/reload 
  // the page that show thank you message after client              
  // open a new ticket, the new ticket would be created
  // and that new record will be saved in database, even 
  // the new ticket has same content with the previous ticket.
  // With this MOD, system will avoid the same ticket-content
  // saved in database.
  // 
  // In other words:
  // Before: Duplicate ticket-content will be saved in database
  // After : Avoid duplicate ticket-content in database
  $sql1='SELECT email FROM '.TICKET_TABLE.' 
         WHERE email='.db_input($var['email']).'
         AND name='.db_input(Format::striptags($var['name'])).'
         AND subject='.db_input(Format::striptags($var['subject'])).'
         AND phone="'.db_input(Format::striptags($var['phone'])).'"
         AND ip_address='.db_input($ipaddress).'        
         AND source='.db_input($source).'';
 
  $sql2='SELECT ticket_id FROM '.TICKET_MESSAGE_TABLE.' 
         WHERE message='.db_input(Format::striptags($var['message'])).'';
 
  $res1=db_query($sql1);
  $res2=db_query($sql2);
 
  if( ($res1 && db_num_rows($res1)) && ($res2 && db_num_rows($res2)) ) {
      $errors['err']="Data already exists in database!";
      return 0;
  }
  // Added by Masino Sinaga, April 13, 2009

From that code above, assuming that the duplicate content ticket are checked based on the same data in
- email
- name
- subject
- phone
- ip_address
- source

You may customize those parameters based on your needs. For example, if you want to avoid the “ip_address” of your client since this IP Address could be changed each time your client refresh or reload the thank you page (dynamic IP), then you may not use this “ip_address” and remove it from that SQL above.

The .htaccess File Content When Permalink Activated

Masino Sinaga — Tue, 25 Aug 2009 03:26:53 +0000

I just wondered what would be happened when Permalink feature in WordPress is being activated? Detail technical question is: “What is the truly identifer that makes me sure this feature is being activated?” For those who do not know what Permalink is, it is a feature in WordPress that allows you to change the URL style become SEO friendly. For example, default URL is: http://www.yourdomainname.com/index.php?p=123 then when Permalink activated, that URL will become http://www.yourdomainname.com/2009/08/21/sample-post/. Well, here is the answer for this.

When you activate Permalink feature from admin panel in Settings section for the very first time, then your WordPress will create an .htaccess file located on your web root directory (assuming this file does not already exist before). This .htaccess file contains of the code as you can see below:

# BEGIN WordPress

RewriteEngine On
RewriteBase /yourdomainnamehere/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /yourdomainnamehere/index.php [L]


# END WordPress

Please note that yourdomainhere is the name of your domain.

When you deactivate this Permalink feature, then this .htaccess file would not be removed, but the main code above would be removed. It becomes like this:

# BEGIN WordPress

# END WordPress

This has been tested in WordPress version 2.8.4.

How to Make a Multi-Language Web Content Page

Masino Sinaga — Fri, 21 Aug 2009 16:32:05 +0000

Today was the first time I used WordPress for building this website. I have been looking for a CMS that support for multi-language web content page. I need that each time my visitor read an article in full-mode and they choose one of the languages, then the content of that article will be translated to the new language.

Then after serveral hours surfing through the Internet, I found a WordPress plugins that has the ability to switch/translate the content of a page to the selected language. The plugins’ name is qTranslate that you can find from here: http://wordpress.org/extend/plugins/qtranslate/ . I downloaded qTranslate version 2.4.3 that compatible with WordPress version 2.8.4 or later.

Incredible! This plugins is really useful as I have been looking for. The most important thing that I like from this plugins is: user will become easier while creating a new article, since there was new tabs as many as the language that being enabled or used. Therefore, we can switch from one to another tab to translate to the new language only from one form.

Another advantage that you get when you use this plugins is: every post for all active languages will be saved in one record. Thus, this will keep your database size smaller, than if every post for each language will be saved in separate record.

But, it has small weakness, especially if you deactivate this plugins after you have some posts that added or updated with this multi-language feature. The tag as I mentioned above will be displayed since it was located in one field. Therefore, if you want to use or currently using this qTranslate plugins, please reconsider not to deactivate it after you have posts that made with this plugins. Except if you want to spend your time to edit the field contains of that separator tag in database.

Now, I am starting to use WordPress, and had fallen in love with it since I knew and found this qTranslate plugins.