Re: [tw] [Node.js] Unable to update past 5.1.13

[William RENOU]

I created a new TW and progressively copied my tiddlers over to it, first 
installing the same plugins I had then moving standard tiddlers, macro / 
template tiddlers and checking each time if it broke it. Since it still 
worked fine I used your method (because I really don't like fixing 
something and not understanding how I did it), plugin to blame was a 
language plugin. I had forgotten about this one & feel kind of dumb not to 
have checked this one.

Le mercredi 22 novembre 2017 10:27:48 UTC+1, Jeremy Ruston a écrit :
>
> Hi William
>
> The first error looks as though TiddlyWiki is trying to use the PUT saver 
> to save changes. That suggests that maybe you have not got the required 
> tiddlyweb plugin loaded. The plugins you’re using should be entered into 
> the tiddlywiki.info file for your wiki:
>
>
> https://tiddlywiki.com/#Installing%20a%20plugin%20from%20the%20plugin%20library
>
> The second error looks like maybe you’ve got a 5.1.13 plugin loaded as a 
> literal tiddler. It won’t get updated when you upgrade because it’s a 
> literal tiddler rather than a reference in the tiddlywiki.info file.
>
> If the system will let you, you can use the $:/AdvancedSearch “Filter" tag 
> to help track this down:
>
> First, the following filter expression will list all of the different 
> values for the “version” field of the loaded plugins:
>
> [all[tiddlers]each[version]get[version]]
>
> If you see “5.1.13” listed then you can identify the specific rogue plugin 
> with the following expression that lists all of the plugins with the 
> “version” field set to 5.1.13:
>
> [all[tiddlers]version[5.1.13]]
>
> If none of that helps then I think you might be best starting with a new 
> wiki and progressively bringing your content over until you can see what 
> breaks.
>
> Best wishes
>
> Jeremy.
>
>
> On 22 Nov 2017, at 03:24, William RENOU <wilr...@gmail.com > 
> wrote:
>
> Hello. 
> I was running on 5.1.13 and decided to upgrade my server to 5.1.15 after 
> testing it for a bit. Unfortunately since the upgrade it has become mostly 
> unusable. I can open my TW fine but when used, most functions return a 
> javascript error. Even only opening the TW yield errors. 
>
> $:/core/modules/utils/dom/http.js:65 
> OPTIONS http://host/path/ 404 (Not Found)
>  exports.httpRequest @ $:/core/modules/utils/dom/http.js:65
>  PutSaver @ $:/core/modules/savers/put.js:28
>  exports.create @ $:/core/modules/savers/put.js:108
>  (anonymous) @ $:/core/modules/saver-handler.js:122
>  (anonymous) @ (index):24882
>  $tw.utils.each @ (index):24213
>  $tw.modules.forEachModuleOfType @ (index):24881
>  SaverHandler.initSavers @ $:/core/modules/saver-handler.js:120
>  SaverHandler @ $:/core/modules/saver-handler.js:30
>  exports.startup @ $:/core/modules/startup.js:115
>  $tw.boot.executeNextStartupTask @ (index):26094
>  $tw.boot.executeNextStartupTask @ (index):26098
>  $tw.boot.executeNextStartupTask @ (index):26098
>  $tw.boot.startup @ (index):26051
>  (anonymous) @ (index):26200
>  $tw.boot.decryptEncryptedTiddlers @ (index):25479
>  $tw.boot.boot @ (index):26198
>  _boot @ (index):26207
>  (anonymous) @ (index):26217
>
> $:/core/modules/utils/dom/http.js:65 HEAD http://host/path/ 404 (Not 
> Found)
>  exports.httpRequest @ $:/core/modules/utils/dom/http.js:65
>  PutSaver @ $:/core/modules/savers/put.js:39
>  exports.create @ $:/core/modules/savers/put.js:108
>  (anonymous) @ $:/core/modules/saver-handler.js:122
>  (anonymous) @ (index):24882
>  $tw.utils.each @ (index):24213
>  $tw.modules.forEachModuleOfType @ (index):24881
>  SaverHandler.initSavers @ $:/core/modules/saver-handler.js:120
>  SaverHandler @ $:/core/modules/saver-handler.js:30
>  exports.startup @ $:/core/modules/startup.js:115
>  $tw.boot.executeNextStartupTask @ (index):26094
>  $tw.boot.executeNextStartupTask @ (index):26098
>  $tw.boot.executeNextStartupTask @ (index):26098
>  $tw.boot.startup @ (index):26051
>  (anonymous) @ (index):26200
>  $tw.boot.decryptEncryptedTiddlers @ (index):25479
>  $tw.boot.boot @ (index):26198
>  _boot @ (index):26207
>  (anonymous) @ (index):26217
>
> I first thought plugins were to blame so I disabled them, no effect. I 
> then downgraded to .14 and again to .13 since .14 was showing the exact 
> same symptoms. Returning to .13 showed my TW back to functionnal status.
> As a test I tried to create a new TW under .15 and it is working fine, 
> meaning my issue was a configuration issue on my TW folders. The error 
> typically triggers when I open the Recent Sidebar tab.
> Most errors I get during use are like this one :
> (index):24287 Uncaught TypeError: Cannot read property 'day' of undefined
> $tw.utils.error @ (ind

[tw] [Node.js] Unable to update past 5.1.13

[William RENOU]

Hello. 
I was running on 5.1.13 and decided to upgrade my server to 5.1.15 after 
testing it for a bit. Unfortunately since the upgrade it has become mostly 
unusable. I can open my TW fine but when used, most functions return a 
javascript error. Even only opening the TW yield errors. 

$:/core/modules/utils/dom/http.js:65 
OPTIONS http://host/path/ 404 (Not Found)
 exports.httpRequest @ $:/core/modules/utils/dom/http.js:65
 PutSaver @ $:/core/modules/savers/put.js:28
 exports.create @ $:/core/modules/savers/put.js:108
 (anonymous) @ $:/core/modules/saver-handler.js:122
 (anonymous) @ (index):24882
 $tw.utils.each @ (index):24213
 $tw.modules.forEachModuleOfType @ (index):24881
 SaverHandler.initSavers @ $:/core/modules/saver-handler.js:120
 SaverHandler @ $:/core/modules/saver-handler.js:30
 exports.startup @ $:/core/modules/startup.js:115
 $tw.boot.executeNextStartupTask @ (index):26094
 $tw.boot.executeNextStartupTask @ (index):26098
 $tw.boot.executeNextStartupTask @ (index):26098
 $tw.boot.startup @ (index):26051
 (anonymous) @ (index):26200
 $tw.boot.decryptEncryptedTiddlers @ (index):25479
 $tw.boot.boot @ (index):26198
 _boot @ (index):26207
 (anonymous) @ (index):26217

$:/core/modules/utils/dom/http.js:65 HEAD http://host/path/ 404 (Not Found)
 exports.httpRequest @ $:/core/modules/utils/dom/http.js:65
 PutSaver @ $:/core/modules/savers/put.js:39
 exports.create @ $:/core/modules/savers/put.js:108
 (anonymous) @ $:/core/modules/saver-handler.js:122
 (anonymous) @ (index):24882
 $tw.utils.each @ (index):24213
 $tw.modules.forEachModuleOfType @ (index):24881
 SaverHandler.initSavers @ $:/core/modules/saver-handler.js:120
 SaverHandler @ $:/core/modules/saver-handler.js:30
 exports.startup @ $:/core/modules/startup.js:115
 $tw.boot.executeNextStartupTask @ (index):26094
 $tw.boot.executeNextStartupTask @ (index):26098
 $tw.boot.executeNextStartupTask @ (index):26098
 $tw.boot.startup @ (index):26051
 (anonymous) @ (index):26200
 $tw.boot.decryptEncryptedTiddlers @ (index):25479
 $tw.boot.boot @ (index):26198
 _boot @ (index):26207
 (anonymous) @ (index):26217

I first thought plugins were to blame so I disabled them, no effect. I then 
downgraded to .14 and again to .13 since .14 was showing the exact same 
symptoms. Returning to .13 showed my TW back to functionnal status.
As a test I tried to create a new TW under .15 and it is working fine, 
meaning my issue was a configuration issue on my TW folders. The error 
typically triggers when I open the Recent Sidebar tab.
Most errors I get during use are like this one :
(index):24287 Uncaught TypeError: Cannot read property 'day' of undefined
$tw.utils.error @ (index):24287
window.onerror @ (index):24314
setTimeout (async)
exports.nextTick @ $:/core/modules/utils/utils.js:584
exports.enqueueTiddlerEvent @ $:/core/modules/wiki.js:152
deleteTiddler @ (index):25065
Popup.cancel @ $:/core/modules/utils/dom/popup.js:144
Popup.handleEvent @ $:/core/modules/utils/dom/popup.js:69
$:/core/modules/tiddler.js:138 Uncaught TypeError: Cannot read property 
'day' of undefined
at $tw.Tiddler.exports.getFieldDay ($:/core/modules/tiddler.js:138)
at eval ($:/core/modules/filters/sameday.js:26)
at each ((index):25093)
at exports.sameday ($:/core/modules/filters/sameday.js:24)
at eval ($:/core/modules/filters.js:207)
at Object.$tw.utils.each ((index):24224)
at operationSubFunction ($:/core/modules/filters.js:190)
at eval ($:/core/modules/filters.js:238)
at eval ($:/core/modules/filters.js:263)
at Object.$tw.utils.each ((index):24224)
I could rollback to .13 and keep using my TW, but I'd really like to fix 
them as there are a few things the updates added I could use. 

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/e6dfbfe1-c047-4adc-8267-7b63251a98f0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Not sure how to proceed

[William RENOU]

I tried installing a pluging on a working node.js tiddlywiki (running 
5.1.13).
First I wasn't sure if you had to both add the plugins through the 
ControlPanel and in the tiddlywiki.info file.
As it got me errors upon accessing the tiddlywiki, I guessed the 
ControlPanel part was wrong.
I restored my tiddlywiki (I had it backed up before trying anything, as I 
usually break everything I try to touch).
The tiddlywiki loads & works fine.
If I shut down the server, edit the tiddlywiki.info file to add the plugins 
to the plugins subsection, then save the file & launch the server again, no 
plugin is loaded.
Accessing the ControlPanel shows only the base plugins (tiddlyweb, 
filesystem, highlight and core [which is not listed in tiddlywiki.info]).

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/1d6c78e7-1b60-4b51-beda-40b740db9674%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] MacroCall Widget & sub-macros

