AutoBlogged at this time only works with a WordPress installation that you control. Note that it will not work on free WordPress hosts such as wordpress.com where you cannot install custom plugins.

We are considering versions of AutoBlogged that work with other platforms, so if you have a specific request, please comment below.

…

Tags: blogger wordpress

WordPress has a reputation of breaking compatibility with third party plugins and themes with each new version release. Although we try to fully test each new WordPress release, sometimes new releases have short beta periods or are even announced with no public beta testing.

To minimize the impact of compatibility issues with WordPress upgrades, we recommend the following:

• Create a test site to try out new releases before deploying them to your production site.
• Create full backups (all files and your database) before performing any upgrades.
• Check our Known Issues page before upgrading.

More Information

• Upgrading WordPress
• Upgrading WordPress Extended
• Common WordPress Installation Problems
• WordPress Release Archive

For the latest information of WordPress compatibility, see http://www.autoblogged.com/support/release-history/

For information on any known issues with the latest WordPress releases, see http://autoblogged.com/support/kb/known-issues/

Issue

By default WordPress will send a notification to any external blog posts referenced in your site, which show up as comments to the original post.  Sometimes you may not want to notify other blogs when you autoblog their posts.

Solution

To disable pingbacks and trackbacks, go to the Discussion settings in WordPress and uncheck the option Attempt to notify any blogs linked to from the article (slows down posting.)

For AutoBlogged to work with WordPress 2.8 or later, you must have AutoBlogged v2.5.74 or later. You can get the update with the original download link you received from us. If you no longer have this link, you can look it up here:

http://autoblogged.com/purchase/downloads/

For those times when e-mail support is not enough, we have partnered with WordPress HelpCenter to provide premium paid support for AutoBlogged at 10% off their normal rate. WordPress HelpCenter is an on-call help desk for WordPress that can answer your questions, install and troubleshoot plugins, assist you with theme customization, and generally help with any WordPress related issues.

WordPress HelpCenter is staffed by experienced web developers and backed by the expert WordPress developers at Crowd Favorite.

Support calls are normally free for the first three minutes and $19.99 for the first 25 minutes*, but mention AutoBlogged to get a 10% discount off their regular rates!

You can call WordPress HelpCenter Monday through Friday from 9am to 7pm pst (GMT-0800)

Phone: 512-788-9236

http://wphelpcenter.com/

* Visit the WordPress HelpCenter web site for detailed pricing and terms.

AutoBlogged post templates give you much flexibility in controlling how it creates posts in WordPress. If you want to configure all external links in your posts to use the nofollow tag, you can do this through your post template.

By default, AutoBlogged uses the following post template:

<p>%excerpt%</p>
%if:video%<p>%video%</p>%endif:video%
%if:thumbnail%<p>%thumbnail%</p>%endif:thumbnail%
[Read more here|Read the original here|Read more from the original source|
Continued here|Read more|More here|View original post here|More|See more
here|See original here|Originally posted here|Here is the original post|See
the original post|The rest is here|Read the rest here|See the rest here|Go
here to read the rest|Go here to see the original|See the original post here
|Read the original post|Original post|Read the original|Link|Excerpt from|
View post|Visit link|Follow this link|Continue reading here|See the article
here|Read this article|Read more]:[<br />| ]
<a target="_blank" href="%link%" title="%title%">%title%</a>

To give all external links the nofollow tag, simply change the last line of the post template to the following:

<a target="_blank" href="%link%" title="%title%" rel="nofollow">%title%</a>

Note that there are a number of WordPress plugins that also allow to control nofollow tags across your entire blog.

By default, AutoBlogged uses the original post title as the post for each new WordPress post it creates. However, you can customize how the title appears using our Custom Fields feature.

To do this, create a new custom field named title (note that it is lower case). For the Custom Field Value, you can enter anything you want. What makes this feature so powerful is that you can use the full AutoBlogged Post Template syntax here to include variables, use random values, or even use conditional values.

Here are some examples:

If you have come up with any cool title templates, please comment below, we’d love to see what you have!

Issue
This error is caused when you use the WordPress upload feature to install a plugin from the Add New plugin page. Unfortunately, this feature cannot handle a zip file that contains folders so it places the files in a subdirectory where WordPress cannot see the plugin header files to activate the plugin.

For example, the autoblogged.php file would be installed in a directory like this:
/wp-content/plugins/2.xx/autoblogged/autoblogged.php

Background
Since WordPress v2.8, there has been a feature to upload and install new plugins directly through the WordPress admin back-end by browsing for them on your local hard drive. WordPress will upload the zip file, extract it to the /plugins directory, and then try to activate the plugin. The problem is that since the AutoBlogged zip file contains the plugin files in a subdirectory, WordPress will create one directory with the name of the zip file and then the /autoblogged directory under that. Since that places the plugin file two directories deep, WordPress cannot find it and reports an invalid header. This same problem occurs with any plugin that uses subdirectories in the zip file, and there are many that do.

Solution
To correctly install AutoBlogged, you should use FTP or your hosting control panel’s file manager to upload the autoblogged directory directly under the wp-content/plugins directory. In other words, the full path to autoblogged.php should be:
/wp-content/plugins/autoblogged/autoblogged.php

If you have already used the WordPress upload feature to upload the plugin, you can fix it by moving the /autoblogged directory directly under the /wp-content/plugins directory.

Comments
Obviously, we could fix this ourselves by placing all the files in the zip file without any subfolders, which we tried for a short time, but then found that many users were confused about where to put the files when uploading them via ftp. By zipping them into the autoblogged directory it is pretty intuitive to upload that entire /autoblogged directory to the plugins directory in WordPress. Another benefit is that it allows us to place other files in our zip file that don’t need to be uploaded to your server.

We personally consider this to be a WordPress issue. One solution would be for them to recognize that zip files might actually contain subdirectories and unzip the files accordingly. Another solution would be to allow WordPress to activate plugins that are one or more directories deep under the /plugins directory. And of course, they really should fix their error message saying that our plugin header is invalid when in fact they just can’t find the file that they uploaded to the wrong place.

See Also:

http://wordpress.org/support/topic/280262

http://ijstyles.com/wordpress-2-8-issues-how-to-solve-plugin-does-not-have-a-valid-header/

http://wordpress.org/search/%22The+plugin+does+not+have+a+valid+header%22?forums=1