Here’s a lengthy article on SQLite! That’s something I really need to look at!
Bah.. link is dead. Grrr.
Here’s a lengthy article on SQLite! That’s something I really need to look at!
Bah.. link is dead. Grrr.
To display “static” pages here I use the Apache “ForceType” directive so that all requests to /pages/something get processed by a php file called “pages”. Unfortunately that doesn’t work as easily when PHP is running as a CGI.
I found a possible solution in this Textpattern forum thread. Not sure if you can put “ScriptAlias” into a .htaccess file. I just checked and no, you can’t. That limits the usefulness of this solution dramatically!
Here’s how to use PATHINFO to create search engine friendly URLs. Again, it uses the ForceType idea.
Looks like it’s worth perceivering with mod_rewrite after all!
Here’s a nice way of adding a calendar graphic to your website – use the background= attribute of html to fool the eye!
Savant is another PHP templating engine. Here’s the getting started guide, with a nice Model-View example.
These guidelines are probably worth a read no matter what your favourite language is. Many are PHP specific but I’m going to digest some of the more appetizing ones. (you can tell it’s almost lunchtime can’t you?)
Aaron doesn’t explicitly list the dangers but I can guess that they include overwriting db files. I haven’t looked at SQLite yet however, it’s on the TODO list! 🙂
OK, I read the comments, it’s no more dangerous than having text files lying around, although as the file has to be writeable by the webserver that guarantees certain responsibilites when using them!
Via delicious this morning I have two titbits for your consumption!
Movable Type Ported to PHP – Apparently they’ve done what appears to be a nearly complete port of MT from Perl (bless it) to PHP. This port appears to include support for all current MT tags, it relies on Justin Vincent’s ezSQL DB library and Smarty templates, and even supports a plug-in API.
Why PHP still stinks – from a Perl coder’s perspective. 😉
This technique is an old one. Feed your content through the PHP output buffer using the gzip handler, then at the end flush it out to the browser.
Even if the text doesn’t compress well, just using the output buffer results in slightly less network traffic as the data is sent in one big blob. I have to investigate if the HTTP headers are affected yet but it seems to be working fine.
Zend in the clowns? is a lengthly article about the history of PHP. *phew*
It’s official and everyone and their mum has the news. I’ll let SitePoint PHP Blog provide the summary!