[William RENOU]

I got it from what was used as 3rd example 
on http://tiddlywiki.com/#MacroCallWidget. Looks like there are a few 
errors on it. It works now, thanks.

Le lundi 12 décembre 2016 05:10:48 UTC+1, Mark S. a écrit :
>
> Even though they may sometimes seem to perform as functions, macros just 
> support text substitution. Your version would have had a widget inside of a 
> widget, which probably won't work, except on the 2nd Tuesday of months with 
> full moons. Or something. I don't quite have it right yet.
>
> This code seems to work. Hopefully it will be close to what you need:
>
> \define myDataMacro(var2) <$transclude tiddler="$:/data/dataExample" index
> ={{$var2$!!keyfield}} />
>
>
> <$macrocall $name="myDataMacro"  var2={{!!mytarget}} />
>
>
>
>
> On Sunday, December 11, 2016 at 5:47:47 PM UTC-8, William RENOU wrote:
>>
>> I'm currently trying to link a tiddler's field to a DataTiddler 
>> (dictionary tiddler). My (semi) working prototype has a SelectWidget 
>> pulling up a list of Tiddlers. When one is selected, its fields are 
>> displayed. The title of the current displayed tiddler is stored in a field 
>> inside the viewer tiddler. One of these fields is codified (to save time 
>> when editing this type of tiddler & to save time in case of field 
>> codification changes). This field key values are stored in a Dictionary 
>> Data Tiddler. My goal is to display the value of the field instead of its 
>> stored key. 
>> I use two macros to do so :
>>
>>- To retrieve the key to look for 'in the data tiddler) stored in the 
>>target tiddler
>>
>> \define targetKey() <$transclude tiddler={{!!myTarget}} field="keyField"
>> />
>>
>>- I have a second macro that'll look for the value to be displayed in 
>>my Data Tiddler 
>>
>> \define myDataMacro(var:0) <$transclude tiddler="$:/data/dataExample" 
>> index=$var$/>
>>
>>- I globaly use them using a MacroCallWidget
>>
>> <$macrocall $name="myDataMacro" var=<>/>
>>
>>
>>- My Data Tiddler has currently these test values
>>
>> 0:White1:Green2:Blue3:Orange4:Red5:Yellow
>>
>>
>> My issue is the values aren't displayed. It should display the value 
>> associated with the correct key, e.g. : when I try it to select a test 
>> tiddler having "1" (without the quotes) as value for the *keyField* field, 
>> instead of displaying *Green *it displays its value *1.*
>> Using the MacroCallWidget without specifying the *var *variable displays 
>> correctly the default value set in the *myDataMacro. *Using a key 
>> instead of the sub-macro displays it's value correctly.
>>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/72acc0d6-c46d-4c39-abf8-c88198df9573%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] [TW5] MacroCall Widget & sub-macros

