golem
/
twentyGOLEM
9
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Custom Wordpress theme for our Wordpress blog instance, based on the original TwentyTwelve
16,038 Commits 2 Branches 0 Tags 40 MiB
CSS 54.4%
PHP 42.6%
JavaScript 2.5%
Hack 0.5%
Go to file
nacin 9db8f895a0 Rewrite of Twenty Eleven theme-options.php. Including: 
* Full inline documentation.
 * Enqueue scripts/styles on admin_enqueue_scripts and use hook_suffix rather than GET[page]
 * Add filters to twentyeleven_color_schemes(), twentyeleven_layouts(), which necessitates adding a thumbnail URL value here, rather than generating them in the form.
 * Add a twentyeleven_default_theme_options filter.
 * Remove manual check for REQUEST[settings-updated], instead using settings_errors(), since we're using options.php.
 * Abstract out the default link color, rather than hardcoding it in certain places.
 * Use checked().
 * Rename some variables and functions for clarity.
 * Remove unnecessary functions twentyeleven_current_layout() and twentyeleven_current_color_scheme(), as we already have twentyeleven_get_theme_options().
 * Add a twentyeleven_color_schemes action to allow for enqueueing custom color schemes.
 * Add a twentyeleven_layout_classes filter, to allow filtering what gets sent back to body_class().
 * Hook into wp_enqueue_scripts rather than wp_print_styles for enqueueing the color stylesheet.
 * Rewrite the register_setting() callback to start from scratch with an empty array. Improve the link_color logic.
 * Use submit_button().
 * Use esc_attr() rather than esc_attr_e() for non-translations.

TODO:
 * Implement settings sections/fields logic to allow extension of the options page.
 * Consider re-doing this in a class. It'll be cleaner.
 * Store a DB version so we can do an add_option(), rather than calling get_option() with defaults.

see #17198.



git-svn-id: http://svn.automattic.com/wordpress/trunk@17733 1a063a9b-81f0-0310-95a4-ce76da25c4cd
 		2011-04-28 08:06:57 +00:00
wp-admin Only show the sticky posts checkbox when edit_others_posts. Doesn't work without it. props solarissmoke, linuxologos, fixes #16947. 2011-04-27 11:27:08 +00:00
wp-content Rewrite of Twenty Eleven theme-options.php. Including: 2011-04-28 08:06:57 +00:00
wp-includes Add Background and Header to Admin Bar Appearance Menu. fixes #17263 2011-04-27 22:06:01 +00:00
index.php File file level phpdoc from jacobsantos. see #7037 2008-05-25 20:33:13 +00:00
license.txt Also mention compressed scripts 2011-02-22 22:36:17 +00:00
readme.html Bump readme system requirements. props duck_, see #16917. 2011-03-25 21:21:14 +00:00
wp-activate.php Use static strings and respect coding standards in wp-activate.php. Fixes #17158 props niallkennedy. 2011-04-17 21:31:38 +00:00
wp-app.php s/occured/occurred/. props aldenta, fixes #15653. 2010-12-02 23:30:21 +00:00
wp-atom.php Always exit after wp_redirect. props filosofo, fixes #15518. 2010-12-09 18:02:54 +00:00
wp-blog-header.php Revert debug 2010-11-20 21:44:11 +00:00
wp-comments-post.php Always exit after wp_redirect. props filosofo, fixes #15518. 2010-12-09 18:02:54 +00:00
wp-commentsrss2.php Always exit after wp_redirect. props filosofo, fixes #15518. 2010-12-09 18:02:54 +00:00
wp-config-sample.php Apply the missing bits of the patch. Fixes #13891 props TobiasBg and zeo 2010-11-01 14:45:11 +00:00
wp-cron.php More pedantry. "Setup" is not a verb. http://notaverb.com/setup 2010-03-17 04:39:50 +00:00
wp-feed.php Always exit after wp_redirect. props filosofo, fixes #15518. 2010-12-09 18:02:54 +00:00
wp-links-opml.php Do not Query for posts on OPML exports, Fixes OPML export script 404'ing due to no pages matching 'wp-links-opml.php'. Fixes #15195 2010-10-23 12:17:33 +00:00
wp-load.php Switch some strings to single rather than double quotes in wp-load.php. Fixes #17160 props niallkennedy. 2011-04-18 07:11:05 +00:00
wp-login.php Do not attach wp_enqueue_scripts to login_head. New login_enqueue_scripts hook. props nacin. fixes #16586 for trunk 2011-02-18 05:10:58 +00:00
wp-mail.php Strip trailing whitespace 2010-05-26 02:42:15 +00:00
wp-pass.php Always exit after wp_redirect. props filosofo, fixes #15518. 2010-12-09 18:02:54 +00:00
wp-rdf.php Always exit after wp_redirect. props filosofo, fixes #15518. 2010-12-09 18:02:54 +00:00
wp-register.php Always exit after wp_redirect. props filosofo, fixes #15518. 2010-12-09 18:02:54 +00:00
wp-rss.php Always exit after wp_redirect. props filosofo, fixes #15518. 2010-12-09 18:02:54 +00:00
wp-rss2.php Always exit after wp_redirect. props filosofo, fixes #15518. 2010-12-09 18:02:54 +00:00
wp-settings.php Don't load themes functions.php for upgrades. Props greuben. fixes #16722 2011-04-27 21:16:49 +00:00
wp-signup.php s/ms-options/settings/. props koke, fixes #15708. 2010-12-06 19:26:26 +00:00
wp-trackback.php Spelling and grammar fun. Fixes #11875 props cnorris23 2010-02-24 20:13:23 +00:00
xmlrpc.php Introduce a special wp_die handler for XMLRPC requests to ensure we send an XML response. 2011-04-17 08:35:51 +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 &#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.2
</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>Updating</h1>
<h2>Using the Automatic Updater</h2>
<p>If you are updating from version 2.7 or higher, you can use the automatic updater:</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>Updating Manually</h2>
<ol>
	<li>Before you update 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>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>System Requirements</h1>
<ul>
	<li><a href="http://php.net/">PHP</a> version <strong>5.2.4</strong> or higher.</li>
	<li><a href="http://www.mysql.com/">MySQL</a> version <strong>5.0</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>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/news/">The WordPress Blog</a></dt>
		<dd>This is where you'll find the latest updates and news related to WordPress. Recent WordPress 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><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. 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 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>. 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>License</h1>
<p>WordPress is free software, and is released under the terms of the <abbr title="GNU General Public License">GPL</abbr> version 2 or (at your option) any later version. See <a href="license.txt">license.txt</a>.</p>


</body>
</html>