Page 1 of 1

DIDIWIKI - it dos not save text input into a new page

Posted: Mon 08 Sep 2008, 10:08
by sjain259
I am using pup_400 am trying to learn how to use didiwiki the personal wiki program. I am not able to write & save text into a new page. Th text vanishes when the save button is pressed. What is wrong?

Posted: Mon 08 Sep 2008, 16:34
by silver-city-productions
Check your permissions. The didiwiki process runs as user 'spot', and there may be an issue with 'spot' getting to the files owned by 'root'.

Howto change owner

Posted: Tue 07 Oct 2008, 07:21
by myman_05
I have same problem

Posted: Thu 13 Nov 2008, 00:47
by anagramagia
This is how I solve my problem with didiwiki in puppy linux 4.1: I found that .didiwiki was owned by root and not spot, so i changed owner and group from root to spot and that's it. (Thanks to sylver-city-productions for the idea about the permissions)
Open a console with rxvt, then go to /root/spot/ (to be sure write cd /root/spot/)
Then, for changing owner:
chown spot .didiwiki
And for changing group:
chgrp spot .didiwiki

After those changes didiwiki saves the text I write in a new page.
May be it works for you too.

Posted: Fri 14 Nov 2008, 08:50
by friednoodle
I have found that opening a console and entering this:

Code: Select all

chmod 744 /root/spot/.didiwiki
or this:

Code: Select all

chmod 0744 /root/spot/.didiwiki
will fix the problem, at least it has worked on a couple of installs.
I'm only guessing, but maybe the source code for didiwiki is written
to prevent writing to a .didiwiki directory with 755 permissions for
better security??? You can also do this with the Rox file manager by clicking on the eye icon when in the spot directory so you can see the .didiwiki directory, then right clicking on the .didiwiki directory, select properties, and untick the write boxes for group and world. If someone
knows that this is the wrong approach please post a reply to this post.

They changes suggested above by anagramagia are probably good
for improving security as well, I would guess that changing both ownership as suggested by anagramagia and permissions as in this post would give the most desirable result, a working and secure didiwiki.