[William RENOU]

I'm currently trying to link a tiddler's field to a DataTiddler (dictionary 
tiddler). My (semi) working prototype has a SelectWidget pulling up a list 
of Tiddlers. When one is selected, its fields are displayed. The title of 
the current displayed tiddler is stored in a field inside the viewer 
tiddler. One of these fields is codified (to save time when editing this 
type of tiddler & to save time in case of field codification changes). This 
field key values are stored in a Dictionary Data Tiddler. My goal is to 
display the value of the field instead of its stored key. 
I use two macros to do so :

   - To retrieve the key to look for 'in the data tiddler) stored in the 
   target tiddler

\define targetKey() <$transclude tiddler={{!!myTarget}} field="keyField"/>

   - I have a second macro that'll look for the value to be displayed in my 
   Data Tiddler 

\define myDataMacro(var:0) <$transclude tiddler="$:/data/dataExample" index=
$var$/>

   - I globaly use them using a MacroCallWidget

<$macrocall $name="myDataMacro" var=<>/>


   - My Data Tiddler has currently these test values

0:White1:Green2:Blue3:Orange4:Red5:Yellow


My issue is the values aren't displayed. It should display the value 
associated with the correct key, e.g. : when I try it to select a test 
tiddler having "1" (without the quotes) as value for the *keyField* field, 
instead of displaying *Green *it displays its value *1.*
Using the MacroCallWidget without specifying the *var *variable displays 
correctly the default value set in the *myDataMacro. *Using a key instead 
of the sub-macro displays it's value correctly.

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/a4584345-a4cd-45fe-a005-1ffe855a4cb6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] [TW5] Node.js & multiple instances

