Thanks werner. I will build my own notes after trying this thanks

Regards
Tony

On Monday, 7 September 2020 at 20:36:23 UTC+10 Werner wrote:

> Tony,
>
> here's how I did it: 
>
> - D&D installed the plugin in question. In my case, it was A. Aldrich's 
> Tables plugin. 
> - The result was two files in my tiddlers 
> directory: $__plugins_aaldrich_tables.json 
> and $__plugins_aaldrich_tables.json.meta. 
> - Under my 
> c:\<username>\appdata\roaming\npm\node-modules\tiddlywiki\plugins 
> directory, I now created two directories aaldrich and aaldrich\tables.
> - Copied the .json file into the latter and renamed it to plugin.info. 
> - Opened the json.meta file and copied the contents ahead of the 
> "tiddlers" key in the plugin.info file. 
> - Added proper JSON formatting (quotation marks and commas) to the new 
> entries. If you have any wikitext plugin installed, you can use its 
> plugin.info file as a template.
> - Deleted the plugin from my wiki to get rid of the two above files
> - Added the missing plugin information in tiddlywiki.info in my wiki's 
> home directory. 
> - Stopped and restarted the server. 
>
> VoilĂ . 
>
> Best, Werner
>
> TW Tones schrieb am Samstag, 5. September 2020 um 08:33:37 UTC+2:
>
>> Mark,
>>
>> Are there instructions anywhere to take an in wiki plugin and make it a 
>> server plugin (file?).
>>
>> Regards
>> Tones
>>
>>
>> On Saturday, 5 September 2020 06:27:02 UTC+10, Mark S. wrote:
>>>
>>> Let me add, that there are two ways to add a plugin folder.
>>>
>>> The first is to add it to just a single wiki, in the plugins folder of 
>>> your tiddly data folder.
>>>
>>> The second is to add it to your node.js master copy of tiddlywiki.
>>>
>>> The advantage of the first method is that the plugins will continue to 
>>> be there as you upgrade, and it's pretty easy.
>>>
>>> The advantage of the second method is that once you have the plugins in 
>>> place, they are available to all your wikis just by insert some lines into 
>>> tiddlywiki.info.
>>>
>>> The disadvantage of the second method is that you have to find where 
>>> your master copy of TW is (On Windows, the path to the default TW version 
>>> is buried pretty deep.), and, possibly, your plugins won't survive when you 
>>> upgrade (don't know for sure on this point.) Certainly if you relink to a 
>>> different TW directory structure, your personal plugins aren't going to be 
>>> there automatically. 
>>>
>>> On Thursday, September 3, 2020 at 4:56:07 PM UTC-7, TW Tones wrote:
>>>>
>>>> Mark,
>>>>
>>>> That is possibly the clearest description so far. We need to document 
>>>> this a bit better.
>>>>
>>>> I admit I am no expert in this yet, and I hope if what I state is 
>>>> incorrect someone will contradict me.
>>>>
>>>> I would add to your points, as I understand it, that if installed in 
>>>> node apparently they are available to all wikis within Node such as under 
>>>> Bob, but installed by Drag and drop they become tiddlers installed in the 
>>>> specific wiki.
>>>>
>>>> You can see that except for the exceptions Mark mentions, drag and drop 
>>>> can be an intentional approach to installing a different set of plugins in 
>>>> different wikis.
>>>>
>>>> Despite this I am not sure what happens to to make correctly installed 
>>>> server plugins visible in the wikis below.
>>>>
>>>> Regards
>>>> Tony
>>>>
>>>>
>>>> On Friday, 4 September 2020 00:56:10 UTC+10, Mark S. wrote:
>>>>>
>>>>> I think it means there some plugins meant for node.js that need to be 
>>>>> installed in a directory (maybe because they need to communicate directly 
>>>>> with the operating system).
>>>>>
>>>>> For most 3rd party plugins I think you're OK with d&d. But if you have 
>>>>> a plugin that needs to directly communicate with the OS or over the 
>>>>> internet, then you will need to install local plugin directories.
>>>>>
>>>>> If you have official plugins, then you can "install" them just by 
>>>>> listing them in the tiddlywiki.info file. You do not want there to 
>>>>> also be a drag-and-drop plugin version of them because the d&d version 
>>>>> will 
>>>>> block the latest copy of the official version. The idea is that your 
>>>>> official plugins will automatically be upgraded on node.js when you 
>>>>> upgrade 
>>>>> your tiddlywiki installation on node.js.
>>>>>
>>>>> Having said that, if you're using code-mirror, and your drag-and-drop 
>>>>> version seems to be working, maybe just stick with it for the current 
>>>>> generation. It seemed to me that there was some internal inconsistency 
>>>>> with 
>>>>> the next gen of code-mirror. Whenever I tried to do the official install, 
>>>>> things broke. But that's just my thinking.
>>>>>
>>>>>
>>>>> Good luck!
>>>>>
>>>>>
>>>>>
>>>>> On Thursday, September 3, 2020 at 5:49:25 AM UTC-7, [email protected] 
>>>>> wrote:
>>>>>>
>>>>>> So I have my nodejs server up and running, but I did not want to 
>>>>>> start an entirely new wiki, instead I wanted to import my old wiki and 
>>>>>> continue using that. I imported it via just drag and dropping my .html 
>>>>>> file 
>>>>>> onto the newly made empty wiki. It imported everything just fine and 
>>>>>> everything seems to work ok.
>>>>>>
>>>>>> However, I noticed that installing plugins in nodejs 
>>>>>> <https://tiddlywiki.com/static/Installing%2520custom%2520plugins%2520on%2520Node.js.html>server
>>>>>>  
>>>>>> should *not *be done by drag and dropping them as individual 
>>>>>> tiddlers but instead you should make plugins folder in the server and 
>>>>>> put 
>>>>>> them there and tell in the tiddlywiki.info file what plugins to 
>>>>>> load. It is said that:
>>>>>>
>>>>>> > Note that including a plugin as an ordinary tiddler (e.g. by 
>>>>>> dragging and dropping a plugin into the browser) will result in the 
>>>>>> plugin 
>>>>>> only being active in the browser, and not available under Node.js.
>>>>>>
>>>>>> So what does this *actually *mean? All my old plugins were installed 
>>>>>> this way when I was not using nodejs. They still seem to work fine. 
>>>>>> Should 
>>>>>> I remove all my plugins installed with drag and drop and install them 
>>>>>> manually as per the link?
>>>>>>
>>>>>

-- 
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/10eb4f1b-db8a-416e-943b-3f4c7d4c69cen%40googlegroups.com.

Reply via email to