Is anyone having trouble loading .opml files?

I have a report where Bike is failing to open the attached OPML file. Seems to work fine for me. Anyone else noticed problems opening OPML files in Bike?

abc.opml.zip (1.2 KB)

I have no problem opening the specific file you provided.

I also tried opening an iThoughts file (very large) exported as OPML. No problem opening. Any of the “notes” I had in iThoughts were lost, but the actual “nodes” opened as expected as an outline.

1 Like

No problem at all here in opening or re-saving that file.

  • macOS 11.6.7
  • Bike 1.3 (61)

(and no other OPML opening problems seen)

No problems here. Latest beta.

HI,
I’ve tried opening an OPML exported from Scapple v1.4.1 and I get the error message The document “test for opml export.opml” could not be opened.
It is a very simple document but Scapple may contain some odd stuff. I only use Scapple as it integrates with Scrivener.
R

Can you share a simple as possible Scapple document that reproduces this problem when exported as opml. I’ve tried a few very simple Scapple documents and Bike appears able to open their exported opml.

Perhaps you could zip that in the Finder with Ctr-click for a contextual menu, choosing Compress to make a zip copy, and drag it into a post in the thread here ?


OPML exported by Scrivener 3.2.3 on macOS 11.6.7 seems to be importing well here into Bike 1.3 (61)

Here is the file.

Jesse has already opened it at his end.
My copy of Bike wont open an OPML file produced by itself. I have no other software which produces OPML to test a different file.
R
test_for_opml_export.opml.zip (731 Bytes)

Also I am using Bike 1.3(61) and Mac OS 12.4

What results do you get when you open Terminal.app and use the mdls command to inspect the opml file path? For example I see:

jessegrosjean@Jesses-MacBook-Pro Desktop % mdls Scapple.opml
_kMDItemDisplayNameWithExtensions      = "Scapple.opml"
kMDItemAlternateNames                  = (
    "Scapple.opml"
)
kMDItemContentCreationDate             = 2022-07-06 11:11:55 +0000
kMDItemContentCreationDate_Ranking     = 2022-07-06 00:00:00 +0000
kMDItemContentModificationDate         = 2022-07-06 11:11:55 +0000
kMDItemContentModificationDate_Ranking = 2022-07-06 00:00:00 +0000
kMDItemContentType                     = "org.opml.opml"
kMDItemContentTypeTree                 = (
    "org.opml.opml",
    "public.xml",
    "public.text",
    "public.data",
    "public.item",
    "public.content"
)
kMDItemDateAdded                       = 2022-07-06 11:11:55 +0000
kMDItemDateAdded_Ranking               = 2022-07-06 00:00:00 +0000
kMDItemDisplayName                     = "Scapple"
kMDItemDocumentIdentifier              = 0
kMDItemFSContentChangeDate             = 2022-07-06 11:11:55 +0000
kMDItemFSCreationDate                  = 2022-07-06 11:11:55 +0000
kMDItemFSCreatorCode                   = ""
kMDItemFSFinderFlags                   = 16
kMDItemFSHasCustomIcon                 = (null)
kMDItemFSInvisible                     = 0
kMDItemFSIsExtensionHidden             = 1
kMDItemFSIsStationery                  = (null)
kMDItemFSLabel                         = 0
kMDItemFSName                          = "Scapple.opml"
kMDItemFSNodeCount                     = (null)
kMDItemFSOwnerGroupID                  = 20
kMDItemFSOwnerUserID                   = 501
kMDItemFSSize                          = 250
kMDItemFSTypeCode                      = ""
kMDItemInterestingDate_Ranking         = 2022-07-06 00:00:00 +0000
kMDItemKind                            = "OPML"
kMDItemLastUsedDate                    = 2022-07-06 11:12:00 +0000
kMDItemLastUsedDate_Ranking            = 2022-07-06 00:00:00 +0000
kMDItemLogicalSize                     = 250
kMDItemPhysicalSize                    = 4096
kMDItemUseCount                        = 6
kMDItemUsedDates                       = (
    "2022-07-06 04:00:00 +0000"
)
jessegrosjean@Jesses-MacBook-Pro Desktop % 

Another thing to test… what happens if you rename that opml file to have a txt file extension instead of an opml file extension?

I have no problem opening the test_for_… opml file in Bike.

OK. changing to .txt and Bike opens the file.

Running terminal command results below.
I can see the kMDItemContentTypeTree is different

*****:~ $ mdls /Users//Desktop/test_for_opml_export.opml
_kMDItemDisplayNameWithExtensions = “test_for_opml_export.opml”
kMDItemContentCreationDate = 2022-07-06 11:01:25 +0000
kMDItemContentCreationDate_Ranking = 2022-07-06 00:00:00 +0000
kMDItemContentModificationDate = 2022-07-06 11:01:25 +0000
kMDItemContentModificationDate_Ranking = 2022-07-06 00:00:00 +0000
kMDItemContentType = “dyn.ah62d4rv4ge8086drru”
kMDItemContentTypeTree = (
“public.item”,
“dyn.ah62d4rv4ge8086drru”,
“public.data”
)
kMDItemDateAdded = 2022-07-06 11:26:07 +0000
kMDItemDateAdded_Ranking = 2022-07-06 00:00:00 +0000
kMDItemDisplayName = “test_for_opml_export.opml”
kMDItemDocumentIdentifier = 0
kMDItemFSContentChangeDate = 2022-07-06 11:01:25 +0000
kMDItemFSCreationDate = 2022-07-06 11:01:25 +0000
kMDItemFSCreatorCode = “”
kMDItemFSFinderFlags = 0
kMDItemFSHasCustomIcon = (null)
kMDItemFSInvisible = 0
kMDItemFSIsExtensionHidden = 0
kMDItemFSIsStationery = (null)
kMDItemFSLabel = 0
kMDItemFSName = “test_for_opml_export.opml”
kMDItemFSNodeCount = (null)
kMDItemFSOwnerGroupID = 20
kMDItemFSOwnerUserID = 502
kMDItemFSSize = 286
kMDItemFSTypeCode = “”
kMDItemInterestingDate_Ranking = 2022-07-06 00:00:00 +0000
kMDItemKind = “Document”
kMDItemLastUsedDate = 2022-07-06 14:11:52 +0000
kMDItemLastUsedDate_Ranking = 2022-07-06 00:00:00 +0000
kMDItemLogicalSize = 286
kMDItemPhysicalSize = 4096
kMDItemUseCount = 6
kMDItemUsedDates = (
“2022-07-05 23:00:00 +0000”
)
*****:~ *****$

Good news is found a fix… Bike is declaring opml universal type identifier incorrectly… :frowning: and that causes the problem. But it’s an easy fix on my end.

I think the reason it doesn’t happen on most Bike users computers might be that they already have other apps that declare opml identifier correctly, and that’s what is used. Just a guess.

1 Like

I’ve just posted a new preview release here that I think fixes the issue:

1 Like

Hi Jesse,

The link for the preview download goes to the regular download link.
This provides the 1.3(61) app.

R

In Bike Preferences > General check “Include Preview Releases” and then check for updates to get the latest preview.

I’m not sure what to do about that link… I include it because I think somewhat often people who have never used Bike come directly to a release post… but there’s no easy path to download Bike, so I provide like to latest release. I don’t want to link directly to the release because often I’ll delete a few preview releases and that will create broken links.

I’ll update the wording on that link to make things clearer.