[William RENOU]

Is there a way to run simultaneously several TW5 on the same node, except 
using a different port for each one ? I was looking for a way to make them 
run in different adresses :
- first TW on localhost/node1
- second TW on localhost/node2
- etc...

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/f34c8bcf-c24e-407f-b351-1981ca6a1167%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Multi-level transclusion

[William RENOU]

I tried putting the viewTiddler code from L1 directly into the tiddler, and 
it works perfectly. But I'd need to put the same code in each and every 
tiddler of the same type.
Possible workaround : instead of calling L2 through L1 from Root, maybe 
calling both of them from Root might work, like a nested list ?

Le lundi 1 août 2016 03:39:24 UTC+2, Mark S. a écrit :
>
> Well, I can see what the problem is, but I don't see what the solution is 
> other than putting a template (e.g. {{||L1Template}}) into each L1 object.. 
> Hopefully one of the gurus will have the magic.
>
> At the Level 1 level, the template works because the Level 2 objects have 
> actual content.
>
> At the Root level, it doesn't work (well, it works, but doesn't do what 
> you wanted it to do) because there's nothing actually in the Level 1 
> objects. You were hoping that it would bring in the rendered L1 objects, 
> but instead it's bringing in the *contents *of the L1 object(s) -- which 
> are empty.
>
> If there is a workaround that would allow you to bring in the rendered 
> contents of tiddler displayed via $:/tags/ViewTemplate it would be great to 
> learn about it.
>
> Good luck!
> Mark
>
> On Sunday, July 31, 2016 at 4:22:41 PM UTC-7, William RENOU wrote:
>>
>> Here's my root tiddler viewTemplate :
>> <$list filter="[is[current]tag[rootTag]]">
>>
>>   <$list filter="[tag[L1Tag]field:someField{!!title}]]">
>>
>> ! {{!!title}}
>> <<<
>> {{!!text}}
>> <<<
>>   
>>
>> 
>>
>> Here's my level 1 viewTemplate :
>> <$list filter="[is[current]tag[L1Tag]]">
>>
>>   <$list filter="[tag[L2Tag]field:someField{!!someValue}]">
>>
>> !! {{!!title}}
>> <<<
>> {{!!text}}
>> <<<
>>   
>>
>> 
>>
>> There's a field reference from level 1 tiddlers to the root Tiddler 
>> (using the root tiddler's title). Sames goes for L2 to L1 : it's 
>> referencing an ID on the L1 tiddler.
>> My first idea was to remove the block quotes, but it hasn't solved the 
>> issue of content not showing.
>>
>> Le lundi 1 août 2016 00:34:17 UTC+2, Eric Shulman a écrit :
>>>
>>> On Sunday, July 31, 2016 at 3:14:49 PM UTC-7, William RENOU wrote:
>>>>
>>>> I was wondering if transcluding content accross several levels was 
>>>> possible ? 
>>>> Here's what I'm trying to do :
>>>>
>>>> RootTiddler (A)
>>>> + L1SubTiddler (Aa)
>>>>   + L2SubTiddler (Aa1)
>>>>   + L2SubTiddler (Aa2)
>>>> + L1SubTiddler (Ab)
>>>>   + L2SubTiddler (Ab1)
>>>> + L1SubTiddler (Ac)
>>>>
>>>> Both root-level tiddlers and level 1 subtitlers are displayed using 
>>>> viewTemplates. Level 2 tiddlers are transcluded in their Level 1 parent, 
>>>> transcluded again in the root Tiddler. 
>>>> But for some reason, while directly viewing a L1 tiddler displays its 
>>>> L2 contents, opening the root Tiddler only displays the Level 1 contents.
>>>>
>>>
>>> Show some code, please.  Or, better still, post your document online 
>>> somewhere.
>>> Then perhaps we can see what you are *actually* doing... rather than 
>>> just reading a description of what you *want* to do.
>>>
>>> -e
>>> Eric Shulman
>>> TiddlyTools / ELS Design Studios
>>> InsideTiddlyWiki: The Missing Manuals
>>>
>>>
>>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/9b8c8cc3-17fe-470b-8b68-45a9fc720bdd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Multi-level transclusion

[William RENOU]

Here's my root tiddler viewTemplate :
<$list filter="[is[current]tag[rootTag]]">

  <$list filter="[tag[L1Tag]field:someField{!!title}]]">

! {{!!title}}
<<<
{{!!text}}
<<<
  



Here's my level 1 viewTemplate :
<$list filter="[is[current]tag[L1Tag]]">

  <$list filter="[tag[L2Tag]field:someField{!!someValue}]">

!! {{!!title}}
<<<
{{!!text}}
<<<
  



There's a field reference from level 1 tiddlers to the root Tiddler (using 
the root tiddler's title). Sames goes for L2 to L1 : it's referencing an ID 
on the L1 tiddler.
My first idea was to remove the block quotes, but it hasn't solved the 
issue of content not showing.

Le lundi 1 août 2016 00:34:17 UTC+2, Eric Shulman a écrit :
>
> On Sunday, July 31, 2016 at 3:14:49 PM UTC-7, William RENOU wrote:
>>
>> I was wondering if transcluding content accross several levels was 
>> possible ? 
>> Here's what I'm trying to do :
>>
>> RootTiddler (A)
>> + L1SubTiddler (Aa)
>>   + L2SubTiddler (Aa1)
>>   + L2SubTiddler (Aa2)
>> + L1SubTiddler (Ab)
>>   + L2SubTiddler (Ab1)
>> + L1SubTiddler (Ac)
>>
>> Both root-level tiddlers and level 1 subtitlers are displayed using 
>> viewTemplates. Level 2 tiddlers are transcluded in their Level 1 parent, 
>> transcluded again in the root Tiddler. 
>> But for some reason, while directly viewing a L1 tiddler displays its L2 
>> contents, opening the root Tiddler only displays the Level 1 contents.
>>
>
> Show some code, please.  Or, better still, post your document online 
> somewhere.
> Then perhaps we can see what you are *actually* doing... rather than just 
> reading a description of what you *want* to do.
>
> -e
> Eric Shulman
> TiddlyTools / ELS Design Studios
> InsideTiddlyWiki: The Missing Manuals
>
>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/647d2751-dd66-4482-b8b6-e617a0254b78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Multi-level transclusion

[William RENOU]

What more information do you need ?

Le lundi 1 août 2016 00:32:25 UTC+2, Jed Carty a écrit :
>
> What you want is almost certainly possible, but you need to give more 
> information about what is going on. You describe sometihng like how the 
> threaded comments are displayed in twederation here 
> , but I can't give you anything 
> specific without more information.
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/637ed343-2902-4c7a-991e-3540a8bf708f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] [TW5] Multi-level transclusion

