Kiler Media Development Group

We have a new logo! Yep, the very first official Kiler Media business logo.

What do you think about our new business logo?? Let us know! Leave comments!!

If you’re looking for pre-made website templates to use with your new or old website or web project look no further than to the image on the left, Boxed Art! With well over $2,000,000 worth of website and design templates and content, it just doesn’t get any better than BoxedArt.com!

[Official Release:]

Our first of several new adult comics-related websites has been fully released to the public. Lewd Comics is a general adult comics/cartoon blog-type website developed by us here at Kiler Media. You may have noticed it added to our links section a few weeks ago, but now we are officially opening it up for everyone!

We hope you all enjoy our projects and as always, if you have any questions, comments or concerns please feel free to contact us.

If you would like to try the famous ID® Lube™ I found a way to get a FREE SAMPLE of ID® Glide™ Personal Lubricant! All you have to do is fill out their simple survey that will take you approximately 15 seconds to complete!!

HERE IT IS! A FREE SAMPLE OF ID GLIDE PERSONAL LUBRICANT!!!

So, you’re looking for the “almost” perfect startup tutorial for the uber-famous Smarty template engine written with PHP? Or, are you just looking for a good straight-up to the point tutorial on using Smarty? Well, either way HERE IT IS!!

For the basic setup check out this tutorial here. Once you have Smarty running on your server then take a seat and follow me.

Your folder/directory structure should be like the following:

/root/
Example: /var/www/vhosts/yoursite.com/httpdocs/
/root/cache/ - Chmod 775
Example: /var/www/vhosts/yoursite.com/httpdocs/cache/
/root/configs/
Example: /var/www/vhosts/yoursite.com/httpdocs/configs/
/root/templates/
Example: /var/www/vhosts/yoursite.com/httpdocs/templates/
/root/templates/themeName/ - Your Theme’s Folder
Example: /var/www/vhosts/yoursite.com/httpdocs/templates/themeName/
/root/templates/themeName/index.tpl - Your Main Theme File
Example: /var/www/vhosts/yoursite.com/httpdocs/templates/themeName/index.tpl
/root/templates_c/ - Chmod 775
Example: /var/www/vhosts/yoursite.com/httpdocs/templates_c/
/root/smarty/
Example: /var/www/vhosts/yoursite.com/httpdocs/smarty/
/root/smarty/internals/
Example: /var/www/vhosts/yoursite.com/httpdocs/smarty/internals/
/root/smarty/plugins/
Example: /var/www/vhosts/yoursite.com/httpdocs/smarty/plugins/
/root/smarty/Config_File.class.php
Example: /var/www/vhosts/yoursite.com/httpdocs/smarty/Config_File.class.php
/root/smarty/debug.tpl
Example: /var/www/vhosts/yoursite.com/httpdocs/smarty/debug.tpl
/root/smarty/Smarty.class.php
Example: /var/www/vhosts/yoursite.com/httpdocs/smarty/Smarty.class.php
/root/smarty/Smarty_Compiler.class.php
Example: /var/www/vhosts/yoursite.com/httpdocs/smarty/Smarty_Compiler.class.php

For secure template placement:

Example:
/var/www/vhosts/yoursite.com/httpdocs/ = The web root.
/var/www/vhosts/yoursite.com/templates/
/var/www/vhosts/yoursite.com/templates_c/

To protect your templates from being viewed as-is I like to utilize a pre-existing security script, with an .htaccess file. Inside the folder/directory of your template file you make an .htaccess file with the following contents:

<Files ~ “\.tpl$”>
Order allow,deny
Deny from all
</Files>

For the example above, you would place an .htaccess file with the above contents inside the folder: /root/templates/themeName/

/root/templates/themeName/.htaccess

Now, to setup the PHP code which displays the page I’ll demonstrate a simple example:
The PHP code: index.php

