Scenario one. I need a "todo" list page for our web site which I, and the rest of our team, can view and update quickly and easily.

Scenario two. Dave wants to provide his local cricket club's website with pages that the committee can update without them having to be trained / skilled in HTML, with each of the pages having the same look and feel, and without the risk of something silly being inserted into the page that will cause a major security breach.

Dave was with me for last week's PHP Course and we wrote a single page wiki demonstration ... which I have just modified and installed onto our live web server as a staff usage page for our team.

When any of our team visits the page, this is the sort of thing we'll see - there are a few standard headers and timestamps, and a picture which can be changed by anyone who edits the page.


Select the edit button, and our staff members are offered a text edit window, and Javascript buttons for bold, italic, underline, colour changes, links, etc. These add in bulletin board type codes such as [b]through[/b] for bold.


With the particular case of our internal "todo" list, the display that's shown to public visitors isn't the one that I started with, but rather it's what you see here. We have chosen to display the picture, but only a standard piece of text that suggests you should be logged in.


The Wiki demonstration code - it's only about 6k bytes - is [here] and there's a sample template [here]. That's even shorter. You'll need to rewrite URLs so that all your page names point to a single script if you're going to be using multiple pages within the system - we have a sample .htaccess file [here].

If you're already knowledgeable in PHP, you should find the script quite easy, but if you'ld like some help with this and many similar things, we cover it on our PHP Techniques Workshop.

(written 2010-02-14, updated 2010-03-03)

 H310 - PHP - Putting it all together
  [468] Stand alone PHP programs - (2005-10-18)
  [687] Presentation, Business and Persistence layers in Perl and PHP - (2006-04-17)
  [1716] Larger applications in PHP - (2008-07-22)
  [1754] Upgrade from PHP 4 to PHP 5 - the TRY issue - (2008-08-15)
  [1794] Refactoring - a PHP demo becomes a production page - (2008-09-12)
  [1840] Validating Credit Card Numbers - (2008-10-14)
  [1962] Index Card System for Game Characters in PHP - (2008-12-27)
  [2275] Debugging multipage (session based) PHP applications - (2009-07-09)
  [2931] Syncronise - software, trains, and buses. Please! - (2010-08-22)
  [3454] Your PHP website - how to factor and refactor to reduce growing pains - (2011-09-24)

Back to London to and from Melksham by public transport

Previous and next or Horse's mouth home

Forward to Linux - useful tips including history and file name completion

su or su - ... what is the difference?
Finding what has changed - Linux / Unix
Courses - Melksham and elsewhere - until the end of April
Linux - useful tips including history and file name completion
A PHP example that lets your users edit content without HTML knowledge
London to and from Melksham by public transport
Why do I teach niche skills rather than mainstream?
Shipping a test harness with your class in PHP
How to show a large result set page by page in PHP
Static variables and ampersands in PHP