You have a working wordpress website on your localhost server and when you need to migrate or copy the same wordpress website to your live server, what should you do ?
To install a fresh copy of wordpress and put all the data again and again is very frustrating.
I think almost all the wordpress developers face this problem. I have a solution to this problem.
There is a very simple way to get rid of this problem.
You just need to download the SQL file from your database and make a copy of your wordpress website folder.
Now open the wp-config.php which is present at the root directory and write the database details you have for your live server.
Now open the SQL file in the editor (I prefer Adobe Dreamweaver), and find http://localhost/yourfoldername/ and replace this with http://www.mywebsite.com/.
You are all done. Just upload the folder through any FTP client and upload the database and enjoy your website fully functional like your local version.
PHP Sessions allow web pages to be treated as a group, allowing variables to be shared between different pages. One of the weaknesses of cookies is that the cookie is stored on the user’s computer (and by user we mean the person with the browser visiting your web site). This provides the user the ability to access, view and modify that cookie for potentially nefarious purposes. PHP sessions, on the other hand, store only an ID cookie on the user’s system which is used to reference the session file on the server. As such, the user has no access to the content of the session file, thereby providing a secure alternative to cookies. PHP sessions also work when the user has disabled the browser’s cookie support. In this situation it includes the session ID information in the web page URLs.
PHP sessions are created using the session_start() function which should the first function call of the PHP script on your web page (i.e. before any output is written to the output stream).
The following example demonstrates the creation of a PHP session:
<title>A PHP Session Example</title>
</html> Continue reading
Web servers are typically stateless entities. That is to say they serve up web pages without regard to who requested the page and with no knowledge of whether that person has previously requested other pages. This makes it difficult for web based applications to track whether a visitor is new to the site or whether they have visited before and have already logged into a service. Cookies were developed to provide a mechanism to track state in the otherwise stateless world of the web.
Cookies essentially provide a mechanism to store small pieces of data on the computer systems of the visitors to your site. This enables you to maintain the state of a user’s visit to your site so that you can track their movement through the site, or to store information such as their user name and address after they have entered it on one page so that they don’t have to keep re-entering it on different pages.
Before going too far in implementing cookies on your web site it is important to keep in mind that users can disable cookie support in their browsers. You should, therefore, avoid making your site completely dependent on cookies.
Another option for maintaining state is to use PHP Sessions. Cookies and sessions differ in important ways, and which to use depends on your requirements. Continue reading
By default Maximum file upload size is 128MB.
php_value upload_max_filesize 128M
php_value post_max_size 128M
If you want to change the default Maximum file upload size from 128MB to 1GB, then it can be done by changing in the these files..
.htaccess file (Apache + mod_php) add the following two lines to a
.htaccess in the installed directory:
php_value upload_max_filesize 1G
php_value post_max_size 1G
2.) In php.ini file, which is located in the php folder (like C:/xampp/php/php.ini)
upload_max_filesize = 1G
post_max_size = 1G
After modifying the global
php.ini you will need to restart the webserver to have changes take effect.