[William RENOU]

I was wondering if transcluding content accross several levels was possible 
? 
Here's what I'm trying to do :

RootTiddler (A)
+ L1SubTiddler (Aa)
  + L2SubTiddler (Aa1)
  + L2SubTiddler (Aa2)
+ L1SubTiddler (Ab)
  + L2SubTiddler (Ab1)
+ L1SubTiddler (Ac)

Both root-level tiddlers and level 1 subtitlers are displayed using 
viewTemplates. Level 2 tiddlers are transcluded in their Level 1 parent, 
transcluded again in the root Tiddler. 
But for some reason, while directly viewing a L1 tiddler displays its L2 
contents, opening the root Tiddler only displays the Level 1 contents.

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/acb6eda8-85e5-4a5a-a4a0-8cc711701556%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Filtering out tag from tag list

[William RENOU]

Wasn't expecting it to be that simple. Big thanks for the quick reply :)

Le mardi 5 juillet 2016 01:58:51 UTC+2, Mark S. a écrit :
>
> Since you know the name of the tag you don't want, you can subtract it out:
>
> <$list filter="[is[current]tags[]] 
> -[[filterTagNotToDisplay]]">{{||$:/core/ui/TagTemplate}} 
>
> HTH
> Mark
>
> On Monday, July 4, 2016 at 4:49:48 PM UTC-7, William RENOU wrote:
>>
>> I am currently using a viewtemplate to display a list (filtered using a 
>> specific tag plus a few other operators) of tiddlers with their respective 
>> tags.
>> I'm using the listWidget inside my main listWidget to display the tags of 
>> each Tiddler.
>>
>> <$list filter="[tag[filterTagNotToDisplay]otherOperators]">
>> * <$list 
>> filter="[is[current]tags[]]">{{||$:/core/ui/TagTemplate}} 
>>
>> The issue (well not exactly a real issue since it's working perfectly 
>> fine) is all tags are displayed, even the one used in the main filter 
>> (which is somewhat pointless to display it since I'm interested in only 
>> having all the other tags).
>> I could very well let it as it is, but I was curious to know if there was 
>> a way to filter out an element from a list (the list here being tags) ?
>>
>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/a8254924-da21-4dc1-a00c-da5e86aa99d8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] [TW5] Filtering out tag from tag list

