DIDIWIKI - it dos not save text input into a new page
DIDIWIKI - it dos not save text input into a new page
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?
- silver-city-productions
- Posts: 6
- Joined: Fri 06 Jun 2008, 18:56
- Location: Benicia, CA, USA
-
- Posts: 13
- Joined: Sat 08 Nov 2008, 23:54
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.
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.
-
- Posts: 14
- Joined: Mon 19 Nov 2007, 09:42
I have found that opening a console and entering this:
or this:
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.
Code: Select all
chmod 744 /root/spot/.didiwiki
Code: Select all
chmod 0744 /root/spot/.didiwiki
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.