Changeset 1412754
- Timestamp:
- 05/09/2016 03:05:30 AM (10 years ago)
- Location:
- 2mb-autocode
- Files:
-
- 2 added
- 4 edited
- 1 copied
-
tags/1.2.2 (copied) (copied from 2mb-autocode/trunk)
-
tags/1.2.2/2mb-autocode.php (modified) (2 diffs)
-
tags/1.2.2/LICENSE (added)
-
tags/1.2.2/readme.txt (modified) (3 diffs)
-
trunk/2mb-autocode.php (modified) (2 diffs)
-
trunk/LICENSE (added)
-
trunk/readme.txt (modified) (3 diffs)
Legend:
- Unmodified
- Added
- Removed
-
2mb-autocode/tags/1.2.2/2mb-autocode.php
r1209327 r1412754 6 6 Plugin Name: 2MB Autocode 7 7 Plugin URI: http://2mb.solutions/plugins/autocode 8 Version: 1.2. 18 Version: 1.2.2 9 9 License: Gpl v2 or later 10 10 */ … … 216 216 <br> 217 217 <ul> 218 <li>To stop the text from displaying at the top or bottom of a post and the homepage, enter ##no_top## for the top text or ##no_bottom## for the bottom text anywhere in the post. </li>219 <li>To stop the text from displaying selectively on the homepage *or* the post page, enter ##no_top_home## or ##no_bottom_home## for the homepage, or ##no_top_post## or ##no_bottom_post## for the post page. </li>220 <li>To enable the top and/or bottom text when it is normally not enabled on the homepage, add ##do_top_home## or ##do_bottom_home## to anywhere on the post. </li>218 <li>To stop the text from displaying at the top or bottom of a post and the homepage, enter ##no_top## for the top text or ##no_bottom## for the bottom text anywhere in the post. Alternatively, simply select the appropriate option on the post edit page itself.</li> 219 <li>To stop the text from displaying selectively on the homepage *or* the post page, enter ##no_top_home## or ##no_bottom_home## for the homepage, or ##no_top_post## or ##no_bottom_post## for the post page. Once again, these options can be set in the post editor.</li> 220 <li>To enable the top and/or bottom text when it is normally not enabled on the homepage, add ##do_top_home## or ##do_bottom_home## to anywhere on the post. And again, post editor... you get it.</li> 221 221 <li>To include php code to run in a page, enter [php]CODE HERE[/php] anywhere in the post. Note: You should not include the beginning opening or end closing php tag, but you may exit php and re-enter by using a closing then opening tag.</li> 222 <li>To place the top or bottom text at a different point than at the top or bottom, enter ##do_bottom## or ##do_top## where you want them in the post editor.</li> 222 223 </ul> 223 224 <br> -
2mb-autocode/tags/1.2.2/readme.txt
r1210487 r1412754 4 4 Tags: autocode, code placement, automatic, php, html, preformatted text, top, bottom, modify posts 5 5 Requires at least: 3.0 6 Tested up to: 4. 37 Stable tag: 1.2. 16 Tested up to: 4.5.1 7 Stable tag: 1.2.2 8 8 License: GPLv2 or later 9 9 License URI: http://www.gnu.org/licenses/gpl-2.0.html … … 76 76 == Changelog == 77 77 78 = 1.2.2 = 79 80 * Documentation updates. 81 78 82 = 1.2.1 = 79 83 … … 86 90 87 91 = 1.1.2 = 92 88 93 *Very important! If you were using inline php to put php on your blog before, please upgrade to this version or uninstall inline php before upgrading to 2mb autocode 1.1. There was a problem that caused the two plugins to conflict, which has now been solved. *** NOTE *** if your blog is not accessible due to the conflict, do the following: Delete the inline php folder from your server, and all should be well. We're sorry for any inconvenience -- sometimes even plugin developers can screw up ;-). 89 94 -
2mb-autocode/trunk/2mb-autocode.php
r1209327 r1412754 6 6 Plugin Name: 2MB Autocode 7 7 Plugin URI: http://2mb.solutions/plugins/autocode 8 Version: 1.2. 18 Version: 1.2.2 9 9 License: Gpl v2 or later 10 10 */ … … 216 216 <br> 217 217 <ul> 218 <li>To stop the text from displaying at the top or bottom of a post and the homepage, enter ##no_top## for the top text or ##no_bottom## for the bottom text anywhere in the post. </li>219 <li>To stop the text from displaying selectively on the homepage *or* the post page, enter ##no_top_home## or ##no_bottom_home## for the homepage, or ##no_top_post## or ##no_bottom_post## for the post page. </li>220 <li>To enable the top and/or bottom text when it is normally not enabled on the homepage, add ##do_top_home## or ##do_bottom_home## to anywhere on the post. </li>218 <li>To stop the text from displaying at the top or bottom of a post and the homepage, enter ##no_top## for the top text or ##no_bottom## for the bottom text anywhere in the post. Alternatively, simply select the appropriate option on the post edit page itself.</li> 219 <li>To stop the text from displaying selectively on the homepage *or* the post page, enter ##no_top_home## or ##no_bottom_home## for the homepage, or ##no_top_post## or ##no_bottom_post## for the post page. Once again, these options can be set in the post editor.</li> 220 <li>To enable the top and/or bottom text when it is normally not enabled on the homepage, add ##do_top_home## or ##do_bottom_home## to anywhere on the post. And again, post editor... you get it.</li> 221 221 <li>To include php code to run in a page, enter [php]CODE HERE[/php] anywhere in the post. Note: You should not include the beginning opening or end closing php tag, but you may exit php and re-enter by using a closing then opening tag.</li> 222 <li>To place the top or bottom text at a different point than at the top or bottom, enter ##do_bottom## or ##do_top## where you want them in the post editor.</li> 222 223 </ul> 223 224 <br> -
2mb-autocode/trunk/readme.txt
r1210487 r1412754 4 4 Tags: autocode, code placement, automatic, php, html, preformatted text, top, bottom, modify posts 5 5 Requires at least: 3.0 6 Tested up to: 4. 37 Stable tag: 1.2. 16 Tested up to: 4.5.1 7 Stable tag: 1.2.2 8 8 License: GPLv2 or later 9 9 License URI: http://www.gnu.org/licenses/gpl-2.0.html … … 76 76 == Changelog == 77 77 78 = 1.2.2 = 79 80 * Documentation updates. 81 78 82 = 1.2.1 = 79 83 … … 86 90 87 91 = 1.1.2 = 92 88 93 *Very important! If you were using inline php to put php on your blog before, please upgrade to this version or uninstall inline php before upgrading to 2mb autocode 1.1. There was a problem that caused the two plugins to conflict, which has now been solved. *** NOTE *** if your blog is not accessible due to the conflict, do the following: Delete the inline php folder from your server, and all should be well. We're sorry for any inconvenience -- sometimes even plugin developers can screw up ;-). 89 94
Note: See TracChangeset
for help on using the changeset viewer.