Bimlas,
I understand your needs better now, please consider this approach, which I
am confident should work,
- it is I believe technically feasible
- but needs some technical PHP and saver help.
- In your example case you would not need a serial editing mechanism.
The current tw-receiver allows single file wikis save to php server.
Typically all our savers for single file wikis, just save the monolithic
wikifile.
- There is already sufficient tools within tiddlywiki to save as another
filename, using a different filter and even different templates for the
save.
- I have long thought that it should be trivial to introduce a plugin
with the ability to save and read other files to/from a PHP server (if the
passphrase is available)
- Using custom or available templates you could save one, more or all
tiddlers as json, text and preformatted static html that your other website
has references to, allowing "display on a web page independently".
Basically these additional "exported" files get served by the PHP server
not tiddlywiki as with node.
- Such a facility could be used to develop a checkin/out or tiddlywiki
lock allowing single file wikis with multiple to be restricted to serial
editing.
Security,
- With the tw-receiver pass phrase you are authorised to write to disk
only if you have that
- When using single file wikis the key gaps with bob is dealing with
referencing single tiddlers and contention when you have more than one
potential editor
- Being able to export to the php server would allow you to publish
single tiddlers
- A lock and serial editing layer can address contention for single
file wikis.
- Additional supporting php could be added to restrict the saving from
tiddlywiki to particular folders or file names either publicly writable or
only authenticated.
- Perhaps we could build a method to save a named users modified
tiddlers to their own folder and load or import them (with selective
application) for some or all users.
- This would allow the contribution of content independent from the
core wiki, and be mediated by the authorised editor.
- Such as comments, form filled tiddlers, and more.
- You could have a hidden secure editable single file tiddlywiki that is
published to a seperate file on the server that is publicly accessible with
or without local storage and other plugins activated.
- Innerwiki plugin may be an option for generating a public version,
perhaps if the tiddlywiki is not too big.
Have you seen the core plugin "Auto download modified tiddlers" $:/
plugins/tiddlywiki/savetrail?
- I could imagine a version of this able to use the operational saver,
eg php perhaps saving flagged tiddlers only and according to a nominated
template raw or rendered.
There may be some resistance to this because some would say "It breaks the
single file wiki" model, but in many ways it does not, it just allows the
export, externalising and import of content, which accross time is a
multi-user function. The alternative method available now is to move to
NODE which already breaks the single file model.
Another, perhaps unnecessary, approach if the above one will not be
achievable (unlikely), is tiddlers can contain full html that interacts
with php and server based scripting, and if necessary via an iframe. It
would be possible to build a server based solution embedded within
tiddlywiki that publishes content to files to the server as desired by you.
Regards
Tony
On Thursday, March 5, 2020 at 9:38:19 PM UTC+11, bimlas wrote:
>
> TonyM,
>
> I want to get Tiddly to keep and edit notes that I can display on a web
> page independently of Tiddly. So Tiddly would be the "editor", but the
> display would be eg. In PHP. On the other hand, I also want to make the
> wiki completely online, so that I can access it anywhere and the changes
> are all in one place.
>
> I don't like the idea of a VPN because I don't think I get it through a
> webhost, on the other hand, it would have to run at home on a continuously
> running server. If I already have a web host, I'd like to use it for this
> purpose.
>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" 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/tiddlywikidev/c56346f7-f729-47f9-a0a0-3bb7ff21d0af%40googlegroups.com.
