Enable user to view only, not post/delete., posted by Denis Perevalov on Tue Jul 20 21:03:10 2010
|
Hi,
I have just discovered elog and I absolutely love it.
I have a question. Is there a way to enable user to view only, not post/delete in my elog. Also I would like to allow them to view only certain |
Re: Enable user to view only, not post/delete., posted by Stefan Ritt on Wed Jul 21 12:33:39 2010
|
Denis Perevalov wrote:
I have a question. Is there a way to enable user to view only, not post/delete in my elog. Also I would |
elogd -C failing to sync password file with "Received invalid response from elogd server" message, posted by John Rouillard on Sun May 2 17:43:06 2010
|
Hello:
I am running release 2.7.8 of elog. I am using the cloning/syncing features
|
Re: elogd -C failing to sync password file with "Received invalid response from elogd server" message, posted by John Rouillard on Sun May 9 18:12:28 2010
|
Does anybody have any ideas? Should I post a config or something?
-- rouilj |
Re: elogd -C failing to sync password file with "Received invalid response from elogd server" message, posted by Stefan Ritt on Mon May 10 09:55:12 2010
|
Hi Rouilj,
re-posting your bug report doe not help. If I'm not replying immediately it means I'm pretty busy with other things, so just be patient.
|
Re: elogd -C failing to sync password file with "Received invalid response from elogd server" message, posted by John Rouillard on Mon May 17 04:01:16 2010
|
[quote="Stefan Ritt"]Hi Rouilj,
re-posting your bug report doe not help. If I'm not replying immediately it means I'm pretty busy with other things, so just be patient.
[/quote]
|
Re: elogd -C failing to sync password file with "Received invalid response from elogd server" message, posted by John Rouillard on Mon May 17 04:19:29 2010
|
[quote="John Rouillard"]
I think I kind of see what's happening here. In is_command_allowed you add the GetPwdFile to the list of
allowed command but only if is_admin_user is true. Since the user is guest at that point, I assume
|
Re: elogd -C failing to sync password file with "Received invalid response from elogd server" message, posted by Stefan Ritt on Tue May 18 13:21:32 2010
|
[quote="John Rouillard"][quote="John Rouillard"]
I think I kind of see what's happening here. In is_command_allowed you add the GetPwdFile to the list of
allowed command but only if is_admin_user is true. Since the user is guest at that point, I assume
|
Re: elogd -C failing to sync password file with "Received invalid response from elogd server" message, posted by John Rouillard on Tue May 18 21:17:35 2010
|
[quote="Stefan Ritt"]
Ok, now I got it! The problem was that you used "Guest menu commands = ..." and I did not. So the behavior is different with that option, which is why
I could not reproduce your problem initially. Now I could reproduce it and the cleanest fix is this:
|
Re: elogd -C failing to sync password file with "Received invalid response from elogd server" message, posted by Stefan Ritt on Wed May 19 09:57:50 2010
|
[quote="John Rouillard"]Ok, so this patch fixes the problem on the client side (rather than the server side like my patch) of the
cloning process. I can't tell from the patch above but will this fix allow the cloning process to "complete"
but without the password file being copied, or does code outside the patched section try to login and get
|
Re: elogd -C failing to sync password file with "Received invalid response from elogd server" message, posted by John Rouillard on Thu May 20 03:37:59 2010
|
[quote="Stefan Ritt"][quote="John Rouillard"]Ok, so this patch fixes the problem on the client side (rather than the server side like my patch) of the
cloning process. I can't tell from the patch above but will this fix allow the cloning process to "complete"
but without the password file being copied, or does code outside the patched section try to login and get
|
Re: elogd -C failing to sync password file with "Received invalid response from elogd server" message, posted by John Rouillard on Sat Jun 12 05:55:39 2010
|
[quote="John Rouillard"]
Sorry to report that it fails same as originally with:
[code]
|
change design part of the discussion board, posted by Heinzmann on Sun Jun 6 22:54:55 2010
|
Hello Stefan,
If I would like to change the design of the attached part of the discussion board like: |
Re: change design part of the discussion board, posted by Stefan Ritt on Tue Jun 8 09:02:03 2010
|
Heinzmann wrote:
Hello Stefan, |
Re: change design part of the discussion board, posted by Heinzmann on Tue Jun 8 23:08:41 2010
|
Stefan Ritt wrote:
|
Re: change design part of the discussion board, posted by Stefan Ritt on Wed Jun 9 08:26:20 2010
|
Heinzmann wrote:
I have done the changes to my logbock, but I think I have done something wrong. As an example, the window |
inline-code, posted by Yoshio Imai on Tue Jun 8 15:48:06 2010
|
Hi, Stefan!
Sometimes, it is annoying that the [code][code][/code]-Tag creates a line break, because there are situations where verbatim text inside the regular text |
Re: inline-code, posted by Stefan Ritt on Tue Jun 8 16:33:07 2010
|
[quote="Yoshio Imai"]Sometimes, it is annoying that the [code][code][/code]-Tag creates a line break, because there are situations where verbatim text inside
the regular text flow is desirable (just like here). I would like to request an additional elcode-tag [code][ilcode][/code] (in-line code) which translates
to [code]<code>[/code] instead of [code]<pre>[/code].
|
Restricting logbook view, posted by Allen on Fri May 21 14:37:26 2010
|
Is there anyway to restrict access so that a user can only see the log entries they post or only replies to their log entry? I know it is possible
to restrict editing to only posts they submitted, but I have a need to not even allow them to see other posts except for what they submitted and I am wondering
if this is possible currently, or if this is planned, or could be planned for a future version? |
Re: Restricting logbook view, posted by Stefan Ritt on Tue Jun 8 12:02:36 2010
|
Allen wrote:
Is there anyway to restrict access so that a user can only see the log entries they post or only replies to their log entry? I know |
Deamon on Debian, posted by Marco Rojas on Wed Jun 2 18:46:32 2010
|
Hi,
I have been using ELOG for a while and I love it. It is a default installation on Debian Lenny and ELOG 2.7.8. I am having problems
with the deamon script, I can stop the service by doing /etc/init.d/elog stop but I can't started. When I do /etc/init.d/elog start I get this error: |
Re: Deamon on Debian, posted by Stefan Ritt on Tue Jun 8 09:21:16 2010
|
Marco Rojas wrote:
Hi, |
cannot start elog, posted by harley on Thu May 27 22:35:49 2010
|
I have v2.7.7 of elog running on a OSX system running 10.6 I configured and installed about a year ago. It's a wonderful thing to have.
I acquired another system running 10.6 to dedicate to the elog app. I downloaded 2.7.8 and performed the following steps:
extract tarball in the desired directory |
Re: cannot start elog, posted by Stefan Ritt on Tue Jun 1 13:17:18 2010
|
harley wrote:
I have v2.7.7 of elog running on a OSX system running 10.6 I configured and installed about a year ago. It's a wonderful thing to have. |
attachment filename bug & Makefile issue, posted by A. Martin on Sat May 15 06:01:40 2010
|
If I upload the file "000000_000000_file.txt", elog will chop the filename to "file.txt." Also, this effects
the file's displayed "Uploaded" time. It shows the file as being uploaded on: "Tue Nov 30 00:00:00 1999"
|
Re: attachment filename bug & Makefile issue, posted by Stefan Ritt on Tue May 18 16:40:15 2010
|
> If I upload the file "000000_000000_file.txt", elog will chop the filename to "file.txt." Also, this effects
> the file's displayed "Uploaded" time. It shows the file as being uploaded on: "Tue Nov 30 00:00:00 1999"
|
Re: attachment filename bug & Makefile issue, posted by A. Martin on Thu May 20 04:33:07 2010
|
|