=== PowerPress Posts From MySQL ===
Contributors: machouinard
Donate link: http://markchouinard.com
Tags: powerpress, podcasting, mysql
Requires at least: 3.0
Tested up to: 3.4.1
Stable tag: 0.9.1
License: GPLv2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html
Have a bunch of podcasts stored on your server and aren't excited about creating each post manually? This will help.
== Description ==
By populating a MySQL database table with all the information about the podcasts you can automatically create the posts needed for podcasting with the [Blubrry PowerPress plugin](http://wordpress.org/extend/plugins/powerpress/ "WordPress Podcasting").
Information required from the database:
* Host Name (i.e., localhost)
* Database Name
* Database Table Name
* Database Username
* Database Password.
Field names from the database table which will be used for the following:
* Title
* Category
* Post Body
* Featured Image(URL to an image)
* Media URL
* Media size
* Media type
* Date posted.
== Installation ==
This section describes how to install the plugin and get it working.
(make sure you have created the category in your blog before running or all the podcasts will be uncategorized)
1. Upload the folder containing `pfd.php` and `process.php` to the `/wp-content/plugins/` directory
2. Activate the plugin through the `Plugins` menu in WordPress
3. Configure your database settings in `Post From MySQL` under the `Tools` menu in the Dashboard and click `Save Changes`
4. After you've saved your settings, click `Process` and sit tight.
NOTE! For this plugin to work correctly, it requires a numerically sequential field to reference records by. The approach I've found best is to ensure all records are inserted into the table using an auto-incremented primary key such as id. The values for this field must begin with 1.
== Frequently Asked Questions ==
= How should I set up the database table? =
* Create fields that will correspond to those on the settings page.
* Make sure to include a field that can be used for sorting records. The default name for said field is 'id'. It is imperative that this field be auto-incremented starting at 1.
* In my case the podcasts themselves were numbered from 1 to 465. I also included an 'id' field which I set as primary and auto-increment so after all the podcasts were entered into the table, both 'id' and 'number' fields ranged from 1 to 465. This may seem redundant, but I included the 'id' field to ensure continuity in case the podcast numbers became non-sequential at some point in the future. As long as all records have an auto-incremented id field starting at 1 you should be able to run the plugin on multiple occasions adding only records that have been inserted since the previous run.
= I think something's not right. Can you fix it? =
I'll do my best. Post a message at explaining what's up and I'll get to work making it right.
= Does the MySQL table have to be on the same DB Host as my WordPress install? =
I don't believe so, but I honestly haven't tested that. Yet.
== Screenshots ==
1. Post From MySQL Settings Page in the Tools Menu
2. Once the database values are entered, a connection is made and you will be shown the total number of records the specified table holds.
3. If any of the values are incorrect you will be notified that there is no database connectivity. Please check your settings and re-enter.
4. You can supply a database field name to use if you would like to create a range of podcasts from your table. If either the Start Record or End Record fields are left blank they will default to the first and last record, respectively. The default field is `id`.
5. After clicking process, the posts will be created and you will be shown the number of podcasts posted.
== Changelog ==
v 0.9.1
* Added database connectivity checking.
* Added check to prevent posting same podcast twice based on the podcast/post title.
* Added ability to post from a range of records in the table based on a specific database field.
* Added display of total records in table.
== Arbitrary section ==
You may provide arbitrary sections, in the same format as the ones above. This may be of use for extremely complicated
plugins where more information needs to be conveyed that doesn't fit into the categories of "description" or
"installation." Arbitrary sections will be shown below the built-in sections outlined above.
== A brief Markdown Example ==
Ordered list:
1. Some feature
1. Another feature
1. Something else about the plugin
Unordered list:
* something
* something else
* third thing
Here's a link to [WordPress](http://wordpress.org/ "Your favorite software") and one to [Markdown's Syntax Documentation][markdown syntax].
Titles are optional, naturally.
[markdown syntax]: http://daringfireball.net/projects/markdown/syntax
"Markdown is what the parser uses to process much of the readme file"
Markdown uses email style notation for blockquotes and I've been told:
> Asterisks for *emphasis*. Double it up for **strong**.
``