Cote de Azur
About C#/.NET programming, BlogEngine usage, and Software testing
About C#/.NET programming, BlogEngine usage, and Software testing
Apr 28th
As a web developer begins to delve into more complex development tasks, PHP is often their chosen language of choice. We’ve put together a list of the top 10 questions asked about the PHP programming language to get you started!
PHP is a recursive acronym for “PHP: Hypertext Preprocessor”. PHP is a widely-used general-purpose scripting language that is especially suited for web development and can be embedded into HTML. Much more info can be found at PHP.net.
The manual is on-line here and is also available in other languages and downloadable versions.
For a beginner’s tutorial on PHP, check out this Zend.com tutorial.
Yes, but note that in addition to PHP you will need a web server running on your PC, too. A very convenient and effective way to do this is to download and install Apachefriends.org’s XAMPP, which is an open-source program which will install PHP, Apache web server, MySQL DBMS, and phpMyAdmin onto your PC.
We have put together a great tutorial with useful information and example code on this subject.
This is not a trivial project (unless done very poorly and with little to no consideration for security). Consider using one of the many open-source CMS’s which are available. OpenSourceCMS has lots of info on some of the many choices.
The line number in a PHP parse error message is the line where PHP “got too confused and gave up,” but it’s not necessarily the line where the root cause of the problem occurred. When you get such a message start looking at that line, then start working your way back through the code for various syntax errors (missing “;”, unbalanced brackets or quotes, etc.) It is worth using an editor with PHP syntax color-coding to help you see some of these errors.
Learn to code defensively. Do not assume variables are set the way you think they should be; instead check their values before proceeding using functions like isset() and empty(). Learn to use PHP’s error-handling functions.
This is usually done by using PHP sessions in conjunction with a database. The database contains login information which is used to verify the user’s login. Upon successful login, a session variable can be set. Controlled pages can then first check to see if this session variable exists and is properly set, and if not then redirect the user to the login page. Here is one article of many on the web on this subject.
Simply put, by using the mail() function. For more info, check out this article by Web Developer forum member Bokeh.
Apr 26th
I have another ERROR discovered by PEAR PHP_CodeSniffer, http://pear.php.net/package/PHP_CodeSniffer:
End of line character is invalid; expected “n” but found “rn”
And this ERROR is only occurring at the very first line, at , in my PHP code.
For new files, you can change the default line delimiter to Unix style, such as in Eclipse, you can,
Window –>
Apr 17th
Both pear and pecl tools should be available everywhere on command line. For that to work, pear’s binary (bin) directory should be in your PATH variable.
To verify it works, simply type pear. A list of commands should be shown:
$
Apr 17th
I want to install PEAR manager for PHP 5.3.2 with apache on Windows, while run go_pear.bat
Apr 17th
While I am install the PEAR for PHP 5.3.2 version with display_errors settings on, I get following error,
===========================================================
Warning: date(): It is not safe to rely on the system’s timezone settings. You a
re *required* to use the date.timezone setting or the date_default_timezone_set(
) function. In case you used any of those methods and you are still getting this
Apr 16th
Apr 15th
PHPUnit 3.4 requires PHP 5.1.4 (or later) but PHP 5.3.2 (or later) is highly recommended. It should be installed using the PEAR Installer. This installer is the backbone of PEAR, which provides a distribution system for PHP packages, and is shipped with every release of PHP since version 4.3.0.
The PEAR channel (pear.phpunit.de) that is used to distribute PHPUnit needs to be registered with the local PEAR environment. Furthermore, a component that PHPUnit depends upon is hosted on the Symfony Components PEAR channel (pear.symfony-project.com).
pear channel-discover pear.phpunit.de
pear channel-discover pear.symfony-project.com
This has to be done only once. Now the PEAR Installer can be used to install packages from the PHPUnit channel:
pear install phpunit/PHPUnit
After the installation you can find the PHPUnit source files inside your local PEAR directory; the path is usually /usr/lib/php/PHPUnit.
Although using the PEAR Installer is the only supported way to install PHPUnit, you can install PHPUnit manually. For manual installation, do the following:
Download a release archive from http://pear.phpunit.de/get/ and extract it to a directory that is listed in the include_path of your php.ini configuration file.
Prepare the phpunit script:
Rename the phpunit.php script to phpunit.
Replace the @php_bin@ string in it with the path to your PHP command-line interpreter (usually /usr/bin/php).
Copy it to a directory that is in your path and make it executable (chmod +x phpunit).
Prepare the PHPUnit/Util/PHP.php script:
Replace the @php_bin@ string in it with the path to your PHP command-line interpreter (usually /usr/bin/php).
Apr 15th
by Christopher Heng, thesitewizard.com
Many web developers want to run Apache and PHP on their own computer since it allows them to easily test their scripts and programs before they put them “live” on the Internet. This article gives a step by step guide on how you can install and configure PHP5 to work together with the Apache HTTP Server on Windows. The procedure has been tested to work on both Windows XP and Vista.
If you have not already installed Apache on your machine, check out one of the guides listed below. This “How To” guide assumes that you have already completed installing Apache.
If you are using Apache 1.3.x, see the guide How to Install the Apache Web Server 1.x on Windows.
If you plan to use one of the Apache 2 or 2.2 web servers on Windows XP, see the tutorial How to Install and Configure Apache 2 on Windows instead.
If you are using Apache 2.2 on Windows Vista, please read How to Install Apache 2.2 on Windows Vista.
Note: those planning to install PHP 4 on Apache 1.x should read my article How to Install and Configure PHP4 to Run with Apache on Windows instead.
Before you begin, get a copy of PHP 5 from the PHP download page. In particular, download the VC6 thread-safe zip package from the “Windows Binaries” section — that is, don’t get the installer. For example, select the package labelled “PHP 5.2.5 zip package” if 5.2.5 is the current version.
[Update: note that I have not tested the procedure below with any of the PHP 5.3 versions, only with 5.2.5, which was the latest version at the time I originally wrote this. In theory, the procedure should work with later 5.2 versions as well. I'm not sure about 5.3 though. A version jump from 5.2 to 5.3 usually means bigger changes than simple bug fixes. If you want to be sure the procedure below will work, just get the latest of the 5.2 series.]
Create a folder on your hard disk for PHP. I suggest “c:php” although you can use other names if you wish. Personally though, I prefer to avoid names with spaces in it, like “c:Program Filesphp” to avoid potential problems with programs that cannot handle such things. I will assume that you used c:php in this tutorial.
Extract all the files from the zip package into that folder. To do that simply double-click the zip file to open it, and drag all the files and folders to c:php.
If you are upgrading to PHP 5 from an older version, go to your windows directory, typically c:windows, and delete any php.ini file that you have previously placed there.
Go to the c:php folder and make a copy of the file “php.ini-recommended”. Name the new file “php.ini”. That is, you should now have a file “c:phpphp.ini”, identical in content with “c:phpphp.ini-recommended”.
Note: if you are using Apache 1, you should either move the php.ini file to your windows directory, “C:Windows” on most systems, or configure your PATH environment variable to include “c:php”. If you don’t know how to do the latter, just move the php.ini file to the “c:windows” folder. You do not have to do this if you are using Apache 2, since we will include a directive later in the Apache 2 configuration file to specify the location of the php.ini file.
Use an ASCII text editor (such as Notepad, which can be found in the Accessories folder of your Start menu) to open “php.ini”. You may need to make the following changes to the file, depending on your requirements:
Search for the line that reads:
If short_open_tag is set to “off”, tags like “" will not be recognised as the start tag for a PHP script. In such a case, to begin a PHP script, you will need to code your script with an opening tag like "commercial web hosts that support PHP have no issues with your scripts using “" as the open tag. To fix this, change it to the following:
By default, input data is not escaped with backslashes. That is, if your visitors enter an inverted comma (single quote) into your web form, the script will receive that unadorned inverted comma (single quote). This is for the most part desirable unless you special requirements. If you want your input data to have the backslash (“”) prefix, such as, for example, to mimic your web host’s settings, search for the following:
and replace it with:
Do not do this unless your web host has this setting as well. Even with the setting of “Off”, you can still use the addslashes() function in PHP to add the slashes for the specific pieces of data that need them.
A number of older scripts assume that all data sent by a form will automatically have a PHP variable of the same name. For example, if your form has an input field with a name of “something”, older PHP scripts assume that the PHP processor will automatically create a variable called $something that contains the value set in that field.
If you are running such scripts, you will need to look for the following field:
and change it to the following:
WARNING: Do NOT do this unless you have third party scripts that need it. When writing new scripts, it’s best to always code with the assumption that the register_globals item is set to “Off”.
On a “live” website, you typically want errors in your script to be silently logged to a PHP error file. On your own local machine, however, while you are testing and debugging a PHP script, it is probably more convenient to have error messages sent to the browser window when they appear. This way, you won’t miss errors if you forget to check the error log file.
If you want PHP to display error messages in your browser window, look for the following:
And change it to:
This value should always be set to “Off” for a “live” website.
If your script uses sessions, look for the following line:
The session.save_path sets the folder where PHP saves its session files. Since “/tmp” does not exist on Windows, you will need to set it to a directory that does. One way is to create a folder called (say) “c:tmp” (the way you created c:php earlier), and point this setting to that folder. If you do that, change the line to the following:
Notice that in addition to changing the path, I also removed the semi-colon (“;”) prefix from the line.
Alternatively, you can find out the current TEMP folder on your computer and use that. Or create a “tmp” folder in your PHP directory, like “c:phptmp” and set the configuration file accordingly. The possibilities are endless. If you can’t decide, just create “c:tmp” and do as I said above.
If your script uses the mail() function, and you want the function to successfully send mail on your local machine, look for the following section:
; For Win32 only.
;sendmail_from = me@example.com
Change it to point to your SMTP server and email account. For example, if your SMTP server is “mail.example.com” and your email address is “youremail@example.com”, change the code to:
Note that after you do this, when your script tries to use the mail() function, you will need to be connected to your ISP for the function to succeed. If you do not modify the above lines and attempt to use mail() in your script, the function will return a fail code, and display (or log) the error (depending on how you configure php.ini to handle errors).
(Note that in Apache 1.x, the smtp_port line may not be present. If so, don’t include it.)
There are two ways to set up Apache to use PHP: the first is to configure it to load the PHP interpreter as an Apache module. The second is to configure it to run the interpreter as a CGI binary. I will supply information for how you can accomplish both, but you should only implement one of these methods. Choose the module method if your web host also installed PHP as an Apache module, and use the CGI method if they have implemented it to run as a CGI binary.
To configure Apache to load PHP as a module to parse your PHP scripts, use an ASCII text editor to open the Apache configuration file, “httpd.conf”. If you use Apache 1.x, the file is found in “c:Program FilesApache GroupApacheconf”. Apache 2.0.x users can find it in “C:Program FilesApache GroupApache2conf” while Apache 2.2.x users can find it in “C:Program FilesApache Software FoundationApache2.2conf”. Basically, it’s in the “conf” folder of wherever you installed Apache.
Search for the section of the file that has a series of “LoadModule” statements. Statements prefixed by the hash “#” sign are regarded as having been commented out.
If you are using Apache 1.x, add the following line after all the LoadModule statements:
If you are using Apache 2.0.x, add the following line after all the LoadModule statements:
If you are using Apache 2.2.x, add the following line instead:
Note carefully the use of the forward slash character (“/”) instead of the traditional Windows backslash (“”). This is not a typographical error.
If you are using Apache 1.x, search for the series of “AddModule” statements, and add the following line after all of them. You do not have to do this in any of the Apache 2 series of web servers.
Next, search for “AddType” in the file, and add the following line after the last “AddType” statement. Do this no matter which version of Apache you are using. For Apache 2.2.x, you can find the “AddType” lines in the
If you need to support other file types, like “.phtml”, simply add them to the list, like this:
Finally, for those using one of the Apache 2 versions, you will need to indicate the location of your PHP ini file. Add the following line to the end of your httpd.conf file.
Of course if you used a different directory for your PHP installation, you will need to change “c:/php” to that path. Remember to use the forward slash (“/”) here again.
If you are using Apache 1, you will have already placed your php.ini file in either the Windows directory or somewhere in your PATH, so PHP should be able to find it by itself. You can of course do the same if you are using Apache 2, but I find modifying the Apache configuration file a better solution than cluttering your c:windows directory or your PATH variable.
If you have configured PHP 5 to run as an Apache module, skip forward to the next section. This section is for those who want to configure PHP to run as a CGI binary.
The procedure is the same whether you are using the Apache 1.x series or one of the 2.x series.
Search for the portion of your Apache configuration file which has the ScriptAlias section. Add the line from the box below immediately after the ScriptAlias line for “cgi-bin”. If you use Apache 2.2.x, make sure that the line goes before the closing for that
Note that if you installed PHP elsewhere, such as “c:Program Filesphp”, you should substitute the appropriate path in place of “c:/php/” (for example, “c:/Program Files/php/”). Observe carefully that I used forward slashes (“/”) instead of the usual Windows backslashes (“”) below. You will need to do the same.
Apache needs to be configured for the PHP MIME type. Search for the “AddType” comment block explaining its use, and add the AddType line in the box below after it. For Apache 2.2.x, you can find the AddType lines in the
As in the case of running PHP as an Apache module, you can add whatever extensions you want Apache to recognise as PHP scripts, such as:
Next, you will need to tell the server to execute the PHP executable each time it encounters a PHP script. Add the following somewhere in the file, such as after the comment block explaining “Action”. If you use Apache 2.2.x, you can simply add it immediately after your “AddType” statement above; there’s no “Action” comment block in Apache 2.2.x.
Note: the “/php/” portion will be recognised as a ScriptAlias, a sort of macro which will be expanded to “c:/php/” (or “c:/Program Files/php/” if you installed PHP there) by Apache. In other words, don’t put “c:/php/php.exe” or “c:/Program Files/php/php.exe” in that directive, put “/php/php-cgi.exe”.
If you are using Apache 2.2.x, look for the following section in the httpd.conf file:
Add the following lines immediately after the section you just found.
This section applies to all users, whether you are using PHP as a module or as a CGI binary.
If you create a file index.php, and want Apache to load it as the directory index page for your website, you will have to add another line to the “httpd.conf” file. To do this, look for the line in the file that begins with “DirectoryIndex” and add “index.php” to the list of files on that line. For example, if the line used to be:
change it to:
The next time you access your web server with just a directory name, like “localhost” or “localhost/directory/”, Apache will send whatever your index.php script outputs, or if index.php is not available, the contents of index.html.
Restart your Apache server. This is needed because Apache needs to read the new configuration directives for PHP that you have placed into the httpd.conf file. The Apache 2.2 server can be restarted by doubleclicking the Apache Service Monitor system tray icon, and when the window appears, clicking the “Restart” button.
Create a PHP file with the following line:
Save the file as “test.php” or any other name that you fancy, but with the “.php” extension, into your Apache htdocs directory. If you are using Notepad, remember to save as “test.php” with the quotes, or the software will add a “.txt” extension behind your back.
Open your browser and access the file by typing “localhost/test.php” into your browser’s address bar. Do not open the file directly on the hard disk – you’ll only see the words you typed in earlier. You need to use the above URL so that the browser will try to access your Apache web server, which in turn runs PHP to interpret your script.
If all goes well, you should see a pageful of information about your PHP setup. Congratulations – you have successfully installed PHP and configured Apache to work with it. You can upload this same file, test.php, to your web host and run it there to see how your web host has set up his PHP, so that you can mimic it on your own machine.
If for some reason it does not work, check to see whether your PHP setup or your Apache setup is causing the problem. To do this, open a Command Prompt window (found in the “Accessories” folder of your “Start” menu) and run php-cgi.exe on test.php with a command line like “c:phpphp-cgi test.php” (without the quotes).
If invoking PHP from the command line causes a large HTML file with all the PHP configuration information to be displayed, then your PHP set up is fine. The problem probably lies with your Apache configuration. Make sure that you have restarted the Apache server after making configuration changes. Verify that you have configured Apache correctly by looking over, again, the instructions on this page and the steps given in How to Install and Configure Apache 1.x for Windows (for Apache 1.x users) or How to Install and Configure Apache 2 on Windows (for Apache 2.x users).
The complete PHP reference manual can be obtained from the php website. You can refer to it online or download the entire set of HTML files for reference offline. As its name implies, it is a reference manual only. For tutorials, check out the PHP tutorials at thesitewizard.com. If you are new to writing PHP scripts, the following chapters may interest you:
Have fun!
Apr 14th
FollowSymLinks is a directive in your web server configuration that tells your web server to follow so called symbolic links. As one would expect, FollowSymLinks is an acronym for Follow Symbolic Links. FollowSymLinks is a very important setting that plays a role in your website security.
In the following text, we will explain general knowledge about FollowSymLinks with some emphasis and how it relates to the Apache
Apr 14th
Order allow,deny is a setting in your Apache web server configuration that is used to restrict access to certain