OK Charlie: can't say as i understand much of this, but the fact that you've been able to replicate that JavaScript error - saving to your local downloaded instance of mine (as you lack edit perms on the hosted instance) i presume- leads me to believe that it's not a Tiddlyhost thing, but rather something else. Does this mean that Relink plugin doesn't like the fact of this new UID field, i wonder? If so, that's a real problem, because Relink is for me an essential part of this mix.
I see it like this: one of TW's superpowers is the ability to create AND modify content (including tiddler titles: a vital content element) so dynamically. Problem is that the title field is in effect the primary key of these tiddler entities, so if you change that, you break a whole lot of links in a typically "intertwingled" wiki. Relink plugin provides a fine solution to this problem internally... But as far as links-in from the ouside world are concerned, they must remain unchanged from the time that you publish them in perpetuity; this is precisely the ProblemOfLinkRot that drives my interest in using some other field that would survive a title change (or any change in other content) as the UID for published Permalinks. So: gosh, this is vexing. Your solution ticks a lot of boxes, Charlie: nice compact URL, smartly integrated in UI (your decision about nesting the control in such a way that is reasonably accessible to editors while obscuring it from the superficial view of more casual wiki-browsers strikes me as wise)... And the fact that it doesn't involve any modification of Core elements means it won't interfere w/ TW's nice easy upgrade mechanics, or complicate the lives of busy Core devs who would have to work around that somehow. If we can get it to play nicely with Relink tho, then it's a non-starter, from my perspective. Would love to hear your thoughts about this. /walt On Sunday, May 9, 2021 at 3:25:25 AM UTC+1 [email protected] wrote: > I removed all of the UID tiddlers from your TiddlyWiki, and I get a > consistent javascript error trying to rename the tiddler "PermaLinkCharlie". > > The javascript error stops happening after I remove the "PermaLinkCharlie" > reference from the text of your "SolutionToProblemOfLinkRot" tiddler. > > It looks like Relink is giving a javascript error when trying to rename a > tiddler (let's call it Tiddler A) that has a CamelCase title WHEN there are > any other tiddlers that have Tiddler A's CamelCase title in any field that > Relink scans. > > On Saturday, May 8, 2021 at 4:10:40 PM UTC-3 ludwa6 wrote: > >> You're a wizard, Charlie! Problem is, these magic spells invoked in an >> unforseen context can yield unexpected results. >> >> At least the first step -getting a PermaLink to a newly created tiddler- >> worked fine: see https://meta.tiddlyhost.com/#:[uid[3]] >> (NB: that one is #3, because tiddlers 1 & 2 got flubbed, because i forgot >> that Tiddlyhost needs me to save not just tiddler, but then the whole >> wiki... And so i ran the script twice on same tiddler, and now both 1&2 >> pull blanks). >> >> But then at step two -changing the title of tiddler- it threw me this >> error message when i tried to save tiddler: >> >> * Internal JavaScript Error: Uncaught TypeError: cannot read property >> '1' of undefined When relinking 'SolutionToProblemOfLinkRot'* >> Because the tiddler in step 1 above has a backlink to this other >> 'SolutionToProblemOfLinkRot' -but i don't know if it's that Tiddlyhost >> doesn't like the UID attribute, or has a problem with the "Relink" plugin i >> have installed. >> >> Anyway: i will try some other tests tomorrow; just thought to share this >> one now, while it's fresh. >> ps: can't wait to see this next video! :-) >> >> /walt >> >> On Saturday, May 8, 2021 at 6:14:30 PM UTC+1 [email protected] wrote: >> >>> Arg. I should have mentioned. The "ViewToolbar" button to add a UID to >>> a tiddler is in the "More" button's menu. >>> >>> I decided to make it a little bit more difficult to reach, because when >>> a TiddlyWiki is publicly hosted on the web, we don't want viewers creating >>> UID's on tiddler's and then grabbing UID permalinks, thinking they can >>> directly open a TiddlyWiki to that particular tiddler. >>> >>> I'll try to remember going over that in next video. >>> >>> >>> >>> On Saturday, May 8, 2021 at 1:54:46 PM UTC-3 Charlie Veniot wrote: >>> >>>> Okay, for anybody who wants to play, please find the attached JSON, a >>>> package of 9 small tiddlers ready for importing into your own test >>>> TiddlyWiki. >>>> >>>> After you import the attached JSON tiddler, open it to import the >>>> individual tidders. >>>> >>>> I've made a few changes, and will discuss them in a new video today, or >>>> tomorrow, or within the next few days. >>>> >>>> In the meantime, please give it a spin and let me know what breaks or >>>> gets broken. >>>> >>>> Cheers ! >>>> >>>> >>>> >>>> >>>> >>>> On Saturday, May 8, 2021 at 12:24:47 PM UTC-3 Charlie Veniot wrote: >>>> >>>>> Tidflix ? >>>>> >>>>> On Saturday, May 8, 2021 at 12:22:28 PM UTC-3 David Gifford wrote: >>>>> >>>>>> The beginnings of the TiddlyWiki Cinematic Universe >>>>>> >>>>>> On Wednesday, May 5, 2021 at 8:18:52 PM UTC-5 [email protected] >>>>>> wrote: >>>>>> >>>>>>> What the heck, I ask for forgiveness rather than for permission. >>>>>>> >>>>>>> I'm thinking this may be worth a distinct thread in case it >>>>>>> generates loads of questions/comments. >>>>>>> >>>>>>> YouTube video based on the conversation in Relink vs Permalinks >>>>>>> <https://groups.google.com/g/tiddlywiki/c/QOzs3CVtosU> : >>>>>>> >>>>>>> TiddlyWiki: A Prototype of UID's for stable permalinks >>>>>>> <https://youtu.be/UOFqXoyEU4I> >>>>>>> >>>>>> -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/394b2ffd-6f97-41b3-8570-ec32e2c3934bn%40googlegroups.com.
