Download version 4.5.5:
May also be accessed from a Subversion repository: http://textpattern.googlecode.com/svn/releases/4.5.5/source/
- Extract the files to your site (in the web root, or choose a subdirectory). The top-level index.php should reside in this directory, as should the /textpattern/ and the /rpc/ directories.
- Create, or establish the existence of, a working mysql database, load /textpattern/setup/index.php (or /subdir/textpattern/setup/index.php) in a browser, and follow the directions.
- Log out of the admin side first.
- Replace the three files in your main installation directory (index.php, css.php and .htaccess) and everything in your /textpattern/ and /rpc/ directories (except config.php) with the corresponding files in this distribution.
- It is recommended that you flush the browser cache to ensure old cached files are not being used in preference to any newer versions within the upgrade.
- When you log back in to the admin side, the relevant upgrade script is run automatically. Please take a look at your Diagnostics to view any errors and whether the correct version number is displayed.
Not for production environments. Unsupported.
If you would like to experience the latest Textpattern development version, please download the latest nightly build and give it a spin.
For advanced users only, and not for production environments. Unsupported.
The latest development versions of Textpattern can be accessed via a Subversion repository:
- dev (4.x, unstable): http://textpattern.googlecode.com/svn/development/4.x/
Patches can be sent in to the public developers’ mailing list.
What follows is a quick style guide, to be followed when modifying Textpattern source files to make patches for submission.
Patch style guide
- Use UNIX (LF) line feeds/endings rather than Windows (CR+LF) or Mac (CR)
- Use “Real” or actual tabs, rather than spaces
- When naming your patch file, make the name descriptive, and include the current revision number. e.g. fix_category_bug_r1375.patch
- Create a new email. Describe what your patch is for. Attach it, if possible, to your email. If you’re unable to do so, upload it somewhere where it can be downloaded, and include a full url to the file.
- Send the patch to the developers mailing list.