WordPress, Git-ified. This repository is just a mirror of the WordPress subversion repository. Please do not send pull requests. Submit pull requests to https://github.com/WordPress/wordpress-develop and patches to https://core.trac.wordpress.org/ instead.
Go to file
ryan e1d48f65ce Set the cap appropriate to the post type. fixes #10807 see #10605
git-svn-id: http://svn.automattic.com/wordpress/trunk@11960 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2009-09-22 22:57:01 +00:00
wp-admin Eliminate the redundant and confusing comment threading depth of 1. Threading starts at 2 now. fixes #10829 2009-09-22 06:00:46 +00:00
wp-content Define in the default theme. Fixes #10682 props Viper007Bond. 2009-08-27 21:27:45 +00:00
wp-includes Set the cap appropriate to the post type. fixes #10807 see #10605 2009-09-22 22:57:01 +00:00
index.php File file level phpdoc from jacobsantos. see #7037 2008-05-25 20:33:13 +00:00
license.txt Updating FSF address at their request. 2008-12-06 07:47:04 +00:00
readme.html Update the readme in trunk early for once. 2009-07-08 07:08:36 +00:00
wp-app.php Remove trailing whitespace 2009-09-14 14:03:32 +00:00
wp-atom.php Redirect ancient wp-*.php feed files. fixes #4604 2008-10-14 06:22:52 +00:00
wp-blog-header.php File file level phpdoc from jacobsantos. see #7037 2008-05-25 15:50:15 +00:00
wp-comments-post.php Deprecate sanitize_url() and clean_url() in favor of esc_url_raw() and esc_url() 2009-05-18 16:00:33 +00:00
wp-commentsrss2.php Redirect ancient wp-*.php feed files. fixes #4604 2008-10-14 06:22:52 +00:00
wp-config-sample.php Improve the Grammar. Fixes #9181 props Viper007Bond. 2009-02-28 09:55:07 +00:00
wp-cron.php Increase timeout on cron-based requests when checking for upgrades, props dd32, fixes #10349 2009-08-16 04:59:38 +00:00
wp-feed.php Redirect ancient wp-*.php feed files. fixes #4604 2008-10-14 06:22:52 +00:00
wp-links-opml.php _a(), _ea(), _xa(), attr() are now esc_attr__(), esc_attr_e(), esc_attr_x(), esc_attr() -- still short, but less cryptic. see #9650 2009-05-05 19:43:53 +00:00
wp-load.php Pass text direction to wp_die(). Allow locales to set text direction in local packages. Props nbachiyski. fixes #6132 2009-05-20 16:32:22 +00:00
wp-login.php Remove trailing whitespace 2009-09-14 14:03:32 +00:00
wp-mail.php Make the action name for post-by-email takeover actually unique so the plugins are not triggered every time WP tries to send an email! 2009-09-18 20:43:05 +00:00
wp-pass.php Grammar fix. Props Denis-de-Bernardy. fixes #9601 2009-04-20 21:50:29 +00:00
wp-rdf.php Redirect ancient wp-*.php feed files. fixes #4604 2008-10-14 06:22:52 +00:00
wp-register.php File file level phpdoc from jacobsantos. see #7037 2008-05-25 15:50:15 +00:00
wp-rss.php Redirect ancient wp-*.php feed files. fixes #4604 2008-10-14 06:22:52 +00:00
wp-rss2.php Redirect ancient wp-*.php feed files. fixes #4604 2008-10-14 06:22:52 +00:00
wp-settings.php First pass commentmeta implementation. See #2659 props scribu. 2009-09-17 20:17:33 +00:00
wp-trackback.php File file level phpdoc from jacobsantos. see #7037 2008-05-25 15:50:15 +00:00
xmlrpc.php Don't run content_save_pre filter twice for XMLRPC posts. Props redsweater. fixes #10802 2009-09-17 16:59:33 +00:00

readme.html

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
	<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
	<title>WordPress &rsaquo; ReadMe</title>
	<link rel="stylesheet" href="wp-admin/css/install.css" type="text/css" />
</head>
<body>
<h1 id="logo" style="text-align: center">
	<img alt="WordPress" src="wp-admin/images/wordpress-logo.png" />
	<br /> Version 2.9
</h1>
<p style="text-align: center">Semantic Personal Publishing Platform</p>

<h1>First Things First</h1>
<p>Welcome. WordPress is a very special project to me. Every developer and contributor adds something unique to the mix, and together we create something beautiful that I'm proud to be a part of. Thousands of hours have gone into WordPress, and we're dedicated to making it better every day. Thank you for making it part of your world.</p>
<p style="text-align: right;">&#8212; Matt Mullenweg</p>

<h1>Installation: Famous 5-minute install</h1>
<ol>
	<li>Unzip the package in an empty directory.</li>
	<li>Open up <code>wp-config-sample.php</code> with a text editor like WordPad or similar and fill in your database connection details.</li>
	<li>Save the file as <code>wp-config.php</code></li>
	<li>Upload everything.</li>
	<li>Open <span class="file"><a href="wp-admin/install.php">/wp-admin/install.php</a></span> in your browser. This should setup the tables needed for your blog. If there is an error, double check your <span class="file">wp-config.php</span> file, and try again. If it fails again, please go to the <a href="http://wordpress.org/support/">support forums</a> with as much data as you can gather.</li>
	<li><strong>Note the password given to you.</strong></li>
	<li> The install script should then send you to the <a href="wp-login.php">login page</a>. Sign in with the username <code>admin</code> and the password generated during the installation. You can then click on 'Profile' to change the password.</li>
