scripting
File/Include Opml... not working as documented
The online documentation for the "File/IncludeOpml..." command recorded in http://docserver.scripting.com/drummer/files.opml states:
"When you expand the headline, Drummer reads the outline and shows you its contents. Later, if you collapse the headline and re-expand it, Drummer will read it again, and if it has changed you'll see the changes."
This outline http://drummer.scripting.com/davidlu/tunetextReflection.opml has been made public.
It consists only of a single "include opml" link to the outline http://drummer.scripting.com/davidlu/tunetextLore.opml which has also been made public.
If you execute the "File/View Opml..." command while viewing tunetextReflection.opml, it currently reports that we are viewing a version of the opml from yesterday:
<dateCreated>Mon, 22 Nov 2021 07:25:33 GMT</dateCreated>
If I collapse everything in tunetextReflection.opml, expand everything, collapse the "include opml" link a second time and then double click on the icon that is displayed to the left of the included text, an Opml view is launched which shows the Opml for the most recent version of the http://drummer.scripting.com/davidlu/tunetextLore.opml outline:
<dateModified>Tue, 23 Nov 2021 23:42:51 GMT</dateModified>
Looking at the expansion of "include opml" link visible within tunetextReflection.opml, it is clear that Drummer is still displaying the version of the outline from <dateCreated>Mon, 22 Nov 2021 07:25:33 GMT</dateCreated> when I would expect the outline from <dateModified>Tue, 23 Nov 2021 23:42:51 GMT</dateModified> to be displayed as the inclusion within the tunetextReflection.opml outline.
You can verify that we are seeing the day old version of the inclusion because nothing with a Tue, 23 Nov 2021 datestamp shows in the Opml shown for the re-expanded outline, when more than 50 outline levels have a "Tue, 23 Nov 2021" datestamp in the expected inclusion.
Dave it’s almost certainly your browser caching the file. But it may be possible to work around that.
I did see similar behavior when I served that same document through PagePark.
In that case, I accessed via Electric Drummer a copy of tunetextReflection.opml that I had moved into Page Park's localhost domain folder , and did the collapse/expand sequence there in the standalone app, which still did not cause the image of the inclusion to be brought up to date, which was the behavior I'd hoped I would see.
Also noted that when I first established my inclusion using Drummer on Firefox, none of the text that I believe should have been included immediately was brought into the outline that was including it. After creating it, I tried serving it through a Page Park URL, which showed an empty result for the inclusion.
After waiting more than 36 hours, a version of the inclusion showed up in the tunetextRefelction.opml that was served by Page Park, when I tried it after letting it lay fallow. Not sure what caused that update to occur.