<?php
// Smarty initializers and code (start)
define(’SMARTY_DIR’, ‘/var/www/vhosts/yoursite.com/httpdocs/smarty/’);
// or if you’re on a shared: /home/accountName/public_html/smarty/
require_once(SMARTY_DIR . ‘Smarty.class.php’);// or die(’Could not load Smarty class.’);
class Kiler_Smarty extends Smarty { // PHP4-5 compatible;
function Kiler_Smarty(){
// Class Constructor.
// These automatically get set with each new instance.
$this->Smarty();
$this->template_dir = ‘/var/www/vhosts/yoursite.com/httpdocs/templates/’;
// or if you’re on a shared: /home/accountName/public_html/templates/
$this->compile_dir = ‘/var/www/vhosts/yoursite.com/httpdocs/templates_c/’;
// or if you’re on shared: /home/accountName/public_html/templates_c/
$this->config_dir = ‘/var/www/vhosts/yoursite.com/httpdocs/configs/’;
// or if you’re on shared: /home/accountName/public_html/configs/
$this->cache_dir = ‘/var/www/vhosts/yoursite.com/httpdocs/cache/’;
// or if you’re on shared: /home/accountName/public_html/cache/
// you can also do like:
$this->assign(’app_name’, ‘Your Website System Name; beta build 110107′);
}
}
$smarty = new Kiler_Smarty();
$smarty->display(’themeName/index.tpl);
?>

Inside the main theme file [/templates/themeName/index.tpl] It could look like this:

<html><head><title>My Website</title></head><body>Hello from Smarty version: {$smarty.version}! This is {$app_name}!</body></html>

Although, it is advisable to place your template files outside of the web root on non-development servers if the server is under constant exposure.

You would need to move the templates folder and the templates_c folder outside of the web root, like so:

/var/www/vhosts/yoursite.com/templates/
// or if you’re on shared: /home/accountName/templates/
/var/www/vhosts/yoursite.com/templates_c/
// or if you’re on shared: /home/accountName/templates_c/

Then be sure to change the PHP code lines reading:

$this->template_dir = ‘/var/www/vhosts/yoursite.com/httpdocs/templates/’;
// or if you’re on a shared: /home/accountName/public_html/templates/
$this->compile_dir = ‘/var/www/vhosts/yoursite.com/httpdocs/templates_c/’;
// or if you’re on shared: /home/accountName/public_html/templates_c/

Change It To:

$this->template_dir = ‘/var/www/vhosts/yoursite.com/templates/’;
// or if you’re on a shared: /home/accountName/templates/
$this->compile_dir = ‘/var/www/vhosts/yoursite.com/templates_c/’;
// or if you’re on shared: /home/accountName/templates_c/

Of course, you’ll also have to handle the file permissions as well.

Do this process of setting up Smarty and the template folder/file structure over and over again until you can memorize the process then the rest of using Smarty will be a breeze! We will be posting more Smarty tutorials in the very near future, so stay tuned!

We have finally realized the true potential of adult comics and cartoons here at Kiler Media and have recently acquired a few adult comic related domains! We are very excited about the potential of these new domains and will post here when we have fully launched them!

To tell you the truth, my girlfriend is really in to reading adult related comics online and I thought it would be a good idea to feed her “fetish”, and at the same time she/we can make some extra income from it! Stay tuned for the launch!

I tend to be tedious when it comes to how I layout my folder/file structures with large web projects. Here’s the just of it:

Basic Folder/Directory Structure:

/root/
-/img/
-/includes/
-/templates/

• /root/ - This is the root folder/directory. You can also call this “public_html” or “httpdocs”. This is the web root for the web site.
• /root/img/ - This folder/directory is obviously used to hold all of the images and graphic files.
• /root/includes/ - This folder/directory is used to hold all of the code library files, style sheets, and any other files which are commonly used throughout the system.
• /root/templates/ - This folder/directory is used to hold template files, if the system uses a templating engine.

I have based my folder structuring techniques out of my many years of experience with producing web sites and systems. If you have any experience with actually editing pre-existing web site systems then this folder structure should be familiar to you.

In my next article I will go over the basis of the way I like to structure my files within the folder structure.

