Wednesday, December 22, 2010

How to import large mysql dump to database? or Fastest mysql dump importer

Hey guys, it is difficult to import large mysql dump file to database. See below for how to import mysql dump using only one file.

Step 1: Download dump file. (e.g.  demodb.sql).
Step 2: Change connection, username, password, database variable values.
Step 3: Change dump file name with proper path.
Step 4: Run this page.

Import mysql dump file code.

+++++++++++++++++++++++++++++++++++++++++++++++++++++
<?php
$host ="Your Host";                   // Change host (e.g localhost)
$dbusername ="Database username";     // Change Database Username
$dbpassword ="Database password";      // Change Database Password
$database ="Your database";        // Change Database
$dumpfile = "Your Dump file";        // Set dump file path (e.g. demodb.sql)   

mysql_connect($host,$dbusername,$dbpassword);
mysql_select_db($database);
$file = fopen($dumpfile, 'r');
print '<pre>';
print mysql_error();
$temp = '';
$count = 0;

while($line = fgets($file)) {
    if ((substr($line, 0, 2) != '--') && (substr($line, 0, 2) != '/*') && strlen($line) > 1) {
    $last = trim(substr($line, -2, 1));
    $temp .= trim(substr($line, 0, -1));
     if ($last == ';') {
         mysql_query($temp);
          $count++;
           $temp = '';
     }
  }
}
echo mysql_error();
echo "Total {$count} queries fire(s).\n";
echo "Enjoing this fastest mysql dump importer..\n";
echo '</pre>';
?>
+++++++++++++++++++++++++++++++++++++++++++++++++++++

Enjoying this fastest mysql dump importer.

Thursday, July 15, 2010

Create dynamic subdomain using Mod rewrite


This article is for dynamic subdomain using mod rewrite. How can you create dynamic subdomain using htaccess or Mod rewrite ? In this article you can create dynamic subdomain only three steps. Ha ha ha !
You might have noticed some sites having their URLs written as if they were different subdomains of the same domain.

For example, for a news site that has the dynamic links of the following form :

http://yourdomainname.com?page=android   
http://yourdomainname.com?page=iphone
, to be rewritten in this form:
http://android.yourdomainname.com
http://iphone.yourdomainname.com
You can achieve this without actually creating the subdomains on your server. This can be done with Apache mod_rewrite.
For this method to work you need a server that runs Apache and has mod_rewrite module installed. Also, if you don't have access to server configuration files, then you might need some help from your hosting support for the second step and possibly with the fists step of this tutorial. 
 
Step 1.  Create a wildcard DNS A record in your DNS Zone.
A wildcard DNS record is a record represented by the character "*”, that will match all non existing sub domain names. For example *.yourdomainname.com will match for  keyword1. yourdomainname.com , keyword2. yourdomainname.com and so on.
You will need to edit the DNS zone records for your domain and add an A record for *.yourdomainname.com. , pointing to the IP for your domain.
If your domain  is on a shared hosting account, then you will need to search in your control panel for a section for DNS management. Enter a new A type DNS record, set as name "*" and enter the IP for your domain. If you cannot find a DNS management section on your hosting account, then you will have to ask your hosting support to add it for you. 
 

Screen 1



Screen 2


Step 2.  Setup wildcard ServerAlias
You must now configure Apache server to serve the pages that come for any subdomain of your domain. Do this by adding a wildcard ServerAlias.
Add the following line to httpd.conf VirtualHosts section for your domain:
ServerAlias www.yourdomainname.com yourdomainname.com *. yourdomainname.com
Again, if you are on a shared hosting and don't have access to httpd.conf file, and no means in your control panel to edit your VirtualHosts section, then you must ask help from your hosting support.
Step 3. Add rewrite rules to your .htaccess file
First you must prepare your .htaccess file. If the file does not exist, create it. You might already have these lines in your .htaccess files, if you do don't add them again.  

Options +FollowSymLinks
You need this option enabled for your rewrite rules to work. But in most cases is already enabled in the configuration files for the http server.  
RewriteEngine On
Use this line if RewriteEngine is not already enabled on your server.
RewriteBase /
If your code is in the root of your domain, then use / as the rewrite base, like in the line above. If it is in a folder, then use the path to that folder, for example:
RewriteBase /subdomain/

