You are about to edit a ShadowTiddler. Any changes will override the default system making future upgrades non-trivial. Are you sure you want to edit "$:/core/save/all"?
Caution: Defining the wrong save-filter may have you unknowingly lose data!
I'm currently using unordered lists on my tiddlers for linking to "sub-types", which of course are also listed in my TOC in the SideBar. While I'm building my knowledgebase wiki, having the static links on the tiddler is handy because I create the new tiddlers for the sub-types by clicking on redlinks (oh how I wish TW would identify missing pages with a red link, rather than italics, but I must remember that TW != MW). But once I have my wiki in a more complete state, I'll probably go back and make those static lists dynamic using the macrocall you linked to above.
a.tc-tiddlylink-missing {
font-style: italic;
}
a.tc-tiddlylink-missing {
color: #FF0000;
}
Thanks Andrew, Mat and Greg for all the replies. I'm obviously not the first person to ask this question, and I did try to search the forums first before asking, but I couldn't find anything that addressed just the state of the TOC, as Mat alludes to above.
I made the change (that Andrew linked to) in my dev wiki first, to see what would happen. I got a message saying...You are about to edit a ShadowTiddler. Any changes will override the default system making future upgrades non-trivial. Are you sure you want to edit "$:/core/save/all"?
So let me make sure I understand what this means. Whenever I edit a system tiddler (shadow tiddler?) I'm going to need to document what I've done, so that when a new version of TW is rolled out, I can go back through my list of personalisations and re-apply them to the latest version.
@Greg: The link to Tobi's tiddler about States and Temporary Tiddlers comes with this dire warning:Caution: Defining the wrong save-filter may have you unknowingly lose data!
As I'm still very new to all this, and don't really know the structure of the underlying TW system well, I'm probably better off avoiding that one for now. But thanks anyway Greg.
And thanks @Mat for your wonderful feedback, which I have posted to the Google+ TiddlyWiki community. I'm glad that my questions and observations are useful. Sorry if I seem like a grumpy old man sometimes, but that's me in real life, haha.
I made the change (that Andrew linked to) in my dev wiki first, to see what would happen. I got a message saying...You are about to edit a ShadowTiddler. Any changes will override the default system making future upgrades non-trivial. Are you sure you want to edit "$:/core/save/all"?
So let me make sure I understand what this means. Whenever I edit a system tiddler (shadow tiddler?) I'm going to need to document what I've done, so that when a new version of TW is rolled out, I can go back through my list of personalisations and re-apply them to the latest version. Does that about sum it up?
Sorry, but, WTF?! I shouldn't have to alter the whole underlying system just to make a simple interface change. I'm going to end up with a huge list of personalisations to my wiki, and have to manage it, curate it, and reapply each one with copy/paste whenever a new version of TW becomes available. It would be far simpler to just go ahead and personalise my own copy of TW 5.1.9 and never upgrade it again! I assume thats why I see so many older copies of TW floating around online still, because its easier to keep personalisations than to upgrade, is that about right? I may be over-reacting to this, I often do. I have no experience with upgrading TW yet, so please let me know that what I imagine from that edit warning is not as bad as it seems.
@Greg: The link to Tobi's tiddler about States and Temporary Tiddlers comes with this dire warning:Caution: Defining the wrong save-filter may have you unknowingly lose data!
As I'm still very new to all this, and don't really know the structure of the underlying TW system well, I'm probably better off avoiding that one for now. But thanks anyway Greg.
Shadow Status
The tiddler HelloThere is not a shadow tiddler
- open http://tiddlywiki.com/#%24%3A%2FAcknowledgements
- (i) info: Advanced shows
Shadow Status
The tiddler $:/Acknowledgements is a shadow tiddler
It is defined in the plugin $:/core
- if you edit the tiddler it shows the "overwrite" warning
- save
- (i) info: Advanced shows
Shadow Status
The tiddler $:/Acknowledgements is a shadow tiddler
It is defined in the plugin $:/core
It is overridden by an ordinary tiddler <- this info is new.
That's the downside of warnings :) They may prevent experimentation.
Thanks for the replies everyone.
On Thursday, September 17, 2015 at 8:12:07 PM UTC+12, PMario wrote:That's the downside of warnings :) They may prevent experimentation.
Oh, I'm all in favor of hacking up my stuff, don't worry about that. I maintain a completely separate instance of TW specifically for experimentation before I make a change to my main "production" wiki, and both "dev" and "live" are backed up regularly. I was just expressing my doubts about my own competence with TW so far, because I haven't experimented enough with it as yet to be confident that I understand the implications of what I'm doing yet. Gimme time to get to know TW a little more before I attempt something that is labeled as "could break something serious", haha.
Also, as much as I'm spending time learning the finer points of TW, I'm also working slavishly to enter raw content into my "live" version of TW, the plain content that doesn't involve any coding, just text, formatting, categories and links. I'm balancing my time between that and experimentation, beginning to explore the possibilities and limitations of TW.
<$button>
<$action-deletetiddler $filter="[search:title[$:/state/toc/]]"/>
Delete TOC State
</$button>
<$button>
<$action-deletetiddler $filter="[prefix[$:/state/toc/]]"/>
Delete TOC State
</$button>
<$button message="tm-save-wiki" param={{$:/config/SaveWikiButton/Template}} tooltip={{$:/language/Buttons/SaveWiki/Hint}} aria-label={{$:/language/Buttons/SaveWiki/Caption}} class=<<tv-config-toolbar-class>>>
<$action-deletetiddler $filter="[prefix[$:/state/toc/]]"/>
<span class="tc-dirty-indicator">
<$list filter="[<tv-config-toolbar-icons>prefix[yes]]">
{{$:/core/images/save-button}}
</$list>
<$list filter="[<tv-config-toolbar-text>prefix[yes]]">
<span class="tc-btn-text"><$text text={{$:/language/Buttons/SaveWiki/Caption}}/></span>
</$list>
</span>
</$button>
<$list filter="[search:title[$:/state/toc/]]"/>
Action this immediately prior to saving -- or else you might prefer to construct a custom 'Save-Wiki' button, which includes this code:<$button message="tm-save-wiki" param={{$:/config/SaveWikiButton/Template}} tooltip={{$:/language/Buttons/SaveWiki/Hint}} aria-label={{$:/language/Buttons/SaveWiki/Caption}} class=<<tv-config-toolbar-class>>><$action-deletetiddler $filter="[prefix[$:/state/toc/]]"/><span class="tc-dirty-indicator"><$list filter="[<tv-config-toolbar-icons>prefix[yes]]">{{$:/core/images/save-button}}</$list><$list filter="[<tv-config-toolbar-text>prefix[yes]]"><span class="tc-btn-text"><$text text={{$:/language/Buttons/SaveWiki/Caption}}/></span></$list></span></$button>
It does seem to be a better, more specific solution than the one I'm using at the moment, suggested by @Andrew, which, as @Mat pointed out, prevents anything from $:/temp/ and $:/state/ from being saved, which could have unintended consequences. I'd like to try using your suggestion, but where do I put it to make it work?
Caution: Defining the wrong save-filter may have you unknowingly lose data!
<$button message="tm-save-wiki" param={{$:/config/SaveWikiButton/Template}} tooltip={{$:/language/Buttons/SaveWiki/Hint}} aria-label={{$:/language/Buttons/SaveWiki/Caption}} class=<<tv-config-toolbar-class>>>
<$action-deletetiddler $filter="[prefix[$:/state/toc/]]"/>
<span class="tc-dirty-indicator">
<$list filter="[<tv-config-toolbar-icons>prefix[yes]]">
{{$:/core/images/save-button}}
</$list>
<$list filter="[<tv-config-toolbar-text>prefix[yes]]">
<span class="tc-btn-text"><$text text={{$:/language/Buttons/SaveWiki/Caption}}/></span>
</$list>
</span>
</$button>
{{$:/_Buttons/SaveWiki}}
<$checkbox tiddler="$:/_Buttons/SaveWiki" tag="$:/tags/PageControls">Toggle Save Wiki Button</$checkbox>
What I was not suggesting was that it should be unsafe in any way to remove any tiddlers prefixed $:/temp/ or $:/state/, which it should not, unless someone is using these namespaces for the wrong purposes ...so, I am doing that by default on tb5.