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 f57362c61c Only unset query vars when serving admin pages. fixes #1979
git-svn-id: http://svn.automattic.com/wordpress/trunk@3233 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2005-11-29 06:44:44 +00:00
wp-admin Regenerate page rewrite rules after creating the first page during install. 2005-11-29 02:47:31 +00:00
wp-content Better error, fixes #1934 2005-11-25 09:12:22 +00:00
wp-includes Only unset query vars when serving admin pages. fixes #1979 2005-11-29 06:44:44 +00:00
index.php Better default behaviour for theme calling 2005-02-13 20:38:28 +00:00
license.txt *** empty log message *** 2003-04-01 14:12:34 +00:00
readme.html Trailing slashes, on the URI, make me happy, make me feel fine. fixes #1742 2005-10-12 18:21:15 +00:00
wp-atom.php Break blog header up into functional chunks. Stick it all in a WP class for now. Make wp() the front door. Move template/theme loader code into template-loader.php. Clean up feed file loadup. Modularize. 2005-06-10 23:15:13 +00:00
wp-blog-header.php More user 2005-06-12 23:22:06 +00:00
wp-comments-post.php Redirect to permalink instead of referrer. Fixes #1673 2005-11-05 22:08:56 +00:00
wp-commentsrss2.php Fetch related post-meta for each comment item. (#1745) 2005-11-22 15:01:32 +00:00
wp-config-sample.php Note character restrictions, fixes #910 2005-08-03 00:46:57 +00:00
wp-feed.php USe absolute paths in require to avoid problems with wonky include paths. http://mosquito.wordpress.org/view.php?id=1169 Props: roxeteer 2005-03-29 15:05:19 +00:00
wp-links-opml.php Making our OPML compliant 2005-10-23 17:00:13 +00:00
wp-login.php Trailing slashes. Propers to Mark Jaquith. fixes #1893 2005-11-17 10:10:10 +00:00
wp-mail.php Fixes #1515 2005-11-14 11:38:15 +00:00
wp-pass.php Introducing wp_redirect(), first cut. http://mosquito.wordpress.org/view.php?id=592 Props: Toby Simmons 2005-03-13 16:36:09 +00:00
wp-rdf.php Update loop in rdf. Props Leffe. fixes #1542 2005-09-08 22:02:14 +00:00
wp-register.php Trailing slashes. Propers to Mark Jaquith. fixes #1893 2005-11-17 10:10:10 +00:00
wp-rss.php Break blog header up into functional chunks. Stick it all in a WP class for now. Make wp() the front door. Move template/theme loader code into template-loader.php. Clean up feed file loadup. Modularize. 2005-06-10 23:15:13 +00:00
wp-rss2.php Who did the goo-id? Fixes #1089 2005-11-29 00:16:04 +00:00
wp-settings.php This should fix permalinks, but may break the PHP as CGI funkiness again 2005-11-14 08:56:40 +00:00
wp-trackback.php Use mb_substr for trackback titles. Props zet. fixes #1474 2005-11-16 09:38:54 +00:00
xmlrpc.php Remove unneeded arg. 2005-11-21 08:35:05 +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>
<title>WordPress &rsaquo; ReadMe</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<style type="text/css" media="screen">
	<!--
	html {
		background: #eee;
	}
	body {
		background: #fff;
		color: #000;
		font-family: Georgia, "Times New Roman", Times, serif;
		margin-left: 25%;
		margin-right: 25%;
		padding: .2em 2em;
	}
	
	h1 {
		color: #006;
		font-size: 18px;
		font-weight: lighter;
	}
	
	h2 {
		font-size: 16px;
	}
	
	p, li, dt {
		line-height: 140%;
		padding-bottom: 2px;
	}

	ul, ol {
		padding: 5px 5px 5px 20px;
	}
	-->
	</style>
</head>
<body>
<h1 style="text-align: center"><img alt="WordPress" src="http://wordpress.org/images/wordpress.gif" /> <br />
	Version 1.5</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 id="installation">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>Launch <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 1.5:</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 amoung people who use WordPress and occasionally support topics. The above wiki page should point you in the right direction. (irc.freenode.net #wordpresss) </dd>
</dl>

<h1 id="requirements">System Recommendations</h1>
<ul>
	<li>PHP version <strong>4.1</strong> or higher</li>
	<li>MySQL version <strong>3.23.23</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_from_other_blogging_software">import from a number of systems</a>. First you need to get WordPress installed and working as described above.</p>

<h1 id="templates">XML-RPC Interface</h1>
<p>You can now post to your WordPress blog with tools like <a href="http://ecto.kung-foo.tv/">Ecto</a>, <a href="http://blogbuddy.sourceforge.net">BlogBuddy</a>, <a href="http://bloggar.com/">Bloggar</a>, <a href="http://www.ubique.ch/wapblogger/">WapBlogger</a> (post from your Wap cellphone!), <a href="http://radio.userland.com">Radio Userland</a> (which means you can use Radio's email-to-blog feature), <a href="http://www.zempt.com/">Zempt</a>, <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 dicrete. The script will <i>delete</i> emails that are successfully posted. </p>
<h1 id="notes">User Levels </h1>
<p>You may allow or disallow user registration in your <a href="wp-admin/options-general.php">General options</a>. If &quot;new users can blog&quot; is disabled you must first raise the level of a newly registered user to allow them to post. Click the plus sign next to their name on the <a href="wp-admin/users.php">Users</a> page. </p>
<h2>User Levels</h2>
<ul>
	<li>0 - New User </li>
	<li>1 - User can post, edit, and delete their own posts.</li>
	<li>5+ - Admin; can post, edit, delete other people's posts, and change the options.</li>
	<li>Any user whose level is higher than 1, can edit and delete the posts and change the level of lower users. Example: a level 2 user is not an admin, but can edit the posts of level 1 users, and up the level of a new user from 0 to 1.</li>
</ul>
<p>Usually you want to have a team of level 1 users except for you.</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>