Add the actual rewrite rules: 
RewriteCond %{HTTP_HOST} !www.yourdomainname.com$ [NC]
RewriteCond %{HTTP_HOST} ^(www.)?([a-z0-9-]+). yourdomainname.com [NC]
RewriteRule (.*) index.php?page=%2 [NC,QSA]
First 2 lines add the condition for the actual rewrite rule (line 3) to come in place. 
First line will add an exception for the subdomain www. Add here a similar line for each subdomain that you don't want to follow the same rule.
Second line adds the condition that the URL is in a form that looks like a subdomain, with or without the www string in front (http://anything.yourdomainname.com).
The actual rule is the third line, and will translate any URL that matches the above conditions to a form: http://yourdomainname.com?page=%2.





Wednesday, April 14, 2010

Web Languages Trend | Web Technologies Trend - PHP's rank is number one.

Now  in the world web technologies are very popular. Now a days web technologies are changed and improved in moment. In the world most of opensource languages available but php is changed the web world.

Php is free opensource server side scripting language. Now a days php's trends is very high. In php there are lot's of frameworks available like Wordpress, Joomla ,Typo3, Magento , PhpBB , Zend Framework, Zend Cart , Oscommerce, Smarty, Prestashop, CakePHP,symfony,CodeIgniter,Akelos,PRADO,evoCore etc.

This graph displays the rank of web languages.












See Google Trend Link
http://www.google.com/trends?q=php%2Cdot+net%2Cjsp%2Casp

Thursday, April 8, 2010

Saturday, February 6, 2010

URL Rewriting

The Apache server’s mod_rewrite module gives you the ability to transparently redirect one URL to another, without the user’s knowledge. This opens up all sorts of possibilities, from simply redirecting
old URLs to new addresses, to cleaning up the ‘dirty’ URLs coming from
a poor publishing system — giving you URLs that are friendlier to both
readers and search engines.

An Introduction to Rewriting

Readable URLs are nice. A well designed website will have a logical
file system layout, with smart folder and file names, and as many
implementation details left out as possible. In the most well designed
sites, readers can guess at filenames with a high level of success.

However, there are some cases when the best possible information
design can’t stop your site’s URLs from being nigh-on impossible to
use. For instance, you may be using a Content Management System that
serves out URLs that look something like

http://www.example.com/viewcatalog.asp?category=hats&prodID=53

This is a horrible URL, but it and its brethren are becoming increasingly prevalent in these days of dynamically-generated pages. There are a number of problems with an URL of this kind:


  • It exposes the underlying technology of the website (in this case ASP).
    This can give potential hackers clues as to what type of data they
    should send along with the query string to perform a ‘front-door’
    attack on the site. Information like this shouldn’t be given away if
    you can help it.


    Even if you’re not overly concerned with the security of your site, the technology you’re using is at best irrelevant — and at worst a source of confusion — to your readers, so it should be hidden from them if possible.


    Also, if at some point in the future you decide to change the language that your site is based on (to » PHP,
    for instance); all your old URLs will stop working. This is a pretty
    serious problem, as anyone who has tackled a full-on site rewrite will
    attest.
  • The URL is littered with awkward punctuation, like
    the question mark and ampersand. Those & characters, in particular,
    are problematic because if another webmaster links to this page using that URL, the un-escaped ampersands will mess up their XHTML conformance. They will have to laboriously replace all the ampersands with &amp; character entities, which is often forgotten.
  • Some search engines won’t index pages which they think are generated dynamically. They’ll see that question mark in the URL and just turn their asses around.
Luckily, using rewriting, we can clean up this URL to something far more manageable. For example, we could map it to

http://www.example.com/catalog/hats/53/

Much better. This URL is more logical, readable and memorable, and will be picked up by all search engines. The faux-directories are short and descriptive. Importantly, it looks more permanent.

To use mod_rewrite, you supply it with the link text you want the server to match, and the real URLs that these URLs will be redirected to. The URLs to be matched can be straight file addresses, which will match one file, or they can be regular expressions, which will match many files.


Basic Rewriting

Some servers will not have » mod_rewrite enabled by default. As long as the » module is present in the installation, you can enable it simply by starting a .htaccess file with the command

RewriteEngine on

Put this .htaccess file in your root so that rewriting is enabled
throughout your site. You only need to write this line once per
.htaccess file.

Basic Redirects

We’ll start off with a straight redirect;
as if you had moved a file to a new location and want all links to the
old location to be forwarded to the new location. Though you shouldn’t
really ever » move a file once it has been placed on the web; at least when you simply have to, you can do your best to stop any old links from breaking.

RewriteEngine on
RewriteRule ^old\.html$ new.html

Though this is the simplest example possible, it may throw a few
people off. The structure of the ‘old’ URL is the only difficult part
in this RewriteRule. There are three special characters in there.
  • The caret, ^, signifies the start of an URL, under the current directory. This directory is whatever directory the .htaccess file is in. You’ll start almost all matches with a caret.
  • The dollar sign, $, signifies the end of the string to be matched. You should add this in to stop your rules matching the first part of longer URLs.
  • The period or dot before the file extension is a special character in regular expressions, and would mean something special if we didn’t escape it with the backslash, which tells Apache to treat it as a normal character.
So, this rule will make your server transparently redirect from old.html to the new.html page. Your reader will have no idea that it happened, and it’s pretty much instantaneous.

Forcing New Requests

Sometimes you do want your readers to know a redirect has occurred, and can do this by forcing a new HTTP request for the new page. This will make the browser load up the new page as if it was the page originally requested, and the location bar will change to show the URL of the new page. All you need to do is turn on the [R] flag, by appending it to the rule:

RewriteRule ^old\.html$ new.html [R]

Using Regular Expressions

Now we get on to the really useful stuff. The power of mod_rewrite
comes at the expense of complexity. If this is your first encounter
with regular expressions, you may find them to be a tough nut to crack,
but the options they afford you are well worth the slog. I’ll be
providing plenty of examples to guide you through the basics here.

Using regular expressions you can have your rules matching a set of URLs at a time, and mass-redirect them to their actual pages. Take this rule;

RewriteRule ^products/([0-9][0-9])/$ /productinfo.php?prodID=$1

This will match any URLs that start with ‘products/’, followed by any two digits, followed by a forward slash. For example, this rule will match an URL like products/12/ or products/99/, and redirect it to the PHP page.

The parts in square brackets are called ranges. In this case we’re allowing anything in the range 0-9, which is any digit. Other ranges would be [A-Z], which is any uppercase letter; [a-z], any lowercase letter; and [A-Za-z], any letter in either case.

We have encased the regular expression part of the URL in parentheses, because we want to store whatever value was found here for later use. In this case we’re sending this value to a PHP page as an argument. Once we have a value in parentheses we can use it through what’s called a back-reference. Each of the parts you’ve placed in parentheses are given an index, starting with one. So, the first back-reference is $1, the third is $3 etc.

Thus, once the redirect is done, the page loaded in the readers’ browser will be something like productinfo.php?prodID=12
or something similar. Of course, we’re keeping this true URL secret
from the reader, because it likely ain’t the prettiest thing they’ll
see all day.

Multiple Redirects

If your site visitor had entered something like products/12, the rule above won’t do a redirect, as the slash at the end is missing. To promote good URL writing, we’ll take care of this by doing a direct redirect to the same URL with the slash appended.

RewriteRule ^products/([0-9][0-9])$ /products/$1/ [R]

Multiple redirects in the same .htaccess file can be applied in sequence, which is what we’re doing here. This rule is added before the one we did above, like so:

RewriteRule ^products/([0-9][0-9])$ /products/$1/ [R]

RewriteRule ^products/([0-9][0-9])/$ /productinfo.php?prodID=$1

Thus, if the user types in the URL products/12, our first rule kicks in, rewriting the URL to include the trailing slash, and doing a new request for products/12/ so the user can see that we likes our trailing slashes around here. Then the second rule has something to match, and transparently redirects this URL to productinfo.php?prodID=12. Slick.

Match Modifiers

You can expand your regular expression patterns by adding some modifier characters, which allow you to match
URLs with an indefinite number of characters. In our examples above, we
were only allowing two numbers after products. This isn’t the most
expandable solution, as if the shop ever grew beyond these initial
confines of 99 products and created the URL productinfo.php?prodID=100, our rules would cease to match this URL.
So, instead of hard-coding a set number of digits to look for, we’ll
work in some room to grow by allowing any number of characters to be
entered. The rule below does just that:

RewriteRule ^products/([0-9]+)$ /products/$1/ [R]

Note the plus sign (+) that has snuck in there. This modifier changes whatever comes directly before it, by saying ‘one or more of the preceding character or range.’ In this case it means that the rule will match any URL that starts with products/ and ends with at least one digit. So this’ll match both products/1 and products/1000.

Other match modifiers that can be used in the same way are the asterisk, *, which means ‘zero or more of the preceding character or range’, and the question mark, ?, which means ‘zero or only one of the preceding character or range.’

Adding Guessable URLs

Using these simple commands you can set up a slew of ‘shortcut URLs’ that you think visitors will likely try to enter to get to pages they know exist on your site. For example, I’d imagine a lot of visitors try jumping straight into our stylesheets
section by typing the URL http://www.yourhtmlsource.com/css/. We can
catch these cases, and hopefully alert the reader to the correct
address by updating their location bar once the redirect is done with these lines:

RewriteRule ^css(/)?$ /stylesheets/ [R]

The simple regular expression in this rule allows it to match
the css URL with or without a trailing slash. The question mark means
‘zero or one of the preceding character or range’ — in other words
either yourhtmlsource.com/css or yourhtmlsource.com/css/ will both be
taken care of by this one rule.

This approach means less confusing 404 errors for your readers, and a site that seems to run a whole lot smoother all ’round.

Wednesday, January 27, 2010

Indians can now verify PayPal account without a credit card!


PayPal
users need to get their account verified in order to lift their Sending and Withdrawal limits. Great news is here, users can now verify their PayPal account by linking and confirming their bank account without the need of a credit card. This is definitely good news especially for users of India.

How to verify PayPal using a bank account - A simple 3 step procedure is required to become a verified member.

1. Login to PayPal and click on 'Get verified' link shown in Status.




2. Select Link my Bank Account option.




 

3. Add a bank account > Start process to confirm bank account and get verified. PayPal will then send 2 small deposits to your bank account.






4. To confirm your bank account:

  • Check your bank account statement in 4-6 days for the 2 deposits from PayPal.
  • Log in to your PayPal account and enter the amounts to confirm your bank account.
This completes the final step of verification process, thus removing any limits on your account. Now, you can send and withdraw as much money using your PayPal account.

Monday, January 11, 2010

Ie6 PNG transparency Fix / Hack

As IE6 doesn't support Alpha Channel Transparency PNG files. With this code we can use PNG’s In IE 6.
Just Copy and paste this code in this CSS file. Copy transparent.gif in to "images" folder.


/*Start css code*/

* html img,
* html .png
{position:relative; behavior: expression((this.runtimeStyle.behavior="none")&&(this.pngSet?this.pngSet=true:(this.nodeName == "IMG" && this.src.toLowerCase().indexOf('.png')>-1?(this.runtimeStyle.backgroundImage = "none",this.runtimeStyle.filter = "progid:DXImageTransform.Microsoft.AlphaImageLoader(src='" + this.src + "', sizingMethod='image')", this.src = "images/transparent.gif"):(this.origBg = this.origBg? this.origBg :this.currentStyle.backgroundImage.toString().replace('url("','').replace('")',''),this.runtimeStyle.filter = "progid:DXImageTransform.Microsoft.AlphaImageLoader(src='" + this.origBg + "', sizingMethod='crop')",this.runtimeStyle.backgroundImage = "none")),this.pngSet=true));}

/*End css code*/

Image : transparent.gif




Monday, January 4, 2010

Google Apps Account

Google offers a wonderful free service called Google Apps. Google Apps gives everyone who has there own domain top notch Email services, world class spam filtering, online word processing, online spreadsheets, a shared calendaring system and access to a flexible intranet system.

Because Google stores all of the files and content centrally (online), collaboration and document management become far simpler than when distributing files to multiple people and keeping track of different versions.

With a few changes to your DNS configuarion, Google apps can closely integrate with your web hosting account here at VodaHost, providing a much more robust web platform based around your existing domain name.

Click Here to create your Google Apps Account...It's 100% Free!

NOTE: If you want to use Googles webmail service with your domain name...You must update your MX Records in cPanel....This will have the effect of all your domain name based email going through Googles servers a and you will be able to use Google webmail interface....

How to update Your MX Records in cPanel

1. Log in to your cPanel account.
2. Click Mail.
3. Click Modify Mail Exchanger (MX Entry). A list of your current MX records will appear.
4. Click Change an MX Entry.
5. In the Change MX for... field, enter ASPMX.L.GOOGLE.COM.
6. Click Change.