Feeder Support
Support Forums
- Feeder Discussions - for support questions and feature requests.
Frequently Asked Questions
These are some frequently asked questions about Feeder. You can also find comprehensive help files in the application by choosing Help > Feeder Help from the main menu.
Licences
How do I upgrade to Feeder 2? Do I need to pay?
Feeder 1.5 will not accept my registration code.
Publishing
Feeder only seems to upload one file at a time.
Podcasting
My podcast's artwork looks fine in Feeder, but doesn't appear in the iTunes Store.
I've updated my podcast but changes don't appear in the iTunes Store.
Where can I get help with my podcast in the iTunes Store?
Feeds in Other Applications
Why, after deleting items in Feeder, do they still show up in Safari?
How can I get Safari or other browsers to auto-detect a feed?
Email Support
If you can't find an answer in the FAQs or support forums, you can also send support questions only to feeder@reinventedsoftware.com. Support is via email only.
Answers
How do I upgrade to Feeder 2? Do I need to pay?
Feeder 1.x users can upgrade to version 2 for $14.95. If your original license was purchased within the 6 months prior to Feeder 2.0's release, you will qualify for a free upgrade.
To upgrade, go to purchase Feeder as normal, choose an Upgrade license and enter your Feeder 1.x registration code. You will be told if you qualify for a free upgrade or offered the upgrade discount, as appropriate.
If you still need Feeder 1.5.10, download it from here: Feeder_1.5.10.dmg
Feeder 1.5 will not accept my registration code.
You may have trouble activating older versions of Feeder on Mac OS X 10.6 or later. Please download the following application to register Feeder instead: RegisterFeeder.zip
If registration still doesn't work, please get in touch.
Feeder shows the message "Cannot cd to directory", "Server denied you to change to the given directory" or "No such file" when publishing.
Usually this happens because a path for the feed or server is incorrect. To fix this problem:
- Open the Servers window by choosing Window > Servers from the menu.
- Select the server you are using to publish.
- Clear everything out of the Site Folder field and click the Choose button next to it.
- Choose the folder where your web site's files are kept. This is usually called "public_html", "htdocs", "yourdomain.com" or similar.
- Close the Servers window.
The next thing to check is that your feed is set to upload to the correct directory.
- Select the feed in the sidebar.
- Choose File > Publish from the menu.
- Click the Settings button.
- Clear everything out of the Path field and click the Choose button next to it.
- Choose the folder where your want to store your feed.
- Click Continue, then click Publish.
Feeder only seems to upload one file at a time to my FTP server.
If Feeder only seems to upload one file at a time to an FTP server, try the following.
- Open the Servers window by choosing Window > Servers from the menu.
- Select the server you are using to publish.
- Click the Options button.
- Uncheck Reuse Connections When Possible.
- Click Save.
- Close the Servers window.
- You can then try publishing your feed again.
My podcast's artwork looks fine in Feeder, but doesn't appear in the iTunes Store.
iTunes makes a copy of your podcast's image on different servers around the world to save you bandwidth. It can take up to a week for your podcast's artwork to appear in the iTunes Store.
To ensure everything is OK do this:
- Click Share in the toolbar
- Select "Podcast Artwork" in the list
- Click Copy to copy the image URL to the clipboard.
- Paste the URL into a web browser.
If the image appears in your browser, there is no problem. If it doesn't, please get in touch. See Apple's Making a Podcast guide for more information on podcasts in the iTunes Store.
I've updated my podcast but changes don't appear in the iTunes Store.
The iTunes Store check for updates to your podcast every 24 hours and it could take a couple of days for your changes to appear in the iTunes Store.
Feeder can notify iTunes when changes to your podcast are published, using a ping service. To set this up for your feed:
- Show the Info view if it is not already visible by choosing View > Show Feed Info from the menu.
- Click Settings.
- Select the Ping Services section.
- Check "iTunes".
The next time you publish your feed, Feeder will "ping" iTunes to notify it of your changes.
Where can I get help with my podcast in the iTunes Store?
If you are having problems with your podcast in the iTunes Store and your feed is valid according to the FeedValidator, then you may be able to find answers on the Apple site:
Why, after deleting items in Feeder, do they still show up in Safari?
Safari and some other RSS readers keep a copy of your items for a certain period of time. You can see this period in Safari's RSS preferences.
You can clear Safari's cache of items by clicking the Remove Now button and restarting Safari.
How can I get Safari or other browsers to auto-detect a feed?
Most web browsers (e.g. Safari, Firefox, OmniWeb) and RSS reader apps can auto-detect feeds on a site by checking for an alternate link with type "application/rss+xml" in the <head> section of your web page, similar to this:
<link rel="alternate" type="application/rss+xml" title="RSS" href="http://example.com/index.xml" />
Where http://example.com/index.xml is the URL to your feed. You can get this in Feeder by choosing File > Share from the menu, and choosing the Web Page Links section.
Why does FeedValidator validate my feed but give the warning 'Your feed appears to be encoded as "utf-8", but your server is reporting "US-ASCII" '?
XML files such as the RSS files created by Feeder state the text encoding at the top of the file, like this:
<?xml version="1.0" encoding="utf-8"?>
This is correct - XML files created by Feeder are encoded as UTF-8. However, when a newsreader or browser contacts your server to get a file, the server returns a MIME type, which the web server determines by checking the file's extension against a configuration file. If not found, the web server will default the type to something like "text/text", which suggests a default encoding of US-ASCII.
For RSS feeds created by Feeder, the correct MIME type to return is either "application/xml" for a file with a .xml extension, or "application/rss+xml" for a file with a .rss extension. Having either of these MIME types returned will tell the newsreader or web browser to determine the text encoding from the processing instruction in the file rather than the MIME type.
The solution to this problem is to configure your web server to return the correct MIME type. With Apache this can be done using AddType. Contact your system administrator if you are not able to change this yourself.
In practice, newsreader applications tend to ignore the MIME type when determining text encoding, preferring to check the processing instruction in the XML, if at all.
This is also discussed on FeedValidator's help pages.