I'll admit that I am not a coder and I don't know
much more than a tiny bit of PHP at the time of writing this. However,
I have managed to create database driven webpages, and even password
protected members only areas due to the extremely easy to use PHP
buttons in Dreamweaver.


If you are interested in learning to
do this for yourself, this lesson will point you in the right direction
so that you can experiment and see for yourself how easy it is.



The first thing you need to do is to create an SQL database on your
webhost. This can be done via CPanel or if not that, then ask your host
how...anyways, creating an SQL database with 1 table is not hard.



The key is, to create it, record the information and then try to log in to that database via Dreamweaver.



You can do this by creating a new database connection in the 'Application' window of Dreamweaver.



This is one of the most challenging parts, and you'll need to set up
the site's testing server. At first this can be tricky, but if you
stick with it and get connected to your SQL databas via Dreamweaver,
you'll soon find ways to insert records, display records, and much more!



You see, once you are connected to the database, the table names will
dynamically show up in Dreamweaver, and from there it is only a short
step to learn how to insert records, repeat records, and display data
in the database.



Of course reading a book can help you with PHP, but it is also fun to just jump right in the Dreamweaver buttons.




Even a total PHP dunce like myself was able to start creating little PHP/SQL applications once I figured out these basic steps.



So if you want to create PHP applications, but don't know how to
hand-code PHP, create a PHP/SQL database with 1 table, figure out how
to connect to it via Dreamweaver, and start messing around with the
Dreamweaver PHP buttons.



In a few hours time you'll see what creating PHP/SQL applications in Dreamweaver is all about.

For more information on Dreamweaver including step by step video tutorials, visit http://www.dreamweaverhowto.com

J.
Gilbert Offers awesome step by step video tutorials that show people
how to set up various aspects of an online information business. You
can see more of his products at http://www.resource-website.com

Read More...

PHPsuexec works in much the same way that CGI (perl
scripts etc) with suexec does. All PHP scripts will be run under your
account user name UID/GID, rather than the user running the web server
which is the case when PHP is run as an apache module.

This
simply means that rules that apply to .cgi & .pl files on your
current server, now also apply to PHP files. The maximum permissions
permitted on directories and .PHP files are 755. Failing to have
permissions set to a MAXIMUM of 755 on PHP files and their installation
paths will result in a 500 internal server error, when attempting to
execute them.

What if a script needs 777 for directories or files!

This
is no longer required. You do not need to have directories or files set
to 777, even if your installation documents tell you that you do.
Permissions of 755 will work in the same way. Scripts owned by your
account user will be able to write to your files in the same way that
they can running under apache with 777 permissions.

If you have
PHP applications/scripts that have directories set to 777, (required to
write to them under PHP/apache module), they will need to be changed to
755. Also you will need to change ownerships of all files owned by user
"nobody" to the username for your account.

.htaccess

You can no longer manipulate the php.ini settings with .htaccess files.

If
you are using .htaccess with php_value entries within it, you will
receive a 500 internal server error when attempting to access the
scripts. This is because PHP is no longer running as an apache module
and apache will not know how to handle those directives any longer. All
PHP values should be removed from your .htaccess files to avoid this
issue. Placing a php.ini file in its place will solve this issue.

Read more
http://www.techentrance.com

Read More...