Woohoo !
All is working A-1. Thank-you very much for your help !
I got rid of the wonky tiddler likely created while in the midst of coding
a new-tiddler action widget.
I also replaced my on startup "context-setting" javascript macro with some
native TW code to do the job, which makes me a
On Saturday, August 14, 2021 at 9:30:58 PM UTC+2 PMario wrote:
> You have a very strange tiddler title, that start with: <$vars vWorkingTid
> . It seems to cause a problem with the node.js syncer. ... No
> tiddlers are saved. ... I did disable it at import so all tiddlers seemed
> to be
I'm not really sure, what the macro does, but if the .run function would
look like this:
exports.run = function() {
if ($tw.browser) {
const queryString = window.location.search;
try {
const urlParams = new URLSearchParams(queryString);
const
Please don't spend too much of your time on that macro.
That was very early going when I couldn't figure out a way to accomplish
the same thing with just native TW code.
I am no fan of javascript, so quite happy to send that js code to the
dustbin.
Maybe not tonight. Bad thunderstorm going
Hi,
Yea, if those 2 tiddlers are removed it works. ... Will have a closer look
at the macro. ...
-m
On Saturday, August 14, 2021 at 9:45:19 PM UTC+2 PMario wrote:
> On Saturday, August 14, 2021 at 9:35:11 PM UTC+2 cj.v...@gmail.com wrote:
>
>> getstartupcontext.js, that I can get rid of going
On Saturday, August 14, 2021 at 9:35:11 PM UTC+2 cj.v...@gmail.com wrote:
> getstartupcontext.js, that I can get rid of going forward.
>
> If you want, delete that tiddler from the process.
>
It's astonishing that this mechanism works. ... Where did you get this
implementation from?
The
And that "<$vars vWorking Tid..." tiddler, that's definitely something I
created by mistake while in the process of creating an action widget.
I think. I can't explain that tiddler.
On Saturday, August 14, 2021 at 4:30:58 PM UTC-3 PMario wrote:
> You have a very strange tiddler title, that
getstartupcontext.js, that I can get rid of going forward.
If you want, delete that tiddler from the process.
On Saturday, August 14, 2021 at 4:30:58 PM UTC-3 PMario wrote:
> You have a very strange tiddler title, that start with: <$vars vWorkingTid
> . It seems to cause a problem with
You have a very strange tiddler title, that start with: <$vars vWorkingTid
. It seems to cause a problem with the node.js syncer. ... No
tiddlers are saved. ... I did disable it at import so all tiddlers seemed
to be created ... But .. see next issue ;)
And there seems to be a
If it matters any: version of node is 10.24.0
On Saturday, August 14, 2021 at 4:22:25 PM UTC-3 PMario wrote:
> On Saturday, August 14, 2021 at 8:54:15 PM UTC+2 cj.v...@gmail.com wrote:
>
>> version 5.1.23
>>
>> Should I first upgrade the single-file TiddlyWiki from 5.1.22 to 5.1.23 ?
>>
>
> No.
On Saturday, August 14, 2021 at 8:54:15 PM UTC+2 cj.v...@gmail.com wrote:
> version 5.1.23
>
> Should I first upgrade the single-file TiddlyWiki from 5.1.22 to 5.1.23 ?
>
No. ... I did test it with the prerelease and it worked without a problem.
I'll test it with 5.1.23 again.
-mario
--
You
Hi,
version 5.1.23
Should I first upgrade the single-file TiddlyWiki from 5.1.22 to 5.1.23 ?
On Saturday, August 14, 2021 at 3:39:14 PM UTC-3 PMario wrote:
> Hi,
> Which TW server version do you use?
>
> tiddlywiki --version will show it.
>
> -m
>
> On Saturday, August 14, 2021 at 7:36:45
Hi,
Which TW server version do you use?
tiddlywiki --version will show it.
-m
On Saturday, August 14, 2021 at 7:36:45 PM UTC+2 cj.v...@gmail.com wrote:
> Hello all,
>
> I was under the impression that the html file for a single-file TiddlyWiki
> could simply be dragged to the node.js
13 matches
Mail list logo
