See the INSTALL file in this directory named for instructions.
Within Movable Type, navigate to the Main Page or the "Entries" page for the blog into which you will be importing reBlog posts from a Reblog Source feed.
Scroll to the bottom, click on the Plugin Action labelled "Configure your Reblog Source Source Feed"
On the configuration page, input the URL of a reBlog Source feed and submit. Most likely it is the rss.php
page of your reFeed installation.
If your reFeed installation is in a directory that requires HTTP Authentication (the in-browser
login/password) you can include the requisite login/passwod in this URL. For example:
http://USERNAME:PASSWORD@www.reblog.org/refeed/out/rss.php
Within Movable Type, navigate to the Main Page or the "Entries" page for the blog into which you will be importing reBlog posts from a Reblog Source feed.
Scroll to the bottom, click on the Plugin Action labelled "Import Entries from your Reblog Source Source Feed"
This will automatically import new posts from your Reblog source feed and rebuild the appropriate pages in Movable Type. Also, note that if you update a post in the source feed, that post will be updated and rebuilt in Movable Type.
The reBlog Movable Type plugin will now import categories from your Reblog Source Feed and creates the necessary categories in Movable Type's category database.
It iterprets the value of the <dc:subject> element as a set of del.icio.us style category 'tags'.
That is, tokens separated by whitespace are considered separate categories.
Also, within one category, double-colons '::
' will be interpreted as denoting a hierarchy (Movable Type has sub-categories). And, URL-style, a '+' will be interpreted as a space in the category name.
For Example, "blogs feeds::RSS::1.0 feeds::Atom with+space" would result in the following category tree being created and attributed to the reBlogged item:
The reBlog plugin also implements several new template tags for display attributive metadata along with the content of imported reBlog posts.
Use this before any of the others. It doesn't actually result in any output text but pre-fetches data necessary for the other tags to function correctly.
Is this entry a reBlog post.
Is this entry not a reBlog post. You can also use <MTElse>
Source blog title
Link to source blog
(backwards compatible with <MTEntryReblogSourceLink>)
Link to source blog xml feed
(backwards compatible with <MTEntryReblogSourceLinkXML>)
Primary link for this post
Via link for this post
Original Author of this post
(backwards compatible with <MTEntryReblogAuthor>)
Original Date of publication for this post in its source feed. You can use the same format="...." as for <MTEntryDate>
Special reBlog unique identifier. Don't use this.
Container tag for list of sources
Source blog title
(backwards compatible with <MTReblogSourceTitle>)URL for source blog
(backwards compatible with <MTReblogSourceLink>)XML feed url for source blog
(backwards compatible with <MTReblogSourceLinkXML>)By itself, this returns the number of posts for that source.
It has lots of options though:
These options can be used to adjust formatting (i.e. font-size, HEX-colors, etc.) by some factor representing how big one feed is to your reblog.
Examples:
<$MTReblogSourceFreq format="percent" truncate="1" $>
returns the % of posts for that feed, as a whole # from 0 - 100
<$MTReblogSourceFreq min="1" max="10" factor=".1" truncate="1" $>
returns the integral # of posts, multiplied by .1, with a min return value of 1 and a max return value of 10
We have also provided example templates in the ./tmpl/ directory of this installation:
Movable Type 3.x has a feature for auto-trackbacking, which can be enabled by clicking the checkbox entitled "Enable TrackBack Auto-Discovery" in Weblog Config -> Preferences.
Thus, if you have this enabled and you reBlog a post that contains a link to an MT blog with trackbacking enabled, it should auto-trackback for you. (note: this is totally untested)
And, fortunately for you, reFeed by default includes a link to the original post in the content of the post being spat out by its feeds. Notice the "Via XXX" link that is automatically generated when you 'publish' an item but select a link different than the one it came with in its originating feed.