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 6f27182cf1 Introduce sanitize_key().
git-svn-id: http://svn.automattic.com/wordpress/trunk@13718 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2010-03-16 19:19:32 +00:00
wp-admin Introduce taxonomies_allowed_in_menus and post_types_allowed_in_menus. Show only pages and categories by default. see #11817 2010-03-16 17:22:24 +00:00
wp-content Menus rework. Props ptahdunbar. see #11817 2010-03-15 16:26:46 +00:00
wp-includes Introduce sanitize_key(). 2010-03-16 19:19:32 +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 Check in install.css for [13516]. Bump version, include version in readme.html. see #10835 2010-02-28 22:42:36 +00:00
wp-activate.php more multisite UX rebranding, See #11644 2010-02-24 20:45:02 +00:00
wp-ajax.php Opt out of content sniffing for front end AJAX endpoint as well. 2010-03-10 08:08:27 +00:00
wp-app.php Use is_ssl() in place of manual SERVER['HTTPS'] == 'on' checks. fixes #11885 2010-02-26 06:21:47 +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 Deny commenting on any post with a non-public status. see #9674 2010-02-18 20:08:35 +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 Add initial WP_DEBUG define to wp-config-sample.php and suggest plugin/theme developers use it. Fixes #12236 2010-02-17 20:36:00 +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 Add the generator element in feeds through the {rss2|atom|rdf|rss|opml}_head hooks. Fixes #6947 props sivel. 2010-02-13 16:45:16 +00:00
wp-load.php Display PHP Start-up Errors/Warnings. Props Denis-de-Bernardy. Fixes #12395. 2010-02-28 12:19:09 +00:00
wp-login.php Set up the password nag for newly registered users. Fixes #12143 2010-02-28 07:15:15 +00:00
wp-mail.php Switch from POST_BY_EMAIL constant to enable post-by-email when multisite to a filter. See #12381. 2010-02-25 22:06:10 +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-rss2.php Redirect ancient wp-*.php feed files. fixes #4604 2008-10-14 06:22:52 +00:00
wp-rss.php Redirect ancient wp-*.php feed files. fixes #4604 2008-10-14 06:22:52 +00:00
wp-settings.php Add a front end Ajax handler. Props Denis-de-Bernardy. See #12400 2010-03-01 11:49:50 +00:00
wp-signup.php add actions before and after signup form, see #12199 2010-03-09 16:27:02 +00:00
wp-trackback.php Spelling and grammar fun. Fixes #11875 props cnorris23 2010-02-24 20:13:23 +00:00
xmlrpc.php Don't use private wpdb vars. See #11644 2010-02-24 00:18:18 +00:00

<!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 &#8250; ReadMe</title>
	<link rel="stylesheet" href="wp-admin/css/install.css?ver=20100228" type="text/css" />
</head>
<body>
<h1 id="logo">
	<a href="http://wordpress.org/"><img alt="WordPress" src="wp-admin/images/wordpress-logo.png" width="250" height="68" /></a>
	<br /> Version 3.0
</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 and upload everything.</li>
	<li>Open <span class="file"><a href="wp-admin/install.php">wp-admin/install.php</a></span> in your browser. It will take you through the process to set up a <code>wp-config.php</code> file with your database connection details.
		<ol>
			<li>If for some reason this doesn't work, don't worry. It doesn't work on all web hosts. 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> and upload it.</li>
			<li>Open <span class="file"><a href="wp-admin/install.php">wp-admin/install.php</a></span> in your browser.</li>
		</ol>
	</li>
	<li>Once the configuration file is set up, the installer will set up the tables needed for your blog. If there is an error, double check your <code>wp-config.php</code> file, and try again. If it fails again, please go to the <a href="http://wordpress.org/support/" title="WordPress support">support forums</a> with as much data as you can gather.</li>
	<li><strong>If you did not enter a password, note the password given to you.</strong> If you did not provide a username, it will be <code>admin</code>.</li>
	<li>The installer should then send you to the <a href="wp-login.php">login page</a>. Sign in with the username and password you chose during the installation. If a password was generated for you, you can then click on 'Profile' to change the password.</li>
</ol>

<h1>Upgrading</h1>
<h2>Using the Automatic Upgrader</h2>
<p>If you are upgrading from version 2.7 or higher, you can use the automatic upgrader:</p>
<ol>
	<li>Open the <span class="file"><a href="wp-admin/update-core.php">wp-admin/update-core.php</a></span> in your browser and follow the instructions.</li>
	<li>You wanted more, perhaps? That's it!</li>
</ol>

<h2>Upgrading Manually</h2>
<ol>
	<li>Before you upgrade anything, make sure you have backup copies of any files you may have modified such as <code>index.php</code>.</li>
	<li>Delete your old WordPress 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>
</ol>

<h2>Theme Template Changes</h2>
<p>If you have customized your theme templates, you may have to make some changes across major versions.</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. Recent WordPress development news appears in your administrative dashboard by default.</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 <abbr title="Internet Relay Chat">IRC</abbr> Channel</a></dt>
		<dd>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 Requirements</h1>
<ul>
	<li><a href="http://php.net/">PHP</a> version <strong>4.3</strong> or higher.</li>
	<li><a href="http://www.mysql.com/">MySQL</a> version <strong>4.1.2</strong> or higher.</li>
</ul>

<h2>System Recommendations</h2>
<ul>
	<li>The <a href="http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html">mod_rewrite</a> Apache module.</li>
	<li>A link to <a href="http://wordpress.org/">http://wordpress.org</a> on your site.</li>
</ul>

<h1>Migrating from other systems</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, before using <a href="wp-admin/import.php" title="Import to WordPress">our import tools</a>.</p>

<h1><abbr title="eXtensible Markup Language">XML</abbr>-<abbr title="Remote Procedure Call">RPC</abbr> and Atom Interface</h1>
<p>You can post to your WordPress blog with tools like <a href="http://download.live.com/writer">Windows Live Writer</a>, <a href="http://illuminex.com/ecto/">Ecto</a>, <a href="http://bloggar.com/">w.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 <abbr title="application programming interface">API</abbr>s! :) You can read more about <a href="http://codex.wordpress.org/XML-RPC_Support"><abbr>XML</abbr>-<abbr>RPC</abbr> 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 <abbr title="Post Office Protocol version 3">POP3</abbr> 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 <a href="http://en.wikipedia.org/wiki/Cron">cron</a>-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> <abbr title="Uniform Resource Locator">URL</abbr>.</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 introduced a very flexible roles system in version 2.0, eliminating user levels. You can <a href="http://codex.wordpress.org/Roles_and_Capabilities" title="WordPress 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, or 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 <abbr title="application programming interface">API</abbr> 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" title="WordPress 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>

<p>WordPress is the official continuation of <a href="http://cafelog.com/">b2/caf&#233;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/" title="Donate to WordPress">donating</a>.</p>

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


</body>
</html>