[William RENOU]

I am currently using a viewtemplate to display a list (filtered using a 
specific tag plus a few other operators) of tiddlers with their respective 
tags.
I'm using the listWidget inside my main listWidget to display the tags of 
each Tiddler.

<$list filter="[tag[filterTagNotToDisplay]otherOperators]">
* <$list filter="[is[current]tags[]]">{{||$:/core/ui/TagTemplate}} 

The issue (well not exactly a real issue since it's working perfectly fine) 
is all tags are displayed, even the one used in the main filter (which is 
somewhat pointless to display it since I'm interested in only having all 
the other tags).
I could very well let it as it is, but I was curious to know if there was a 
way to filter out an element from a list (the list here being tags) ?

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/ab17614e-3711-4e91-9a73-552fad0abd05%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] [TW5] Issues understanding filters

[William RENOU]

Now I understand why it stopped working when I upgraded it from 5.0.8 to 
5.1.11. Now I just need to get the 'is[current]' part.
Thanks.

Le vendredi 3 juin 2016 22:40:38 UTC+2, Jeremy Ruston a écrit :
>
> Hi William
>
> On 3 Jun 2016, at 19:14, William RENOU <wilr...@gmail.com > 
> wrote:
>
>  I've read all documentation on the operators used, but I have found 
> nothing regarding use of / in the field operator - hard and soft parameters 
> but nothing about / being used. The only two examples given in field 
> Operator documentation do not use /.
>
>
> The use of the backslash to quote filter operands is an old, deprecated 
> feature. The idea was to enable regular expressions to be used as filter 
> operands. The problem was that each and every filter operator needed to 
> explicitly implement support for regexps; that never happened for the core 
> because it’s too much work with little benefit. Instead, the recommended 
> alternative is to use the `regexp` filter operator.
>
> When we deprecated the regexp filter operand syntax we also added a 
> warning in the JavaScript console. You can see it by entering the sample 
> filter in the advanced search “filter” tab and checking the JS console:
>
> [is[current]field:fieldName1/fieldValue|fieldValue2/]
>
> Best wishes
>
> Jeremy.
>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/aefe3874-08e6-4ed0-a7eb-716131a0e34d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Issues understanding filters

