WordPress.org

Make WordPress Core

Changeset 1341 for trunk/readme.html


Ignore:
Timestamp:
05/22/04 10:19:45 (10 years ago)
Author:
saxmatt
Message:

New readme. Smaller! More readable! Correct!

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/readme.html

    r1149 r1341  
    1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 
     1<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> 
    22<html xmlns="http://www.w3.org/1999/xhtml"> 
    33<head> 
    4 <title>WordPress&#8212;ReadMe</title> 
     4<title>WordPress&rsaquo;ReadMe</title> 
    55<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> 
    66<style type="text/css" media="screen"> 
    77    <!-- 
     8    html { 
     9        background: #eee; 
     10    } 
    811    body { 
    912        background: #fff; 
     
    1215        margin-left: 25%; 
    1316        margin-right: 25%; 
     17        padding: .2em 2em; 
    1418    } 
    1519     
     
    2024    } 
    2125     
    22      
    2326    h2 { 
    2427        font-size: 16px; 
    2528    } 
    2629     
    27     .tag { 
    28         background: #FFFF99 
    29         color: #000; 
    30         } 
    31  
    32  
    33      
    34     p, li { 
     30    p, li, dt { 
    3531        line-height: 140%; 
    3632        padding-bottom: 2px; 
    3733    } 
    3834 
    39     .file { 
    40         background: #d4f5ff; 
    41         color: #000; 
    42     } 
    43      
    44     .tag { 
    45         background: #FFFF99; 
    46         color: #000; 
    47         } 
    48  
    4935    ul, ol { 
    5036        padding: 5px 5px 5px 20px; 
    51     } 
    52      
    53     .params { 
    54         border: 1px solid #ccc; 
    55         font: 12px arial,helvetica,sans-serif; 
    56         margin: 5px; 
    57         margin-left: 20px; 
    58         margin-right: 80px; 
    59         padding: 5px; 
    6037    } 
    6138    --> 
    6239    </style> 
    6340</head> 
    64 <body>  
    65 <p style="text-align: center"><img alt="WordPress" src="http://wordpress.org/images/wordpress.gif" /> <br /> 
    66 Version 1.0.1</p>  
    67 <p style="text-align: center">Weblog / News Publishing Tool</p>  
    68 <p style="text-align: center"><a href="#requirements">Requirements</a> - <a href="#installation">Installation</a> - <a href="#templates">Template(s)</a> - <a href="#usage">Query String Usage</a> - <a href="#xmlrpc">XML-RPC (Blogging APIs)</a> - <a href="#postviaemail">Post Via Email</a> - <a href="#notes">Notes</a></p>  
    69 <h1 id="requirements">Requirements:</h1>  
    70 <ul>  
    71   <li><strong>PHP4</strong> (version 4.0.6 or higher)</li>  
    72   <li><strong>MySQL</strong> (version 3.23.23 or higher)</li>  
    73   <li>... and a link to <a href="http://wordpress.org">http://wordpress.org</a> on your site.</li>  
    74 </ul>  
    75 <p>The link will help promote <a href="http://wordpress.org">WordPress</a> and is its only mean of promotion. </p>  
    76 <p>WordPress is the official continuation of <a href="http://cafelog.com/">b2</a>, which comes 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>  
    77 <p>This document is currently <em>beta</em> stage, we'll be updating it extensively as WordPress matures. There is also <a href="http://wordpress.org/docs/">online documentation</a> under development, as well as a <a href="http://wiki.wordpress.org">wiki</a>.</p>  
    78 <h1 id="installation">Installation:</h1>  
    79 <h2>New users: 5-minute install.</h2>  
    80 <ol>  
    81   <li>Unzip the package in an empty directory.</li>  
    82   <li>Upload everything. This release is designed to sit in your root folder; i.e, the folder where your WordPress-powered page will reside.</li>  
    83   <li>(Optional) If you're going to use it, the weblogs.com cache file needs to be writable by the web server. <a href="http://www.evolt.org/article/A_quick_and_dirty_chmod_Tutorial/18/541/">CHMOD 666</a> the <span class="file"><code>wp-content/link-update-cache.xml</code></span> file. </li>  
    84   <li> 
    85     <p>Point your browser to <span class="file">wp-admin/install-config.php</span>.  This will create a configuration file for your installation.  You'll need to know your database name, username, password, and host name.</p> 
    86     <p>Alternately, you may open <span class="file">wp-config-sample.php</span> in a text editor and insert your database name, username, password, and host name as indicated in the comments. (Comments are lines that start with <code>/*</code> or <code>//</code>.)  Save this file as <span class="file">wp-config.php</span>, and upload it.</p> 
    87   </li> 
    88   <li> Launch <span class="file"><a href="wp-admin/install.php">/wp-admin/install.php</a></span> in your browser. This should setup the MySQL database for your blog. <strong>Note the password given to you.</strong> 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> and make a post with all the information about the failure (error messages, etc), and your setup (the PHP and MySQL versions on your server, and the browser you were using). </li> 
    89   <li> The install script should then send you to the login page.  Sign in with the username "admin" and the password generated during the installation.  Then click on the item 'My Profile', and change the password.  The login page may also be accessed by going to <span class="file"><a href="wp-login.php">wp-login.php</a></span>.</li>  
    90 </ol>  
    91 <h2>Some notes:</h2>  
    92 <ul>  
    93   <li>Whenever you want to post something, just open a browser and go to <span class="file"><a href="wp-login.php">wp-login.php</a></span> to log in and post.</li>  
    94   <li>You can also use a bookmarklet and/or a sidebar (IE5+/NS6+) to post.</li>  
    95   <li> You can also post through the Blogger, MetaWeblog, and MovableType APIs, <a href="#xmlrpc">click here</a> for more info.</li>  
    96   <li> By default, your site's blog is located at <span class="file">index.php</span>, which is an elaborate .CSS-based template.  There is a non-.CSS template you can also use, called <span class="file">wp.php</span>. You can rename either of these files as any other name you fancy (provided it bears the php extension or is interpreted as a php file by your server).</li>   
    97 </ul>  
    98  
    99 <h2>Preface for all upgrades:</h2> 
    100  <ul><li><strong>Back up</strong> your database before you do anything. </li>  
    101   <li>If you haven't already, we strongly suggest that you <strong>BACK UP</strong> your database.</li> 
    102   <li>Have you <strong>BACKED UP</strong> your database? Yeah? GREAT!</li> 
    103   <li>If you don't know how to do this, <a href="http://wordpress.org/support/10/1384">this script</a> may help.</li> 
     41<body> 
     42<h1 style="text-align: center"><img alt="WordPress" src="http://wordpress.org/images/wordpress.gif" /> <br /> 
     43    Version 1.2</h1> 
     44<p style="text-align: center"> Semantic Personal Publishing Platform </p> 
     45<h1>First Things First</h1> 
     46<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> 
     47<p style="text-align: right;">&#8212; Matt Mullenweg </p> 
     48<h1>Online Resources</h1> 
     49<p>If you have any questions that aren't addressed in this document, please take advantage of WordPress' numerous online resources:</p> 
     50<dl> 
     51    <dt><a href="http://wiki.wordpress.org/">The WordPress Wiki</a></dt> 
     52    <dd>A wiki is like a web page than anyone can contribute to, and the WordPress wiki documentation has grown rich from the many who have contributed to it. It is usually up-to-date and well-hyperlinked. The only downside is it can be hard to find your way around your first time. Use the search box at the top.</dd> 
     53    <dt><a href="http://wordpress.org/docs/">The official documentation</a></dt> 
     54    <dd>The documentation on wordpress.org represents the official resources we've made available. Beyond reference, this includes tutorials and guides for doing different things with WordPress. As I write this, it is a little sparse, but we're doing our best to enrich this resource so by the time you read this sentence the docs may be bursting with information. </dd> 
     55    <dt><a href="http://wordpress.org/development/">The Development Blog</a></dt> 
     56    <dd>This is where you'll find the latest updates and news related to WordPress. Bookmark and check often. </dd> 
     57    <dt><a href="http://faq.wordpress.net/">Frequently Asked Questions Blog </a></dt> 
     58    <dd>In addition to the FAQ on the wiki and the main website, there is a new FAQ blog that several members of the documentation team are updating. The FAQ itself is run with WordPress. </dd> 
     59    <dt><a href="http://wordpress.org/support/">WordPress Support Forums</a></dt> 
     60    <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> 
     61    <dt><a href="http://wiki.wordpress.org/index.php/IRC">WordPress IRC Channel</a></dt> 
     62    <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> 
     63</dl> 
     64<h1 id="requirements">System Recomendations </h1> 
     65<ul> 
     66    <li>PHP version <strong>4.1</strong> or higher</li> 
     67    <li>MySQL version <strong>3.23.23</strong> or higher</li> 
     68    <li>... and a link to <a href="http://wordpress.org">http://wordpress.org</a> on your site.</li> 
    10469</ul> 
    105  
    106 <h2>Upgrading from any previous WordPress to v1.0.1:</h2> 
     70<p>The Apache <code>mod_rewrite</code> is required for some optional functionality. </p> 
     71<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> 
     72<h1 id="installation">Installation: Famous 5-minute install</h1> 
     73<ol> 
     74    <li>Unzip the package in an empty directory</li> 
     75    <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> 
     76    <li>Save the file as <code>wp-config.php</code> </li> 
     77    <li>Upload everything.</li> 
     78    <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> 
     79    <li><strong>Note the password given to you.</strong></li> 
     80    <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> 
     81</ol> 
     82<h1>Upgrading</h1> 
     83<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> 
     84<h2>Upgrading from any previous WordPress to 1.2:</h2> 
     85<ol> 
     86    <li>Upload the new files, and be careful not to overwrite anything important</li> 
     87    <li>Point your browser to <span class="file"><a href="wp-admin/upgrade.php">/wp-admin/upgrade.php</a></span></li> 
     88    <li>You wanted more, perhaps? That's it!</li> 
     89</ol> 
     90<p>If you are coming from 1.0 or greater, your existing templates should work perfectly. If you are coming from a version earlier than 1.0 you will need to modify your templates slightly. Use the default <code>index.php</code> as your guide. </p> 
     91<h1>Upgrading from another system</h1> 
     92<p>WordPress can import from a number of systems. First you need to get WordPress installed and working as described above, then you can run one of the following import scripts:</p> 
    10793<ul> 
    108     <li><strong>Backup your database.</strong>  Yes, you.  Right now.</li> 
    109     <li>Point your browser to <span class="file"><a href="wp-admin/upgrade.php">/wp-admin/upgrade.php</a>.</span></li> 
    110     <li>You wanted more, perhaps?  That's it!</li> 
     94    <li> <a href="wp-admin/import-mt.php"> Import Movable Type </a></li> 
     95    <li><a href="wp-admin/import-rss.php">Import RSS 2.0</a></li> 
     96    <li><a href="wp-admin/import-blogger.php">Import Blogger</a></li> 
     97    <li><a href="wp-admin/import-b2.php">Import b2</a></li> 
     98    <li><a href="wp-admin/import-livejournal.php">Import LiveJournal</a></li> 
     99    <li><a href="wp-admin/import-textpattern.php">Import Textpattern</a></li> 
     100    <li><a href="wp-admin/import-greymatter.php">Import Greymatter </a></li> 
    111101</ul> 
    112 <h2>Note on upgrading to v1.0.1:</h2> 
    113 <ul> 
    114 <li>It is <strong>strongly</strong> recommended that you use the new <span class="file"> index.php</span> for your templates, rather than simply upgrading your old one.  Sure, it'll take a little time, but you'll be much happier with the results when you do!</li> 
    115  
    116 <h2>Upgrading from b2 v0.6.1/v0.6.2.2 to WordPress v1.0.1:</h2>  
    117 <ul>  
    118   <li><strong>Back up</strong> your database before you do anything. Yes, you. Right now.</li>  
    119 <li>You <em>must</em> configure <span class="file"><code>wp-config.php</code></span> as indicated in the "5-minute install" section.</li> 
    120   <li>All you <em>really</em> have to do is replace all the files with newer versions and run <span class="file">wp-admin/upgrade.php</span> and you should be ready to go.</li> 
    121   <li>There is also an import script at <span class="file">wp-admin/import-b2.php</span>.</li> 
    122   <li>If you're using an older version of b2, it's probably a good idea to upgrade to at least .6.1 before making the leap to WordPress.</li>  
    123   <li>The templates are better and structured slightly differently, so it might be worth it to start from scratch and work back to your design.</li>  
    124   <li>WordPress issues should be discussed in our <a href="http://wordpress.org/support/">support forums</a>.</li>  
    125 </ul>  
    126  
    127 <h2>Upgrading to WordPress v1.0.1 from Movable Type, Textpattern, GreyMatter, & Blogger</h2> 
    128 <ul> 
    129 <li>Did we mention <strong>BACKING UP</strong> your database first?</li> 
    130 <li>Each of these tools has an import script available.  They are all located in the wp-admin directory, and must first be configured with your database information before they are executed.   
    131 <li>Detailed importing instructions are given during the execution of the import script. 
    132 <li>Textpattern:  run <span class="file"><a href="wp-admin/import-textpattern.php">wp-admin/import-textpattern.php</a></span>.</li> 
    133 <li>GreyMatter: run <span class="file"><a href="wp-admin/import-greymatter.php">wp-admin/import-greymatter.php</a></span>.</li> 
    134 <li>Blogger: run <span class="file"><a href="wp-admin/import-blogger.php">wp-admin/import-blogger.php</a></span>.</li> 
    135 <li>Movable Type: run <a href="wp-admin/import-mt.php" class="file">wp-admin/import-mt.php</a>. </li> 
    136 </ul> 
    137  
    138 <h1 id="templates">Templates:</h1> 
    139 <p>For information about WordPress templates, please see our <a href="http://wordpress.org/docs/template/">online documentation on them</a>. </p> 
    140 <h2>First notes:</h2>  
    141 <h1 id="usage">Query String Usage:</h1>  
    142 <p>WordPress relies a lot on the query string. These variables passed with the URL (note: to pass variables in the querystring, preceed the first variable name with a '?' question mark and every other variables with a '&amp;' sign.)</p> 
    143 <p>Most of the time you won't have to do anything about it, but if you want to know how it works, it's here:</p> 
    144 <p>How to use the query string:</p>  
     102<h1 id="templates">Templates</h1> 
     103<p>The template tags are too numerous and flexible to adequetely document here, so please see our <a href="http://wordpress.org/docs/template/">online documentation</a>. </p> 
     104<h1>Query String Usage</h1> 
     105<p>WordPress can be manipulated quite a bit through the query string. To pass variables in the querystring, proceed the first variable name with a '?' question mark and every other variables with a '&amp;' sign. You may never use this, but it is useful to know. </p> 
    145106<p>index.php<strong>?m=200107</strong> will display the month of July 2001.</p> 
    146107<p>index.php<strong>?m=20010701</strong> will display all posts from July 1st, 2001.</p> 
    147108<p>index.php<strong>?w=20</strong> will display the posts from the 20th week of the year, where January 1st is in the first week (according to PHP).</p> 
    148109<p>index.php<strong>?p=50</strong> will display the post labeled #50 in the database.</p> 
    149 <p>index.php<strong>?s=blue+house</strong> will display the posts that match the search request "blue house".<br /> 
    150 here is the code for a simple search box:</p> 
    151 <p><code>&lt;form name="searchform" action="&lt;?php echo $PHP_SELF ?&gt;" method="get"&gt;<br /> 
    152 &lt;input type="text" name="s" /&gt;<br /> 
    153 &lt;input type="submit" name="submit" value="search" /&gt;<br /> 
    154 &lt;/form&gt; </code></p> 
     110<p>index.php<strong>?s=blue+house</strong> will display the posts that match the search request "blue house".</p> 
    155111<p>index.php<strong>?cat=1</strong> will display all posts that belong to category #1 (1 is the default). you can add/rename/delete categories from WordPress's interface.</p> 
    156112<p>index.php<strong>?author=1</strong> will display all posts from the author #1</p> 
    157 <p>index.php<strong>?p=50&amp;c=1</strong> will display the comments and a form to add a comment below the post.<br /> 
    158   you should use this variable only with <strong>p=</strong>, example: index.php<strong>?p=50&amp;c=1</strong>.</p> 
    159113<p>index.php<strong>?p=50&amp;page=1</strong> will display the first page of post #50. this, again, should be used only with <strong>p=</strong>, for individual entries.</p> 
    160114<p>You can also mix these variables, example: index.php<strong>?m=200107&amp;s=hotdog</strong> will display the posts that match the search request "hotdog", but only in July 2001.</p> 
    161 <h1 id="xmlrpc">XML-RPC Interface:</h1>  
    162 <p>WordPress has an XMLRPC interface. Currently supported APIs are the <a href="http://www.blogger.com/developers/api/1_docs/">Blogger API</a>, <a href="http://www.xmlrpc.com/metaWeblogApi">metaWeblog API</a>, and the <a href="http://www.movabletype.org/docs/mtmanual_programmatic.html">MovableType API</a>. There are talks about a new API that would cover a lot of weblog/CMS systems in the future: when it's ready, WordPress will support it.</p>  
    163 <p> The <a href="http://www.blogger.com/developers/api/1_docs/">Blogger API</a> has been completely emulated on WordPress, with some little differences:</p>  
    164 <ul>  
    165   <li>using <em>blogger.getRecentPosts</em> with the number 'zero' returns all posts in the blog</li>  
    166   <li><em>blogger.getTemplate</em> fetches your file $blogfilename (as specified in the config), while <em>blogger.setTemplate</em> overwrites it with the edited data</li>  
    167   <li><em>blogger.getUsersBlogs</em> is a dummy function that returns '1' and $blogname, since WordPress supports only one blog as of now</li>  
    168 </ul>  
    169 <p>If you use blogger.newPost, your post is submitted without title and in category #1.</p>  
    170 <p> However, you can type &lt;title&gt;my title&lt;/title&gt; and/or &lt;category&gt;2&lt;category&gt; in the body of your post to make its title be 'my title' and its category be #2 (refer to your categories section to find out the ID numbers of the categories). b2 would then delete that extra info from the body of your post once it is posted.</p>  
    171 <p>The <a href="http://www.xmlrpc.com/metaWeblogApi">metaWeblog</a> and <a href="http://www.movabletype.org/docs/mtmanual_programmatic.html">MovableType</a> APIs are currently supported with the following exceptions:</p>  
    172 <ul>  
    173   <li>metaWeblog.newMediaObject,&nbsp; mt.getRecentPostTitles,&nbsp; and mt.getTrackbackPings are not yet implemented</li>  
    174   <li>mt.supportedTextFilters is a dummy stub function that returns an empty string</li>  
    175   <li>keywords are not supported in the MovableType API</li>  
    176 </ul>  
    177 <br />  
    178 Extended entries in the <a href="http://www.movabletype.org/docs/mtmanual_programmatic.html">MovableType API</a> are automatically converted to/from the WordPress &lt;!--more--&gt; tag.<br />  
    179 <p>You can now post to your WordPress blog with tools like <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! :)</p>  
    180 <p>Your XMLRPC server/path are as described here: if you login to WordPress on http://example.com/me/wp-login.php, then you have:</p>  
    181 <ul>  
    182   <li>server: http://example.com/ (some tools will just want the 'example.com' hostname part)</li>  
    183   <li>path: /me/xmlrpc.php</li>  
    184   <li>complete URL (just in case): http://example.com/me/xmlrpc.php</li>  
    185 </ul>  
    186 <p>There's also a b2-specific method: b2.getCategories. Request it with 3 strings: blog_ID (use '1'), username, password. The response is an array of structs with strings categoryID and categoryName.</p>  
    187 <h1 id="postviaemail">Post via Email:</h1>  
    188 <p>You can post news from an email client!<br />  
    189   But first you'll have to edit the options on the options screen, filling the appropriate values for your POP3 email account (this interface doesn't support IMAP yet, only POP3, sorry).</p>  
    190 <p> Once you have edited the options, you can make your webserver execute wp-mail.php every set amount of time (depending on your host's performance, this script can be resource intensive, so don't make it run every minute or you'll be kicked).</p>  
    191 <p>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 wp-mail.php URL.</p>  
    192 <h2> Preliminary advice:</h2>  
    193 <p> It is strongly advised to send your email as text-only (Outlook and Outlook Express default to 'html', which may cause problems), but HTML email could work (the script would strip all your html tags though...).</p>  
    194 <p>It is also advised not to use your public email address, but create a new one especially for this script. If you use your public email address and the script goes crazy posting every email on your blog and deleting all your emails, I can't take responsibility for this.</p>  
    195 <p>Make sure you delete any email sent to your blog in your 'Sent' folder too, just in case (you don't want someone to find your login and password in the 'Sent' folder).</p>  
    196 <p> The script will <i>delete</i> the emails that were used to post stuff on your weblog if it successfully posted your stuff. If it didn't manage to post, the email is not deleted.</p>  
    197 <h2>How to post:</h2>  
    198 <p>Now to post something, here's how your email should look like:</p>  
    199 <div class="params"> <b>To:</b> address@example.com <span 
    200  
    201  style="color: rgb(153, 153, 153);">(you set it in the config file)</span><br />  
    202   <b>Subject:</b> blog:the post's title <span 
    203  
    204  style="color: rgb(153, 153, 153);">(you can change 'blog:' in the config file)</span><br />  
    205   <b>Body:</b><br />  
    206   login:password <span style="color: rgb(153, 153, 153);">(example: <i>Jack:Starwars</i>)</span><br />  
    207   The content of the post, blah blah blah.<br />  
    208   More blah blah. ___ </div>  
    209 <p> Subject must start with 'blog:', or any string you set in the config file (so that the script doesn't check EVERY email in your mailbox).</p>  
    210 <p>Body's first line must always be login:password, else the script will just skip the email.</p>  
    211 <p> If you don't use '___' (or any body terminator that you set in the config file), the script will post the whole body, which is not what you want if you send email with Yahoo or Hotmail (you don't want their ads on your blog, do you ?).</p>  
    212 <h2>Special cases for mobile phone email:</h2>  
    213 <p> Some mobile phone service providers may allow you to send email with your mobile phone or PDA, but on such devices you can't always include line breaks. In such case, you have to set <i>use_phoneemail = true</i> in the options, and then here's how you write the email:</p>  
    214 <div class="params"> <b>To:</b> address@example.com<br />  
    215   <b>Subject:</b> blog:the post's title <b>:::</b><br />  
    216   <b>Body:</b><br />  
    217   login:password <b>:::</b> The content of the post, blah blah blah.___ </div>  
    218 <p>You will have to append ':::' (or whatever string you set in the config file) after the subject, and after the login:password.</p>  
    219 <p>Some mobile phone service providers may not allow you to set a subject, and they'll make the subject be the first characters of the body, in which case you would send an email like this:</p>  
    220 <div class="params"> <b>To:</b> address@example.com<br />  
    221   <b>Body:</b><br />  
    222   blog:the post's title <b>:::</b> login:password <b>:::</b> The content of the post, blah blah blah.___ </div>  
    223 <h1 id="notes">Notes:</h1>  
    224 <p>On multi-user:</p>  
    225 <p>New users can register with <span class="file">wp-register.php</span>. Then you (as an admin) click the "+" next to their name on the Team page in admin to upgrade their level to 1 or more, so they can post. If you don't want an user to post anymore, just click "-" until their level is 0.</p>  
    226 <p>Note: you can now disable users registration altogether from the config file.</p>  
    227 <p><strong>User Levels</strong>:</p>  
    228 <ul>  
    229   <li>0 - new user: can't post.</li>  
    230   <li>1 - user: can post &amp; edit/delete their own posts.</li>  
    231   <li>3 &amp; higher - admin: can post, edit/delete other people's posts, and change the options.</li>  
    232   <li>Any user whose level is higher than 1, can edit/delete the posts and change the level of users whose level is inferior. 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>  
    233 </ul>  
    234 <p>Usually, you'll want to have a team of only level 1 users except you. ;)</p>  
    235 <p><strong>Note:</strong> you can modify an option on the option screens, to enable new users to post once they've registered.</p>  
    236 <p>If you don't want users to register on your blog at all, just delete wp-register.php once you've registered your user account. </p>  
    237 <h1> Final notes:</h1>  
    238 <ul>  
    239   <li>If you've got suggestions, ideas, or comments, or if you found a bug, why not joining us in the <a href="http://wordpress.org/support/">Support Forums</a>?</li>  
    240   <li>If you can code in PHP, you'll see the structure of WordPress is flexible enough to allow for more functions and sections to be added.</li>  
    241 </ul>  
    242 <h1>Copyright notes:</h1>  
    243 <ul>  
    244   <li>Wherever third party code has been used, credit has been given in the code&#8217;s comments.</li>  
    245   <li>WordPress is released under the <acronym title="GNU Public License">GPL</acronym> (see license.txt).</li>  
    246 </ul>  
     115<h1 id="xmlrpc">XML-RPC Interface</h1> 
     116<p>WordPress has an XMLRPC interface. We currently support the <a href="http://www.blogger.com/developers/api/1_docs/">Blogger API</a>, <a href="http://www.xmlrpc.com/metaWeblogApi">metaWeblog API</a>, and the <a href="http://www.movabletype.org/docs/mtmanual_programmatic.html">MovableType API</a>. </p> 
     117<p> The <a href="http://www.blogger.com/developers/api/1_docs/">Blogger API</a> has been completely emulated on WordPress, with some little differences:</p> 
     118<ul> 
     119    <li>using <em>blogger.getRecentPosts</em> with the number 'zero' returns all posts in the blog</li> 
     120    <li><em>blogger.getTemplate</em> fetches your file $blogfilename (as specified in the config), while <em>blogger.setTemplate</em> overwrites it with the edited data</li> 
     121    <li><em>blogger.getUsersBlogs</em> is a dummy function that returns '1' and $blogname, since WordPress supports only one blog as of now</li> 
     122</ul> 
     123<p>If you use blogger.newPost, your post is submitted without title and in category #1.</p> 
     124<p> However, you can type <code>&lt;title&gt;my title&lt;/title&gt;</code> and/or <code>&lt;category&gt;2&lt;category&gt;</code> in the body of your post to make its title be 'my title' and its category be #2 (refer to your categories section to find out the ID numbers of the categories). b2 would then delete that extra info from the body of your post once it is posted.</p> 
     125<p>The <a href="http://www.xmlrpc.com/metaWeblogApi">metaWeblog</a> and <a href="http://www.movabletype.org/docs/mtmanual_programmatic.html">MovableType</a> APIs are currently supported with the following exceptions:</p> 
     126<ul> 
     127    <li>metaWeblog.newMediaObject,&nbsp; mt.getRecentPostTitles,&nbsp; and mt.getTrackbackPings are not yet implemented</li> 
     128    <li>mt.supportedTextFilters is a dummy stub function that returns an empty string</li> 
     129    <li>keywords are not supported in the MovableType API</li> 
     130</ul> 
     131<p>Extended entries in the <a href="http://www.movabletype.org/docs/mtmanual_programmatic.html">MovableType API</a> are automatically converted to/from the WordPress <code>&lt;!--more--&gt;</code> tag.</p> 
     132<p>You can now post to your WordPress blog with tools like <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! :)</p> 
     133<p>Your XMLRPC server/path are as described here: if you login to WordPress on <code>http://example.com/me/wp-login.php</code>, then you have:</p> 
     134<ul> 
     135    <li>Server: <code>http://example.com/</code> (some tools will just want the 'example.com' hostname part)</li> 
     136    <li>Path: <code>/me/xmlrpc.php</code></li> 
     137    <li>complete URL (just in case): <code>http://example.com/me/xmlrpc.php</code></li> 
     138</ul> 
     139<h1>Post via Email</h1> 
     140<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> 
     141<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> 
     142<h1 id="notes">User Levels </h1> 
     143<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> 
     144<h2>User Levels</h2> 
     145<ul> 
     146    <li>0 - New User </li> 
     147    <li>1 - User can post, edit, and delete their own posts.</li> 
     148    <li>5+ - Admin; can post, edit, delete other people's posts, and change the options.</li> 
     149    <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> 
     150</ul> 
     151<p>Usually you want to have a team of level 1 users except for you.</p> 
     152<h1> Final notes</h1> 
     153<ul> 
     154    <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> 
     155    <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 documentation in the wiki. In most all cases you shouldn't modify any of the core code.</li> 
     156</ul> 
     157<h1>Copyright</h1> 
     158<p>WordPress is released under the <acronym title="GNU Public License">GPL</acronym> (see <a href="license.txt">license.txt</a>).</p> 
    247159</body> 
    248160</html> 
Note: See TracChangeset for help on using the changeset viewer.