</ol>

<h1>Upgrading</h1>
<p>Before you upgrade anything, make sure you have backup copies of any files you may have modified such as <code>index.php</code>.</p>
<h2>Upgrading from any previous WordPress to 2.9:</h2>
<ol>
	<li>Delete your old WP files, saving ones you've modified.</li>
	<li>Upload the new files.</li>
	<li>Point your browser to <span class="file"><a href="wp-admin/upgrade.php">/wp-admin/upgrade.php</a>.</span></li>
	<li>You wanted more, perhaps? That's it!</li>
</ol>
<h2>Template Changes</h2>
<p>If you have customized your templates you will probably have to make some changes to them. If you're converting your 1.2 or earlier templates, <a href="http://codex.wordpress.org/Upgrade_1.2_to_1.5">we've created a special guide for you</a>. </p>

<h1>Online Resources</h1>
<p>If you have any questions that aren't addressed in this document, please take advantage of WordPress' numerous online resources:</p>
<dl>
	<dt><a href="http://codex.wordpress.org/">The WordPress Codex </a></dt>
		<dd>The Codex is the encyclopedia of all things WordPress. It is the most comprehensive source of information for WordPress available.</dd>
	<dt><a href="http://wordpress.org/development/">The Development Blog</a></dt>
		<dd>This is where you'll find the latest updates and news related to WordPress. Bookmark and check often.</dd>
	<dt><a href="http://planet.wordpress.org/">WordPress Planet </a></dt>
		<dd>The WordPress Planet is a news aggregator that brings together posts from WordPress blogs around the web.</dd>
	<dt><a href="http://wordpress.org/support/">WordPress Support Forums</a></dt>
		<dd>If you've looked everywhere and still can't find an answer, the support forums are very active and have a large community ready to help. To help them help you be sure to use a descriptive thread title and describe your question in as much detail as possible.</dd>
	<dt><a href="http://codex.wordpress.org/IRC">WordPress IRC Channel</a></dt>
		<dd>Finally, there is an online chat channel that is used for discussion among people who use WordPress and occasionally support topics. The above wiki page should point you in the right direction. (<a href="irc://irc.freenode.net/wordpress">irc.freenode.net #wordpress</a>)</dd>
</dl>

<h1>System Recommendations</h1>
<ul>
	<li>PHP version <strong>4.3</strong> or higher.</li>
	<li>MySQL version <strong>4.0</strong> or higher.</li>
	<li>... and a link to <a href="http://wordpress.org/">http://wordpress.org</a> on your site.</li>
</ul>
<p>WordPress is the official continuation of <a href="http://cafelog.com/">b2/caf&eacute;log</a>, which came from Michel V. The work has been continued by the <a href="http://wordpress.org/about/">WordPress developers</a>. If you would like to support WordPress, please consider <a href="http://wordpress.org/donate/">donating</a>.</p>

<h1>Upgrading from another system</h1>
<p>WordPress can <a href="http://codex.wordpress.org/Importing_Content">import from a number of systems</a>. First you need to get WordPress installed and working as described above.</p>

<h1>XML-RPC and Atom Interface</h1>
<p>You can now post to your WordPress blog with tools like <a href="http://windowslivewriter.spaces.live.com/">Windows Live Writer</a>, <a href="http://ecto.kung-foo.tv/">Ecto</a>, <a href="http://bloggar.com/">Bloggar</a>, <a href="http://radio.userland.com">Radio Userland</a> (which means you can use Radio's email-to-blog feature), <a href="http://www.newzcrawler.com/">NewzCrawler</a>, and other tools that support the Blogging APIs! :) You can read more about <a href="http://codex.wordpress.org/XML-RPC_Support">XML-RPC support on the Codex</a>.</p>

<h1>Post via Email</h1>
<p>You can post from an email client! To set this up go to your &quot;Writing&quot; options screen and fill in the connection details for your secret POP3 account. Then you need to set up <code>wp-mail.php</code> to execute periodically to check the mailbox for new posts. You can do it with Cron-jobs, or if your host doesn't support it you can look into the various website-monitoring services, and make them check your <code>wp-mail.php</code> URL.</p>
<p>Posting is easy: Any email sent to the address you specify will be posted, with the subject as the title. It is best to keep the address discrete. The script will <em>delete</em> emails that are successfully posted.</p>

<h1>User Roles</h1>
<p>We've eliminated user levels in order to make way for the much more flexible roles system introduced in 2.0. You can <a href="http://codex.wordpress.org/Roles_and_Capabilities">read more about Roles and Capabilities on the Codex</a>.</p>

<h1> Final notes</h1>
<ul>
	<li>If you have any suggestions, ideas, comments, or if you (gasp!) found a bug, join us in the <a href="http://wordpress.org/support/">Support Forums</a>.</li>
	<li>WordPress now has a robust plugin API that makes extending the code easy. If you are a developer interested in utilizing this see the <a href="http://codex.wordpress.org/Plugin_API">plugin documentation in the Codex</a>. In most all cases you shouldn't modify any of the core code.</li>
</ul>

<h1>Share the Love</h1>
<p>WordPress has no multi-million dollar marketing campaign or celebrity sponsors, but we do have something even better&#8212;you. If you enjoy WordPress please consider telling a friend, setting it up for someone less knowledgable than yourself, or writing the author of a media article that overlooks us.</p>

<h1>Copyright</h1>
<p>WordPress is released under the <abbr title="GNU Public License">GPL</abbr> (see <a href="license.txt">license.txt</a>).</p>

</body>
</html>