OPML files no longer exploding on import

A few months ago, I was having a grand time exporting outlines from Tinderbox as OPML, and the importing these into DT—where they converted into nested outlines made of groups or plain-text files (which I then converted to groups and tucked, using AppleScript). Just now, I tried to import an OPML file and it remained an OPML after import. I did this via dragging, and then using File > Import.

I asked ChatGPT what the hell is going on, and it told me to use “Import at OPML.” Did that option used to exist? I don’t remember.

Anyway, have other people noticed OPML files remaining intact now?

Searching for OPML in the forum turns up

perhaps that helps.

Incredible That’s the ticket! Thanks a billion!

You know, I saw that title and thought, “Too bad it’s the opposite problem. So close, but useless.” And there it was—the answer in reverse:

b2$ defaults write com.devon-technologies.think3 RawOPMLImport -bool FALSE

Thanks again!

A hallucination.

b2$ defaults write com.devon-technologies.think3 RawOPMLImport -bool FALSE

RawOPMLImport isn’t enabled by default. I just dragged and dropped an OPML file into DEVONthink on Ventura and it converted it into multiple .txt files.

What OS are you running?

1 Like

I would not rely on ChatGPT to tell me anything about DEVONthink. I would just search the forum or the manual.

5 Likes

Yes, my trust of GPT overrode my own memory. It was a mini-Mandela Effect. Until I read the other forum question that I initially cursed as being close-but-useless.

MBP 16”/2021, 16GB
macOS 12.7.6

1 Like