You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To work around the problem, right click feed entry, select "Edit selected item", under "Type" change "RSS 2.0/2.0.1" to "ATOM", select "OK", refresh feed.
Nb. If one then exports to OPML, what were imported as version="ATOM" feeds are exported as version="RSS".
What was the expected result?
ATOM feeds, once imported, remain ATOM feeds.
What actually happened?
I can confirm that version 4.3.2 does not have this problem and that upgrading from 4.3.2 to 4.3.3 itself does not cause a problem; the problem occurs only when importing an OPML file on a clean install of 4.3.3.
Otherwise, I am enjoying RSS Guard immensely.
Debug log
I was unable to create a log
Operating system and version
OS: macOS 13.3.1
RSS Guard version: 4.3.3
The text was updated successfully, but these errors were encountered:
Brief description of the issue
Following the release of 4.3.3, on OPML file import, atom feeds are being changed to "RSS 2.0/2.0.1" feeds, including seemingly all GitHub and GitLab feeds (eg, https://github.com/martinrotter/rssguard/releases.atom).
How to reproduce the bug?
To work around the problem, right click feed entry, select "Edit selected item", under "Type" change "RSS 2.0/2.0.1" to "ATOM", select "OK", refresh feed.
Nb. If one then exports to OPML, what were imported as version="ATOM" feeds are exported as version="RSS".
What was the expected result?
ATOM feeds, once imported, remain ATOM feeds.
What actually happened?
I can confirm that version 4.3.2 does not have this problem and that upgrading from 4.3.2 to 4.3.3 itself does not cause a problem; the problem occurs only when importing an OPML file on a clean install of 4.3.3.
Otherwise, I am enjoying RSS Guard immensely.
Debug log
I was unable to create a log
Operating system and version
The text was updated successfully, but these errors were encountered: