Prepend and Append Files with .htaccess
One of the lessor known and used capabilities of .htaccess files is the ability to prepend and append includes to every page request. Doing so avoids needing to code <?php require('footer.php'); ?> in every template file you wat to use them in. Here's the .htaccess code:
# Prepend the file
php_value auto_prepend_file "/dir/path/utilities.php"
# Append file to bottom of page
php_value auto_append_file "/dir/path/templates/footer.php"
Now don't mistake this post as me telling you to use this strategy; using this functionality creates a layer of indirection that could confuse a team of developers if they don't all have a grasp of where automatically included files are coming from. Just wanted to let you know this was possible!
![5 HTML5 APIs You Didn’t Know Existed]()
When you say or read "HTML5", you half expect exotic dancers and unicorns to walk into the room to the tune of "I'm Sexy and I Know It." Can you blame us though? We watched the fundamental APIs stagnate for so long that a basic feature...
![9 More Mind-Blowing WebGL Demos]()
With Firefox OS, asm.js, and the push for browser performance improvements, canvas and WebGL technologies are opening a world of possibilities. I featured 9 Mind-Blowing Canvas Demos and then took it up a level with 9 Mind-Blowing WebGL Demos, but I want to outdo...
![Create a Simple Slideshow Using MooTools, Part II: Controls and Events]()
Last week we created a very simple MooTools slideshow script. The script was very primitive: no events and no next/previous controls -- just cross-fading between images. This tutorial will take the previous slideshow script a step further by:
Adding "Next" and "Previous" controls.
Adding...
![MooTools Kwicks Plugin]()
I wrote a post titled Get Slick with MooTools Kwicks ages ago. The post was quite popular and the effect has been used often. Looking back now, the original code doesn't look as clean as it could. I've revised the original...
this strategy is often used to hook a profiler into an existing app, which works great in DEV environments
see e.g. http://xhprof.io/
I can see it now, the /html directory full of code snippets, and an incredibly convoluted htaccess file that conditionally assembles the various pages for a site. :)
Quick! Turn it into a framework!
I’ve used to use this technique, but dropped it for a while now.
It appears very useful at first but can be dangerous actually…
One of its weakness is the impossibility to “un” prepend or “un” append according to directory or filematch directives.
How can i use the .httaccess pre-append a .php file? i have tried using—– php_value auto_prepend_file “inc.php”
Am getting this error: Fatal error: Unknown: Failed opening required ‘inc.php” (include_path=’.;D:\xampp\php\PEAR’) in Unknown on line 0
@Matthew
have you tried using full path like /var/www/site/dir/file.php?
.htaccess – is a single file for all project. And I think it’s a bad practice to prepend files, because they will prepend on all pages.
I find it hard to believe @ Pluto htaccess allows if statements.
Thanks Chris, this would be a great way to append a “copyright link” that can’t easily be found.