Changeset 201620
- Timestamp:
- 02/03/2010 11:35:14 PM (16 years ago)
- File:
-
- 1 edited
-
nomoreie6/trunk/readme.txt (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
nomoreie6/trunk/readme.txt
r201617 r201620 1 1 === No More IE6 === 2 Contributors: Miguel Azevedo e Castro3 Donate link: http://w dmac.com/4 Tags: comments, spam5 Requires at least: 2.0.26 Tested up to: 2.17 Stable tag: 4.32 Contributors: FMacastro (Miguel Azevedo e Castro) 3 Donate link: http://www.wdmac.com/ 4 Tags: IE6, browser, update, warning, download, opera, firefox, ie, safari, chrome 5 Requires at least: - 6 Tested up to: - 7 Stable tag: - 8 8 9 Here is a short description of the plugin. This should be no more than 150 characters. No markup here.9 Adds a browser dependent upgrade-message to the website header, explaining the risks of IE6 and providing download links to a recent browsers. 10 10 11 11 == Description == 12 12 13 This is the long description. No limit, and you can use Markdown (as well as in the following sections).13 NoMoreIE6 this Word Press Plugin adds a browser dependent upgrade-message to the website header, explaining the risks of using IE6 and providing links with icons to upgrade to a recent browser. 14 14 15 For backwards compatibility, if this section is missing, the full length of the short description will be used, and 16 Markdown parsed. 17 18 A few notes about the sections above: 19 20 * "Contributors" is a comma separated list of wp.org/wp-plugins.org usernames 21 * "Tags" is a comma separated list of tags that apply to the plugin 22 * "Requires at least" is the lowest version that the plugin will work on 23 * "Tested up to" is the highest version that you've *successfully used to test the plugin*. Note that it might work on 24 higher versions... this is just the highest one you've verified. 25 * Stable tag should indicate the Subversion "tag" of the latest stable version, or "trunk," if you use `/trunk/` for 26 stable. 27 28 Note that the `readme.txt` of the stable tag is the one that is considered the defining one for the plugin, so 29 if the `/trunk/readme.txt` file says that the stable tag is `4.3`, then it is `/tags/4.3/readme.txt` that'll be used 30 for displaying information about the plugin. In this situation, the only thing considered from the trunk `readme.txt` 31 is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk `readme.txt` to reflect changes in 32 your in-development version, without having that information incorrectly disclosed about the current stable version 33 that lacks those changes -- as long as the trunk's `readme.txt` points to the correct stable tag. 34 35 If no stable tag is provided, it is assumed that trunk is stable, but you should specify "trunk" if that's where 36 you put the stable version, in order to eliminate any doubt. 15 It only uses CSS conditions, no scripts. Its totally unobtrusive, and built with valid W3C code. 37 16 38 17 == Installation == 39 18 40 This section describes how to install the plugin and get it working.41 42 e.g.43 44 19 1. Upload `plugin-name.php` to the `/wp-content/plugins/` directory 45 1. Activate the plugin through the 'Plugins' menu in WordPress 46 1. Place `<?php do_action('plugin_name_hook'); ?>` in your templates 20 2. Activate the plugin through the 'Plugins' menu in WordPress 47 21 48 22 == Frequently Asked Questions == … … 64 38 == Changelog == 65 39 66 = 1.0 =67 * A change since the previous version.68 * Another change.69 70 = 0.5 =71 * List versions from most recent at top to oldest at bottom.72 73 40 == Upgrade Notice == 74 41 75 = 1.0 =76 Upgrade notices describe the reason a user should upgrade. No more than 300 characters.77 42 78 = 0.5 =79 This version fixes a security related bug. Upgrade immediately.80 43 81 == Arbitrary section ==82 83 You may provide arbitrary sections, in the same format as the ones above. This may be of use for extremely complicated84 plugins where more information needs to be conveyed that doesn't fit into the categories of "description" or85 "installation." Arbitrary sections will be shown below the built-in sections outlined above.86 87 == A brief Markdown Example ==88 89 Ordered list:90 91 1. Some feature92 1. Another feature93 1. Something else about the plugin94 95 Unordered list:96 97 * something98 * something else99 * third thing100 101 Here's a link to [WordPress](http://wordpress.org/ "Your favorite software") and one to [Markdown's Syntax Documentation][markdown syntax].102 Titles are optional, naturally.103 104 [markdown syntax]: http://daringfireball.net/projects/markdown/syntax105 "Markdown is what the parser uses to process much of the readme file"106 107 Markdown uses email style notation for blockquotes and I've been told:108 > Asterisks for *emphasis*. Double it up for **strong**.109 110 `<?php code(); // goes in backticks ?>`
Note: See TracChangeset
for help on using the changeset viewer.