Changeset 934655
- Timestamp:
- 06/18/2014 06:56:48 PM (12 years ago)
- Location:
- ldd-directory-lite
- Files:
-
- 2 edited
-
tags/0.5.4-beta/README.txt (modified) (4 diffs)
-
trunk/README.txt (modified) (5 diffs)
Legend:
- Unmodified
- Added
- Removed
-
ldd-directory-lite/tags/0.5.4-beta/README.txt
r931854 r934655 54 54 *You should always back up your data before making major changes to the way your production web site functions.* 55 55 56 This plugin 57 56 58 Installation is easiest when done through your WordPress Dashboard: 57 59 1. Select **Plugins >> Add New** from your sites WordPress dashboard. … … 68 70 This plugin is a rewrite of the [LDD Business Directory](http://wordpress.org/plugins/ldd-business-directory/). As such, you can upgrade to LDD Directory Lite from LDD Business Directory *without* losing any of your content. 69 71 70 * *You do not need to deactivate or uninstall the LDD Business Directory plugin before activating LDD Directory Lite.**72 *You do not need to deactivate or uninstall the LDD Business Directory plugin before activating LDD Directory Lite.* 71 73 74 1. Install and activate the plugin using the above instructions. 75 2. Once installed, if data is detected from the original plugin it will automatically notify you with a rather large message at the top of your Directory Lite dashboard screens. 76 3. Press the "Import Data" button, and you will be taken to the upgrade page. 77 4. All done! 72 78 73 1. Install and activate the plugin using the instructions [here](http://wordpress.org/plugins/ldd-directory-lite/installation/). 74 2. The plugin will collect all your existing content and import it automatically. 75 76 As of now the plugin *does not* remove the data from the original Directory plugin. It also does not store any of its own data in the same locations, so the two datasets are completely separate. 77 78 While this does leave some clutter behind, it also ensures a painless upgrade path. Until the plugin has successfully been upgraded on a few hundred more sites, we chose not to remove your old data in case you either wanted to roll back to using the original plugin, or on the chance that something went awry with the beta. 79 80 A future version of LDD Directory Lite will scan for this leftover data and ask if you want to remove it. 79 **LDD Directory Lite only imports this data, it does nothing to alter or remove it. If you decide to revert to the original plugin because of errors encountered while using this beta release, you will have all you original content waiting for you.** 81 80 82 81 … … 101 100 102 101 102 == Upgrade Notice == 103 104 = 0.5.5-beta = 105 This release addresses a variety of theme compatibility issues, and fixes a severe memory problem on the admin dashboard. 106 107 108 == Changelog == 109 110 = 0.5.4-beta = 111 **enhancements** 112 * Major update to the upgrade functionality for people migrating from [LDD Business Directory](http://wordpress.org/plugins/ldd-business-directory/) 113 * Enqueued Bootstrap core as early as possible so that theme styles will cascade after 114 * Moved away from handling addresses internally, utilizing Google API more effectively 115 **fixes** 116 * Fixed outgoing emails hardcoded From: address 117 * Fixed an out of memory error being caused by `ldl_get_page_haz_shortcode()`, shortcode detection is now done during `save_post` 118 119 = 0.5.3-beta = 120 **enhancements** 121 * Added opt-in anonymous usage tracking 122 * Trimmed a lot of excess from Bootstrap, and removed it from the global scope (it shouldn't affect the theme anymore) 123 * Condensed Bootflat into the main style sheet 124 **fixes** 125 * Fixed an issue with the search, submitting the form now takes you to physical search results 126 127 = 0.5.1-beta = 128 * Initial commit of the forked [LDD Business Directory](http://wordpress.org/plugins/ldd-business-directory/) plugin. 129 130 103 131 == Issues & Bugs == 104 132 … … 113 141 **Feature requests can also be posted on the [GitHub Issue Tracker](https://github.com/mwaterous/ldd-directory-lite/issues).** 114 142 115 == C hangelog==143 == Credits == 116 144 117 = 0.5.4-beta = 145 I tend to spend a lot of time coding; not only is it my day job, but it's also one of the things I like to do in my spare time. No matter how much time I spend however, I'm just one person. This plugin is where it is thanks to the hard work and open source beliefs of more people than just myself. While I always try to make sure they are credited in the code itself, I would like to take the time to include them here as well. In no particular order: 118 146 119 = 0.5.3-beta = 120 * Added opt-in anonymous usage tracking 121 * Fixed an issue with the search, submitting the form now takes you to physical search results 122 * Trimmed a lot of excess from Bootstrap, and removed it from the global scope (it shouldn't affect the theme anymore) 123 * Condensed Bootflat into the main style sheet 147 **Who:** [WebDevStudios](http://webdevstudios.com/)<br> 148 **Where:** [Custom Metaboxes and Fields for WordPress](https://github.com/WebDevStudios/Custom-Metaboxes-and-Fields-for-WordPress)<br> 149 **Why:** Used to build the administrative user interface for the directory listings custom post types. 124 150 125 = 0.5.1-beta = 126 * Initial commit of the forked [LDD Business Directory](http://wordpress.org/plugins/ldd-business-directory/) plugin. 151 **Who:** Federico Ulfo<br> 152 **Where:** [Rain.TPL](http://www.raintpl.com/)<br> 153 **Why:** This amazing but lightweight template parser helps keep our views sorted away from our programming logic. It hasn't yet been decided whether or not this will be permanent (to capitalize on the caching abilities) or temporary (to run straight PHP templates for speed), it is an amazing parser that has helped me focus on other areas of programming. 154 155 **Who:** [yoast](https://yoast.com)<br> 156 **Where:** [WordPress SEO](https://yoast.com/wordpress/plugins/#wpseo) Usage Tracking<br> 157 **Why:** Code from the WordPress SEO plugin was integrated into this plugin in order to quickly add anonymous usage tracking. The information supplied by those who opt in to this program allows us a fantastic insight as to what configurations the plugin is being used on, and how to test future releases. 158 159 **Who:** [Bootstrap](http://getbootstrap.com/) & [Bootflat](http://bootflat.github.io/)<br> 160 **Where:** Front end interface.<br> 161 **Why:** A trimmed down copy of bootstrap (which can be disabled if your theme already uses it) and bootflat were used to rapidly define the front end interface for the plugin. These libraries are amazing feats of CSS prowess. 162 163 **Who:** [Viljami S.](http://viljamis.com), [Henrik Joreteg, Adam Brault & Michael Garvin](http://happyjs.com/), [Ryan Heath](http://rpheath.com/)<br> 164 **Where:** [Responsive Slides](http://responsiveslides.com), [Happy.js](http://happyjs.com/), and [searchbox](https://github.com/rpheath/searchbox)<br> 165 **Why:** Various javascript elements all around the plugin are built on or with scripts originally coded by the above folk. As of this writing, my own javascript abilities are nowhere near as advanced as my ability to draw circles on my stomach and pat my head at the same time. Until they are, I seek out the knowledge of others. 166 167 **Who:** [Evan Solomon](http://evansolomon.me/), [Michel Fortin](http://michelf.ca), & [John Gruber](http://daringfireball.net)<br> 168 **Where:** [WP Github Flavored Markdown Comments](https://github.com/evansolomon/wp-github-flavored-markdown-comments/blob/master/github-flavored-markdown-comments.php)<br> 169 **Why:** Because markdown! Markdown is slowly being integrated in to the front end of the plugin, which will allow users to have some measure of control over the way their listings appear (should the site administrator choose to enable it). 170 171 **Who:** [Tim Schlechter](https://github.com/TimSchlechter)<br> 172 **Where:** [Bootstrap Tags Input](https://timschlechter.github.io/bootstrap-tagsinput/examples/)<br> 173 **Why:** This was added initially on the dashboard to group multiple notification email addresses, but I can see it easily having a future on the front end of the plugin as well. 174 -
ldd-directory-lite/trunk/README.txt
r931853 r934655 4 4 Requires at least: 3.9.1 5 5 Tested up to: 3.9.1 6 Stable tag: 0.5. 4-beta6 Stable tag: 0.5.5-beta 7 7 License: GPLv2 8 8 License URI: http://www.gnu.org/licenses/gpl-2.0.html … … 54 54 *You should always back up your data before making major changes to the way your production web site functions.* 55 55 56 This plugin 57 56 58 Installation is easiest when done through your WordPress Dashboard: 57 59 1. Select **Plugins >> Add New** from your sites WordPress dashboard. … … 68 70 This plugin is a rewrite of the [LDD Business Directory](http://wordpress.org/plugins/ldd-business-directory/). As such, you can upgrade to LDD Directory Lite from LDD Business Directory *without* losing any of your content. 69 71 70 * *You do not need to deactivate or uninstall the LDD Business Directory plugin before activating LDD Directory Lite.**72 *You do not need to deactivate or uninstall the LDD Business Directory plugin before activating LDD Directory Lite.* 71 73 74 1. Install and activate the plugin using the above instructions. 75 2. Once installed, if data is detected from the original plugin it will automatically notify you with a rather large message at the top of your Directory Lite dashboard screens. 76 3. Press the "Import Data" button, and you will be taken to the upgrade page. 77 4. All done! 72 78 73 1. Install and activate the plugin using the instructions [here](http://wordpress.org/plugins/ldd-directory-lite/installation/). 74 2. The plugin will collect all your existing content and import it automatically. 75 76 As of now the plugin *does not* remove the data from the original Directory plugin. It also does not store any of its own data in the same locations, so the two datasets are completely separate. 77 78 While this does leave some clutter behind, it also ensures a painless upgrade path. Until the plugin has successfully been upgraded on a few hundred more sites, we chose not to remove your old data in case you either wanted to roll back to using the original plugin, or on the chance that something went awry with the beta. 79 80 A future version of LDD Directory Lite will scan for this leftover data and ask if you want to remove it. 79 **LDD Directory Lite only imports this data, it does nothing to alter or remove it. If you decide to revert to the original plugin because of errors encountered while using this beta release, you will have all you original content waiting for you.** 81 80 82 81 … … 101 100 102 101 102 == Upgrade Notice == 103 104 = 0.5.5-beta = 105 This release addresses a variety of theme compatibility issues, and fixes a severe memory problem on the admin dashboard. 106 107 108 == Changelog == 109 110 = 0.5.4-beta = 111 **enhancements** 112 * Major update to the upgrade functionality for people migrating from [LDD Business Directory](http://wordpress.org/plugins/ldd-business-directory/) 113 * Enqueued Bootstrap core as early as possible so that theme styles will cascade after 114 * Moved away from handling addresses internally, utilizing Google API more effectively 115 **fixes** 116 * Fixed outgoing emails hardcoded From: address 117 * Fixed an out of memory error being caused by `ldl_get_page_haz_shortcode()`, shortcode detection is now done during `save_post` 118 119 = 0.5.3-beta = 120 **enhancements** 121 * Added opt-in anonymous usage tracking 122 * Trimmed a lot of excess from Bootstrap, and removed it from the global scope (it shouldn't affect the theme anymore) 123 * Condensed Bootflat into the main style sheet 124 **fixes** 125 * Fixed an issue with the search, submitting the form now takes you to physical search results 126 127 = 0.5.1-beta = 128 * Initial commit of the forked [LDD Business Directory](http://wordpress.org/plugins/ldd-business-directory/) plugin. 129 130 103 131 == Issues & Bugs == 104 132 … … 113 141 **Feature requests can also be posted on the [GitHub Issue Tracker](https://github.com/mwaterous/ldd-directory-lite/issues).** 114 142 115 == C hangelog==143 == Credits == 116 144 117 = 0.5.4-beta = 145 I tend to spend a lot of time coding; not only is it my day job, but it's also one of the things I like to do in my spare time. No matter how much time I spend however, I'm just one person. This plugin is where it is thanks to the hard work and open source beliefs of more people than just myself. While I always try to make sure they are credited in the code itself, I would like to take the time to include them here as well. In no particular order: 118 146 119 = 0.5.3-beta = 120 * Added opt-in anonymous usage tracking 121 * Fixed an issue with the search, submitting the form now takes you to physical search results 122 * Trimmed a lot of excess from Bootstrap, and removed it from the global scope (it shouldn't affect the theme anymore) 123 * Condensed Bootflat into the main style sheet 147 **Who:** [WebDevStudios](http://webdevstudios.com/)<br> 148 **Where:** [Custom Metaboxes and Fields for WordPress](https://github.com/WebDevStudios/Custom-Metaboxes-and-Fields-for-WordPress)<br> 149 **Why:** Used to build the administrative user interface for the directory listings custom post types. 124 150 125 = 0.5.1-beta = 126 * Initial commit of the forked [LDD Business Directory](http://wordpress.org/plugins/ldd-business-directory/) plugin. 151 **Who:** Federico Ulfo<br> 152 **Where:** [Rain.TPL](http://www.raintpl.com/)<br> 153 **Why:** This amazing but lightweight template parser helps keep our views sorted away from our programming logic. It hasn't yet been decided whether or not this will be permanent (to capitalize on the caching abilities) or temporary (to run straight PHP templates for speed), it is an amazing parser that has helped me focus on other areas of programming. 154 155 **Who:** [yoast](https://yoast.com)<br> 156 **Where:** [WordPress SEO](https://yoast.com/wordpress/plugins/#wpseo) Usage Tracking<br> 157 **Why:** Code from the WordPress SEO plugin was integrated into this plugin in order to quickly add anonymous usage tracking. The information supplied by those who opt in to this program allows us a fantastic insight as to what configurations the plugin is being used on, and how to test future releases. 158 159 **Who:** [Bootstrap](http://getbootstrap.com/) & [Bootflat](http://bootflat.github.io/)<br> 160 **Where:** Front end interface.<br> 161 **Why:** A trimmed down copy of bootstrap (which can be disabled if your theme already uses it) and bootflat were used to rapidly define the front end interface for the plugin. These libraries are amazing feats of CSS prowess. 162 163 **Who:** [Viljami S.](http://viljamis.com), [Henrik Joreteg, Adam Brault & Michael Garvin](http://happyjs.com/), [Ryan Heath](http://rpheath.com/)<br> 164 **Where:** [Responsive Slides](http://responsiveslides.com), [Happy.js](http://happyjs.com/), and [searchbox](https://github.com/rpheath/searchbox)<br> 165 **Why:** Various javascript elements all around the plugin are built on or with scripts originally coded by the above folk. As of this writing, my own javascript abilities are nowhere near as advanced as my ability to draw circles on my stomach and pat my head at the same time. Until they are, I seek out the knowledge of others. 166 167 **Who:** [Evan Solomon](http://evansolomon.me/), [Michel Fortin](http://michelf.ca), & [John Gruber](http://daringfireball.net)<br> 168 **Where:** [WP Github Flavored Markdown Comments](https://github.com/evansolomon/wp-github-flavored-markdown-comments/blob/master/github-flavored-markdown-comments.php)<br> 169 **Why:** Because markdown! Markdown is slowly being integrated in to the front end of the plugin, which will allow users to have some measure of control over the way their listings appear (should the site administrator choose to enable it). 170 171 **Who:** [Tim Schlechter](https://github.com/TimSchlechter)<br> 172 **Where:** [Bootstrap Tags Input](https://timschlechter.github.io/bootstrap-tagsinput/examples/)<br> 173 **Why:** This was added initially on the dashboard to group multiple notification email addresses, but I can see it easily having a future on the front end of the plugin as well. 174
Note: See TracChangeset
for help on using the changeset viewer.