Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support OPML 2.0 #286

Closed
dabeeeenster opened this issue Jan 8, 2019 · 7 comments
Closed

Support OPML 2.0 #286

dabeeeenster opened this issue Jan 8, 2019 · 7 comments
Milestone

Comments

@dabeeeenster
Copy link

Im trying to migrate data from Workflowy - it exports as OPML 2.0 which can't be imported into Trilium. The import fails silently.

@zadam
Copy link
Owner

zadam commented Jan 8, 2019

Would it be possible to attach an example OPML v2 export?

@dabeeeenster
Copy link
Author

<?xml version="1.0"?>
<opml version="2.0">
  <head>
    <ownerEmail>
      ben+workflowy@solidstategroup.com
    </ownerEmail>
  </head>
  <body>
    <outline text="23r23r23r">
      <outline text="weoufgwiufgweiuogf" />
    </outline>
    <outline text="erghoiergiophergpiherg">
      <outline text="warogjerwegw" />
      <outline text="egp" />
    </outline>
    <outline text="er[go" />
  </body>
</opml>

@zadam
Copy link
Owner

zadam commented Jan 8, 2019

Hmm, this looks exactly like OPML v1 except for the version field.

What I heard some time ago is that OMPL 2.0 implementations differ greatly from the standard and that's a reason I'm trying to get some real world samples ...

@dabeeeenster
Copy link
Author

If I edit the 2.0 to 1.0 I still get nothing imported?

@washere
Copy link

washere commented Jan 8, 2019

importing small files from Notecase Pro works but big files from Notecase Pro often fail.

@zadam
Copy link
Owner

zadam commented Jan 8, 2019

Hmm, when I changed it to 1.0 it didn't import correctly because of missing "title" attribute in the outline nodes. But after filling that attribute in, it imported correctly ...

@zadam zadam added this to the milestone 30 milestone Feb 3, 2019
zadam added a commit that referenced this issue Feb 16, 2019
@zadam
Copy link
Owner

zadam commented Feb 16, 2019

fixed in master

@zadam zadam closed this as completed Feb 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants