Hi Jeremy,
Thanks for responding!
There are several options for setting up TiddlyWiki5 for access by multiple
> users, but I'm afraid that all of them require a degree of technical
> knowledge.
As for the technical knowledge, I have a friend (as above) that has some
PHP knowledge and in two weeks time one will be here with quite a lot of
PHP knowledge.
It's hard to help figure out what went wrong without more information. Can
> you describe the steps you took, and what happened?
- I did follow the instructions on the "Saving on a PHP server" page, it
would say "Starting to save wiki" but never actually save the file;
- The Wikiname: yarne (as set in the store.php);
- Password: yarne123 (as set in the store.php);
- Server URL: enrayarne.com/store.php;
- Upload filename: index.html;
- The other two we kept on root.
- Then I created a TiddlySpot with the same name (yarne) tried again, still
no luck;
- At this stage I read some things about BidiX and his Upload- and
PasswordOptionsPlugin and decided to give that a shot;
- Created a new wiki, installed the plugins offline so they would
actually be installed;
- First tried the method
listed: http://www.wikihow.com/Install-a-Tiddlywiki-Plugin, that didn't
work;
- Then tried adding $/ in front of it which actually gave me a result
that I was expecting, but this still didn't allow me to save it without
using TiddlySpot;
- I used TiddlySpot (http://b507wiki.tiddlyspot.com/) that now gives me
the error as you can see. It actually did do something this time but I
broke it in the process (this was the first time the wiki said "Wiki saved".
- TiddlyWeb is the last option that me and a friend are trying right now,
but we don't know if this will end up the way we want it.
Do you want users to log in in order to edit content or do you want them to
> have to log in in order to be able to see the content?
I would like them to log in for both editing and reading at the same time.
The PHP backend is pretty primitive. It doesn't properly resolve attempts
> to save the wiki at the same time by different users. If there's a clash
> and you've overwritten somebody else's changes then you have to use the
> backups feature to resolve things manually.
This wouldn't happen in the way I/we would use it. The application I have
would have more reading action and about 3-5 edits/additions per week.
Can you describe your use case in a bit more detail? Other people here may
> have already tried to accomplish similar things
I'll write it step by step with possibilities that would work for me/us.
1. Login to enrayarne.com
- With a generic login for edit only;
- Only one person at a time to prevent the edit at the same time
possibility.
- With a generic login for read only.
2. Edit/add a tiddler
- Using autosave (or press the button) the changes will be saved and the
file should be overwritten on the server.
- Either overwrite the index.html or save to a database which then
pulls the most recent version as the index.html.
3. Reload the page
- View the changes that you made previously.
I'm not looking to manually upload the document every time as this takes
away from the experience and thus won't be used because the threshold is to
high.
I see this wiki being applicable to almost every person/project
group/company (web based) because of the UIX. But with the way the
documentation is spread out it is hard to get into. A beginners guide would
be awesome. I'm already recommending it to everyone in my field, even
though we haven't gotten it to run the way we want to yet.
--
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 post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