[William RENOU]

Got this snippet from http://tesis.tiddlyspot.com/ > $:/_notes

Le vendredi 3 juin 2016 22:23:15 UTC+2, PMario a écrit :
>
> Hi William, 
>
> IMO it would be easier, if you tell us, where you found it. 
>
> -m
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/b17782c4-7256-4ed1-93ef-282b86605f55%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] [TW5] Issues understanding filters

[William RENOU]

I've been studying various bits of code found around various TW5, but there 
are some pieces I can't understand how they work.
This is one of them :
<$list filter="[is[current]field:fieldName1/fieldValue|fieldValue2/]">
 <$count 
filter="[field:fieldName/fieldValue3/fieldName2{{!!fieldValue3}}]"/>

 <$button message="tw-new-tiddler" class="btn-invisible" 
param="$:/_Template/fieldValue3> fieldValue3 


I vaguely understand the goal of the <$button> tag, but I can't decypher 
the list and count filter. I've read all documentation on the operators 
used, but I have found nothing regarding use of / in the field operator - 
hard and soft parameters but nothing about / being used. The only two 
examples given in field Operator documentation do not use /.

My 'best' guess (and I've had many in the past few days trying to 
understand them) is the list filter is trying to filter tiddlers having 
either fieldValue or fieldValue2 as value for their fieldName1 field. Goal 
of the 'is[current]' is unknown.
But the <$count> filter totally evades me.

Not sure if this is relevant, but the tiddler is transcluded twice (the 
tiddler it's transcluded in is transcluded in another - no direct use).

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/dab2c799-baaf-4372-a5af-0e4a89dd64e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.