I have some news about our upcoming TGP/CMS system titled Kiler A-TGP/CMS. We have been looking into using template engines with the system for quite some time now and have finally decided on which to use. At first, we wanted to use our own template system but then have decided otherwise. We have finalized on using the world famous Smarty template engine!

I know a few of you are going to be really excited about this. More news to come.

In the past I’ve gotten quite a bit of heat from my colleagues for utilizing cookies over sessions with PHP, and I’ve finally had enough! I will now go ahead and explain the reasons why I use cookies over sessions for everything.

Cookies have been around since day one with dynamic scripting languages. They were the first tracking mechanism ever utilized on the internet and will be the last. Here’s a definition straight from Wiki:

HTTP cookies, sometimes known as web cookies or just cookies, are parcels of text sent by a server to a web browser and then sent back unchanged by the browser each time it accesses that server. HTTP cookies are used for authenticating, tracking, and maintaining specific information about users, such as site preferences and the contents of their electronic shopping carts. The term “cookie” is derived from “magic cookie,” a well-known concept in unix computing which inspired both the idea and the name of HTTP cookies.
Cookies have been of concern for Internet privacy, since they can be used for tracking browsing behavior. As a result, they have been subject to legislation in various countries such as the United States and in the European Union. Cookies have also been criticised because the identification of users they provide is not always accurate and because they could potentially be used for network attacks. Some alternatives to cookies exist, but each has its own drawbacks.
Cookies are also subject to a number of misconceptions, mostly based on the erroneous notion that they are computer programs. In fact, cookies are simple pieces of data unable to perform any operation by themselves. In particular, they are neither spyware nor viruses, despite the detection of cookies from certain sites by many anti-spyware products.
Most modern browsers allow users to decide whether to accept cookies, but rejection makes some websites unusable. For example, shopping baskets implemented using cookies do not work if cookies are rejected.

While sessions can make the tasks of the programmer easier they open up a lot of nasty holes which you need to immediately close and fix. The two most notable vulnerabilities to sessions are the following:

Session Fixation: These are attacks which attempt to exploit the vulnerability of a system which allows one person to fixate (set) another person’s session identifier (SID). This attack is greatly enhanced when the SID is attached to the query string. (Which usually is the case.)

Session Poisoning: These attacks exploit insufficient input validation in server applications which copies user input into session variables. The underlying vulnerability is a state management problem; shared state, race condition, ambiguity in use or plain unprotected modifications of state values. Session poisoning has been demonstrated in server environments where different non-malicious applications (scripts) share the same session states but where usage differ, causing ambiguity and race conditions. Session poisoning have also been demonstrated in scenarios where the attacker is able to introduce malicious scripts into the server environment, which is possible if attacker and victim shares a web hotel.

Before I start explaining myself you should also know that there are several vulnerabilities to cookies if used inproperly, as well. The following list is the main vulnerabilities with using cookies inproperly:

Cookie Theft: Cookies theft is any process allowing an unauthorised party to receive a cookie.

Cookie Poisoning: The process of tampering with the value of cookies is called cookie poisoning, and is sometimes used after cookie theft to make an attack persistent.

Both of the above mentioned cookie vulnerabilities are easily patched up with a bit of brain and leg work.

Firstly, use a “session identifier” as the cookie, instead of, say, the user’s ID or name. Save the session id in a database on the server as well as in the cookie on the clients computer. Set a crontab to delete the session id from the database after a certain time length to ensure limited tampering time.
Secondly, use encryption (SSL if possible) on and when you set the cookie in the database and clients computer.
These two methods of securement make it quite impossible to exploit.

To patch up and fix the vulnerabilities with sessions is impossible. Here are the reasons why:

1. (and only #1): Regeneration Of The SID On Each Request is pretty much the only way to fend off the attacks on sessions, and is quite impossible to use contently. Known cases where session regeneration may cause problems include when third party software such as ActiveX, Java Applets, or browser plugins communicate with the server as well. Third party software could cause logouts, or the session could be split into two separate sessions. In this day and age the websites which have user systems which need to utilize some form of tracking, be it a cookie or session, almost always uses third-party software, such as Flash, Java applets, or browser plugins, mentioned above.

So, the developer is left with the decision of either being able to use third-party software securely with cookies or only their own software with sessions securely. Which would you choose?

In what will be a new tutorial series here at KilerMedia.com, we are going to teach you PHP!
In this first tutorial we ask the question, “What Is PHP?”

PHP is a reflective programming language originally designed for producing dynamic web pages. PHP is used mainly in server-side scripting, but can be used from a command line interface or in standalone graphical applications. Textual User Interfaces can also be created using ncurses. PHP is a recursive initialism for PHP: Hypertext Preprocessor.
The main implementation is produced by The PHP Group and released under the PHP License. This implementation serves to define a de facto standard for PHP, as there is no formal specification. The most recent version of PHP is 5.2.4, released on 30 August 2007. It is considered to be free software by the Free Software Foundation.

HISTORY:
PHP was written as a set of Common Gateway Interface (CGI) binaries in the C programming language by the Danish/Greenlandic programmer Rasmus Lerdorf in 1994, to replace a small set of Perl scripts he had been using to maintain his personal homepage. Lerdorf initially created PHP to display his résumé and to collect certain data, such as how much traffic his page was receiving. Personal Home Page Tools was publicly released on 8 June 1995 after Lerdorf combined it with his own Form Interpreter to create PHP/FI (this release is considered PHP version 2).
Zeev Suraski and Andi Gutmans, two Israeli developers at the Technion IIT, rewrote the parser in 1997 and formed the base of PHP 3, changing the language’s name to the recursive initialism PHP: Hypertext Preprocessor. The development team officially released PHP/FI 2 in November 1997 after months of beta testing. Public testing of PHP 3 began and the official launch came in June 1998. Suraski and Gutmans then started a new rewrite of PHP’s core, producing the Zend Engine in 1999. They also founded Zend Technologies in Ramat Gan, Israel, which actively manages the development of PHP.

USAGE:
PHP is a widely-used general-purpose scripting language that is especially suited for Web development and can be embedded into HTML. PHP generally runs on a web server, taking PHP code as its input and creating Web pages as output. However, it can also be used for command-line scripting and client-side GUI applications. PHP can be deployed on most web servers and on almost every operating system and platform free of charge. The PHP Group also provides the complete source code for users to build, customize and extend for their own use.
PHP primarily acts as a filter. The PHP program takes input from a file or stream containing text and special PHP instructions and outputs another stream of data for display.
Originally designed to create dynamic web pages, PHP’s principal focus is server-side scripting. While running the PHP parser with a web server and web browser, the PHP model can be compared to other server-side scripting languages such as Microsoft’s ASP.NET system, Sun Microsystems’ JavaServer Pages, mod_perl and the Ruby on Rails framework, as they all provide dynamic content to the client from a web server. To more directly compete with the “framework” approach taken by these systems, Zend is working on the Zend Framework - an emerging (as of June 2006) set of PHP building blocks and best practices; other PHP frameworks along the same lines include CakePHP, PRADO and Symfony.
The LAMP architecture has become popular in the Web industry as a way of deploying inexpensive, reliable, scalable, secure web applications. PHP is commonly used as the P in this bundle alongside Linux, Apache and MySQL, although the P can also refer to Python or Perl. PHP can be used with a large number of relational database management systems, runs on all of the most popular web servers and is available for many different operating systems. This flexibility means that PHP has a wide installation base across the Internet; over 19 million Internet domains are currently hosted on servers with PHP installed.

Examples of popular server-side PHP applications include phpBB, WordPress, MediaWiki, vBulletin, NATS, and MPA³.
Examples of popular PHP websites include FaceBook.com, LunarPages.com.

REQUIREMENTS:
Before you get knee deep in these tutorials you should ensure that you have the minimum requirements:

• 1. A web server (preferably Apache),
• 2. PHP installed on the server,
• 3. Ability to add/edit/delete php files on your server.

Ready to get into some code? You’ll have to wait for the next tutorial!