Ticket #85 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

OPML import nuke previous channels and folders

Reported by: znarf Owned by: mbonetti
Priority: high Milestone: Gregarius 0.5.1
Component: BUGS Version:
Severity: normal Keywords:
Cc:

Description

Maybe it's a feature but for me it's a bug.

While importing an OPML i don't expect to replace the actual channels but add new channels to the existing.

The best being to detect feeds in doublon.

The very best being to be able to target imported OPMLs in a precise folder.

Change History

Changed 3 years ago by mbonetti

  • status changed from new to assigned
  • milestone set to Gregarius 0.4.3

Yes, or at least warn the user that he's going to lose all his current subscriptions...

Will give this one a look this evening, also setting as blocker for 0.4.4

Changed 3 years ago by znarf

Excellent !

Changed 3 years ago by anonymous

I also came across this bug, and when using the OPML import feature, I also expected that the new items would be added to the existing set of feeds, not completely replace them.

Also agree with znarf that it'd be really really nice to be able to direct all the imported items from an OPML feed into a folder, as I find myself importing and then copying all the imported items into a new folder.

Changed 3 years ago by gregarius@…

I was also bitten by this bug - imported all my LJ feeds expecting them to be added to my existing feeds - but, with no warning, my existing feeds instead went bye-byes.

At minimum, a warning should be given to a user

Even better, all items in the import should go into a specified folder (with duplicate detection - if that feed already exists, move it into the specified folder).

Fortunately, I was able to rescue most of my feeds from a google-cached copy of my gregarius front page (note to self: really must stop google caching that)

Changed 3 years ago by mbonetti

  • priority changed from normal to high
  • milestone changed from Gregarius 0.4.3 to Gregarius 0.5.1

Changed 3 years ago by mbonetti

  • status changed from assigned to closed
  • resolution set to fixed

Fixed in [750], at last.

Note: See TracTickets for help on using tickets.