Say I have a tiddler that must not be overwritten by things such as:
- an attempt to save a new tiddler with the same name
- an import of a tiddler with the same name
i.e. a critical tiddler, one which if overwritten, things will get
completely screwed up.
Is there an easy way to protect
Charlie,
Have you considered creating a third node Wiki "Customer List", using bob
so more than one user can access it at a time?
Then both Sales Reps wikis can have this "Customer List" in a tiddler with
and an iframe to the customer list and freely drag "customer" tiddlers to
and from the
On Sunday, September 5, 2021 at 8:36:26 PM UTC+2 cj.v...@gmail.com wrote:
...
> Is there an easy way to protect such a tiddler?
>
No. In TW you can overwrite every core tiddler if you like. So there is no
way to write-protect a tiddler.
What do you want to achieve?
-m
--
You received this
Trying to achieve a robust architecture for a farm of node.js TiddlyWikis
that together form a distributed database, with end-user level (and
private) TiddlyWikis that have certain types of tiddlers that are
automagically shared (and the rest private), and system-level TiddlyWikis
that tie all
Charlie,
A few ideas;
One way would be to stash a copy away, perhaps inside a JSON tiddler,
similar to Mohammad's trash plugin but just on editing. This kind of
solution can intercept User interface edit/delete however batch processes
can by pass this.
Some solutions like noteself to keep
G'day Tones,
I've got editing and delete of important tiddlers blocked via tiddler
locking. That's easy and good.
The only thing I have to handle, even if 99% unlikely, is certain tiddlers
getting overwritten by any tech-savvy (well, TiddlyWiki-savvy) individual.
Since that can't really be
Well, "Tiddly Locking" isn't a solution to my problem in this thread.
My problem is about preventing tiddlers from being overwritten by an import
or by a new tiddler getting created and saved with a name of a tiddler that
already exists. That's not solved.
Tiddly Locking is great, is
G'day Tones,
Nah, in this scenario I've dreamed up (to really get to know TiddlyWiki on
node.js), I'm sticking to a minimalist approach and not adding any plugins
or extras, pushing as far as I can with just TiddlyWiki and a little bit of
help via symlinks.
In this scenario, each sales rep
Charlie,
Good to hear. Since you question was answered with "Tiddly locking" could
you point to that as a solution for future readers in this thread ?
Tones
On Monday, 6 September 2021 at 15:15:49 UTC+10 cj.v...@gmail.com wrote:
> G'day Tones,
>
> I've got editing and delete of important
Well, throwing out the general concepts for now. The full guacamole isn't
really mine to share at the moment.
On Monday, September 6, 2021 at 2:46:03 AM UTC-3 TW Tones wrote:
> Thanks for sharing your solution to the community.
>
> On Monday, 6 September 2021 at 15:42:25 UTC+10
Thanks for sharing your solution to the community.
On Monday, 6 September 2021 at 15:42:25 UTC+10 cj.v...@gmail.com wrote:
> G'day Tones,
>
> Nah, in this scenario I've dreamed up (to really get to know TiddlyWiki on
> node.js), I'm sticking to a minimalist approach and not adding any plugins
11 matches
Mail list logo
