Comments on: Basic file includes http://www.stuffbysarah.net/2005/08/26/basic-file-includes/ PHP, WordPress and Business Ramblings Thu, 02 Feb 2012 19:31:59 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Sarah http://www.stuffbysarah.net/2005/08/26/basic-file-includes/comment-page-1/#comment-14853 Sarah Wed, 16 Jul 2008 09:05:53 +0000 #comment-14853 Well it should give you the basics. I kind of ran out of time after a while but to be honest once the basics make sense a book would most likely be the next step. The SitePoint Learning PHP book is a good choice. Well it should give you the basics. I kind of ran out of time after a while but to be honest once the basics make sense a book would most likely be the next step. The SitePoint Learning PHP book is a good choice.

]]> By: Marc Eilbeck http://www.stuffbysarah.net/2005/08/26/basic-file-includes/comment-page-1/#comment-14844 Marc Eilbeck Tue, 15 Jul 2008 20:08:21 +0000 #comment-14844 Very nice guide to learning php. Its something ive always wanted to learn so I think I will be coming back and reading the whole guide at some point! Very nice guide to learning php. Its something ive always wanted to learn so I think I will be coming back and reading the whole guide at some point!

]]> By: Sarah http://www.stuffbysarah.net/2005/08/26/basic-file-includes/comment-page-1/#comment-215 Sarah Sat, 04 Feb 2006 18:01:47 +0000 #comment-215 Not really. .inc just stands for include. It's not a recognised file extension as is parsed by browsers as plain text. .inc and .inc.php are just used by programmers so they realise that they're includes. When you start on large sites and working with lots of files, it makes understanding a file structure easier. Not really. .inc just stands for include. It's not a recognised file extension as is parsed by browsers as plain text.

.inc and .inc.php are just used by programmers so they realise that they're includes.

When you start on large sites and working with lots of files, it makes understanding a file structure easier.

]]> By: pest http://www.stuffbysarah.net/2005/08/26/basic-file-includes/comment-page-1/#comment-214 pest Sat, 04 Feb 2006 17:49:01 +0000 #comment-214 phew! was worried I had some re-building to do there! still I guess it's possible that my includes might contain something important in the future! is there any benifit to .inc? phew! was worried I had some re-building to do there!

still I guess it's possible that my includes might contain something important in the future!

is there any benifit to .inc?

]]> By: Sarah http://www.stuffbysarah.net/2005/08/26/basic-file-includes/comment-page-1/#comment-213 Sarah Sat, 04 Feb 2006 17:44:46 +0000 #comment-213 Good point. I said what to do but not why. A .inc file will be parsed by a browser as plain text. This is fine if that .inc file doesn't contain any important information. But when you come to start placing in sensitive information, which can range from the top most ie. usernames and passwords through to even the knowledge of variable names, then someone could use the information they can see and compromise your site or even the server you're on. By using .inc.php you're telling yourself it's an include file but you're telling the browsers to parse it as PHP, therefore any PHP would be executed, not displayed for all to see. For example, if you have <code><?php // config.inc - store mysql connection details $username = "dbuser"; $password = "dbpass"; ?></code> a simple include with your mysql username and password in for use throughout the site for database connections. Well if I could view that as plain text then I'd know your username and password. So ideally I tend to use .php for PHP pages, .inc.php for includes, .fnc.php for functions and .scr.php for pure script. Just makes it easier to find files on very large sites. Good point. I said what to do but not why. A .inc file will be parsed by a browser as plain text. This is fine if that .inc file doesn't contain any important information. But when you come to start placing in sensitive information, which can range from the top most ie. usernames and passwords through to even the knowledge of variable names, then someone could use the information they can see and compromise your site or even the server you're on.

By using .inc.php you're telling yourself it's an include file but you're telling the browsers to parse it as PHP, therefore any PHP would be executed, not displayed for all to see.

For example, if you have

<?php
// config.inc - store mysql connection details
$username = "dbuser";
$password = "dbpass";
?>

a simple include with your mysql username and password in for use throughout the site for database connections. Well if I could view that as plain text then I'd know your username and password.

So ideally I tend to use .php for PHP pages, .inc.php for includes, .fnc.php for functions and .scr.php for pure script. Just makes it easier to find files on very large sites.

]]> By: pest http://www.stuffbysarah.net/2005/08/26/basic-file-includes/comment-page-1/#comment-211 pest Sat, 04 Feb 2006 17:28:40 +0000 #comment-211 Hi, I just started using xhtml and basic includes (about three months ago) except i've been using (for example) "footer.inc", rather than - "footer.inc.php" is this a problem? Hi,

I just started using xhtml and basic includes (about three months ago)

except i've been using (for example) "footer.inc",
rather than – "footer.inc.php"

is this a problem?

]]>