At whatever point it comes to web development, numerous developers need tips to progress the site. Web development in PHP is beautiful simple for newbies. All you would like is PHP tips and tricks for beginners and the most straightforward way to optimize PHP site.
PHP is one of the foremost cherished and broadly utilized languages that developers adore to build their site from. The finest portion of PHP advancement is that developers can discover Guide for PHP developers and best PHP tips and tricks on the official site of PHP. Another advantage of PHP is that as a PHP developer you'll be able to discover great frameworks and CMSs to work on.
This blog post is all around the leading PHP tips and tricks for Web development in PHP so that you can create your site in PHP without any bother and you'll appreciate your proficient life.
Stay Away from Anything Ending With _once()
Develop With Error Reporting On
Use A Framework If You Need One
Use PHP's Inbuilt Functions
Protect Your Database
Use POST Not GET
Draw Before You Code
Understand Your Project
Code Code Code
In case you have got not however entered the realm of Object-Oriented Programming, at that point you're at a drawback, and you're falling behind quick.
OOP is basically a strategy of programming with the utilize of classes, or Objects, which tie like things together, expel the require for redundancy of code and perform the essential tasks of production very basically. Objects are basically classes that collect a bunch of functions together and wrap them in a wrapper that can be reused over and over once more without the ought to rewrite functionality or methods each time you wish to do something.
Procedural Programming works by following a routine from the best to the bottom of each page as the server reads each file on your server. With OOP, there might be one or two objects being instantiated, which, in turn, may instantiate few, a hundred or a thousand other objects which could all perform certain tasks depending on variables passed into the objects. OOP is faster, less complex, easier to debug, futile server assets, less code, is faster stacking and more coherent to work with once you figure out the fundamental principles.
We all know that include() simply gives us a warning if it fails, while require() kills the script with a fatal error when it fails. What we don't forget is thatinclude_once() and require_once() is extremely hard on server resources. There is nothing we can do about it, it's how PHP is set up. Just remember that these things kill your server resources, especially on a huge framework, and if you plan your code properly you won't even need it anyway.
The very first thing you do when starting a new project is to turn error reporting to E_ALL, and you should only turn it off ten seconds before going into production mode. I do this with every project that I build and there is nothing better than running a project in full production mode and not even getting one error. Besides that, with error reporting on, you pick up any small errors that will eventually grow up to bite you in the... well, you get my point.
Rasmus Lerdorf says you shouldn't use a framework because he could quite conclusively prove that a framework is much slower than normal PHP code when it came to printing a simple "Hello World" application. Two things to mention here though: you are not Rasmus Lerdorf and I bet you won't be building a "Hello World" application every time you program something. Frameworks that assist you to do the tedious things can help, although you may need to learn how the systems work to begin within in order to create things straightforward, that's the as it were the genuine trade-off. Also, you stand less chance of writing terrible code when somebody else has composed most of it for you.
You want to count the number of keys in an array? You can loop through the array and simply increment a value for each iteration, right? Or you can just use the built-in PHP function count(), which does just what it should. PHP has many built-in functions that can do what you need them to, so check out the manual to make sure you are doing it in the best way possible.
The best and safest way is to use mysql_real_escape_string() for all database before it is added to the database. This function makes all strings safe in terms of quotes and other functions that can harm your database or contain malicious code, so use it to be sure you have taken the first step against protection of your data. Another thing you can do is validate all POST and GET strings, never use $_REQUEST, and make sure all form submitted data is of the right type and value before adding it to a database query.
This isn't always possible, but when it is really not necessary, don't use GET, use the POST. The reason is simple - GET is simple to emulate, all I need to do is add something to my address bar and I can hack your project. Obviously GET is the easy way to do pagination and permalinks, but when using form submission especially, stay with the POST, it's safer.
A good practice to get into is to wireframe your projects, even if you are just scribbling a few notes on a piece of paper. It is very important to actually give the mechanics of your application some thought before sitting down to start coding, because in the process of planning it you will actually iron out the difficulties in your head and avoid a major headache that comes with the facepalm when you realize that everything you just did is either wrong, not needed, or just silly.
An artist cannot draw something that he has not seen before. A singer cannot sing a song that he has not heard before. You cannot code a project that you do not fully understand. If you do not understand exactly what it needs to do, and how it needs to it, you cannot build it.
If I could get one thing through to anyone reading this, this is it. You cannot become a good developer by reading. You cannot become a good developer by watching someone develop. The one and only tried and trusted method, is to actually write code. But - and here is the trick - build real things! Do not go and code something that you have no interest in, or will never use. Build what you like, and you will be excited and interested by it, and you will learn. Then, make it awesome, build upon it, and make it better.