TiddlyWiki node update-issue

[torax...@googlemail.com]

Hi!

at first hapyp new year.

I tried the update from 5.1.22 => 5.1.23 with the descriped procedure via

`npm -g update tiddlywiki`

A short `npm -g list` shows the successfiul update in the npm-repository. But still in the control panel a version of 5.1.22 is displayed. What do I miss?

Thanks and for a reply.

Cheers

ToraxMalu

[PMario]

Hi,

Can you try: tiddlywiki --version in the command line?

Then you need to _restart_ your server. ... The control panel should change now.

-m

[duche...@gmail.com]

Hi Torax,

I had the same issue as you and fixed it with:

sudo npm -g update tiddlywiki

sudo systemctl restart tiddlywiki

and then refresh your tiddlywiki page in your browser.

N.

[torax...@googlemail.com]

Hi PMario and duche,

thanks for the try. I forgot to mention, I am working with Windows. So SUDO won't work in the way, you expect. ;)

I fiddled around with the whole stuff and found following situation:

npm -g install tiddlywiki and npm -g update tiddlywiki installing the correct version (5.1.23) in the common repository beneath %appdata%\npm.

Jumping into the directory %appdata%\npm\node-modules\tiddlywiki and executing node tiddlywiki --version starts the correct version 5.1.23.

A call via tiddlywiki --version displayes the version 5.1.22.

Also an update as administrator (equivalent to sudo ...) doesn't change anything.

I even created a VM with a virgin Windows 10 and tested – it was instantly installed and executed tiddlywiki 5.1.23.

So far my testing.

I just uninstalled tiddlywiki via npm - g uninstall tiddlywiki from the system, but tiddlywiki --version still executes with return 5.1.22 – so there must be another installation place for node-stuff and NPM-repository. I now start to dive into the filesystem and variables. (PATH and so on. I'll keep you informed about my progress and would appreciate further hints. Bacause there seems to exist a similar "bug" for Linux, maybe this could be an addition to the tiddlywiki-article for https://tiddlywiki.com/#Upgrading%20TiddlyWiki%20on%20Node.js .

Cheers ToraxMalu

[torax...@googlemail.com]

ps: duchesneno sorry for shortening your nick to duche - the user-interface chopps of part of you name.

[Mark S.]

Is it possible that you installed at one time your own copy of tiddlywiki from github. i.e. following these instructions:

https://tiddlywiki.com/#Working%20with%20the%20TiddlyWiki5%20repository

[torax...@googlemail.com]

Err - no. But I found another installation in C:\Program Files\nodejs\node_modules\tiddlywiki. So my idea of something funny with tiddlywiki.cmd and the PATH was right.

[torax...@googlemail.com]

okay - propabbly I figured it out. Assumed System environment is a Win10 x64 and Node.JS 15.x.

While installation Node.JS sets two path-entries:

1. %ProgramFiles%\nodejs\
2. %AppData%\npm

For my tests I used an account with administrator account, the terminal was started with and without administrator privileges. (comparable with SUDO)

In both szenarios npm -g effected only the 2nd location in %AppData%\npm. So how I managed to install a copy in %ProgramFiles%\nodejs is beyond my imagination – I never modified the first location actively.

Windows creating the PATH-varible from two parts: The common setting and a account-individual part. The first is prioritized over the latter, what resulted in my observed behavior: When I tried to call tiddlywiki in the terminal, I tried to execute %appData%\npm\tiddlywiki.cmd, but ran in effect %ProgramFiles%\nodejs\tiddlywiki.cmd. And in addition the command npm -g update … never reached this location…

I cleand up the mess by

1. stopping all node.js-instances
   
2. uninstalling Node.js
3. deleting
   1. %ProgramFiles%\nodejs
   2. %AppData%\npm
   3. %AppData%\npm-cache
      [an old version of the cache? Wasn't recreated after re-installation]
   4. %LocalAppData%\npm-cache
4. reinstalling Node.js
5. reinstalling node.js-Modules with npm -g at the right location (inclusive tiddlywiki)
   

So far I recognize there were no entries in the Windows registry.

Hope, this helpes someone else. It was definitely not an issue of Tiddlywiki rather a possible wrong use npm…

cheers ToraxMalu