Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 437 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Show attachments  Show all entries    6459 Entries 
Goto page Previous  1, 2, 3 ... 436, 437, 438 ... 806, 807, 808   Next  
ID Date Icon Author Author Email Category OS ELOG Version Subject
  66325   Tue Apr 21 16:29:23 2009 Question Joseph Lejosephle9@gmail.comQuestionWindows2.7.6Is there a way to import old log messages

I update my elog from version 2.7.5 to 2.7.6 and mistakenly replace configuration file. so i have to reconfigure everything from ground up.  when my elog back online, old log messages are not show up. is there a way to import old log messages from old log book to new one.

 

thanks

  66324   Sat Apr 18 02:49:42 2009 Question Mikemike@raghuexim.comBug reportLinux2.7.6-2191"Forgot Password?" link not working?

I have my site running under apache. I don't have a /elog/ directory.

for example most would do http://www.example.com/elog/ to visit elog

but my site loads at http://www.example.com/

The site is private so it's password protected. Everything works fine except

if I click the "Forgot Password" link it does nothing.

but if I go to one of the log books...

http://www.example.com/open/

The forgot password link works.

Is there anyway to fix this? I have nothing else running on the server, it's dedicated to only ELOG.

That's why I don't want to have it running under /elog/ in the url.

  66323   Sat Apr 18 00:33:53 2009 Reply Dennis Seitzdseitz@berkeley.eduQuestionAll2.7.5Re: Config so that users can delete only their own entries?
Thanks for reminding me of that, it will do fine. A suggestion: Separate Restrict Edit into Restrict Edit and Restrict Delete or some functional equivalent. Then we have the choice to restrict one or the other or both. Is that worth doing?


Stefan Ritt wrote:

Dennis Seitz wrote:
I've tried

Deny_Delete = All
Allow Delete = $author

and just
Allow Delete = $author

But either users can delete anyone's entries, or they can't delete any entries.

Am I missing something? If not, can you add the capability to allow users to delete, but only their own entries?

Thanks as usual for a great piece of code!


You cannot put $author into any Allow or Deny option, only explicit login names (not "full" names). What you want however is
Restrict Edit = 1

which lets only the original author either delete or edit entries. If you use that option, you probably want as well
Preset Author = $long_name
Preset on reply Author = $long_name
Preset on duplicate Author = $long_name
Locked Attributes = Author

So a user cannot pretend to be somebody else. You also need a valid "admin user = ..." statement. Note that the admin user always can delete/edit entries. If no admin user is defined, everybody has automatically admin rights, so Restrict Edit has no effect.
  66322   Fri Apr 17 22:44:58 2009 Idea Mikemike@raghuexim.comQuestionLinux2.7.6-219mail to localhost?

Initially I thought you had to specify a port number after localhost for emailing.

As it turns out just putting "localhost" as the email server in the elog config

file works just fine. We have a strange problem where our elog server is running.

our outgoing mail has to be routed through port 465 and SSL. I had to set up

postfix and stunnel to handle this arrangement.

  66321   Thu Apr 16 08:34:03 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionAll2.7.5Re: Config so that users can delete only their own entries?

Dennis Seitz wrote:
I've tried

Deny_Delete = All
Allow Delete = $author

and just
Allow Delete = $author

But either users can delete anyone's entries, or they can't delete any entries.

Am I missing something? If not, can you add the capability to allow users to delete, but only their own entries?

Thanks as usual for a great piece of code!


You cannot put $author into any Allow or Deny option, only explicit login names (not "full" names). What you want however is
Restrict Edit = 1

which lets only the original author either delete or edit entries. If you use that option, you probably want as well
Preset Author = $long_name
Preset on reply Author = $long_name
Preset on duplicate Author = $long_name
Locked Attributes = Author

So a user cannot pretend to be somebody else. You also need a valid "admin user = ..." statement. Note that the admin user always can delete/edit entries. If no admin user is defined, everybody has automatically admin rights, so Restrict Edit has no effect.
  66320   Wed Apr 15 17:57:19 2009 Question Dennis Seitzdenseitz@comcast.netQuestionAll2.7.5Config so that users can delete only their own entries?
I've tried

Deny_Delete = All
Allow Delete = $author

and just
Allow Delete = $author

But either users can delete anyone's entries, or they can't delete any entries.

Am I missing something? If not, can you add the capability to allow users to delete, but only their own entries?

Thanks as usual for a great piece of code!
  66319   Wed Apr 15 14:44:42 2009 Reply Yoshio ImaiQuestionWindows2.7.5Re: Multi Logook Login
Hi, Stefan!


Stefan Ritt wrote:
If "password file = xxx" is however in each individual logbooks configuration, then you get "path=/<lobook>". You can check that by inspecting your browser's cookies. In that case the login name and password cookies are only sent to the URL for that specific logbook. I have not tested that extensively (different browsers, with/without Apache proxy), but if it works reliably, I will put this into the documentation.


We had done so on your advice and in principle this works, but our experience has shown one problem:

We have separated our logbooks into different top groups because of the sheer number of them (i.e. experiment logbooks in one top group with logbook groups for the sub-categories, personal analysis logbooks in another top group etc.). Obviously, the experiment logbooks may share the same login, therefore we have put the "password file" statement into that top group's global section (otherwise, we would have to log on to every beamtime logbook individually, which can be cumbersome when comparing e.g. experiment settings between beamtimes). For the personal logbooks, of course, we use per-logbook-access (i.e. "password file" statement in the individual logbook sections) such that logging on to one's own logbook does not imply access to someone else's logbook. However, since the group/top group structure does not appear in the elog URLs, the cookies for the beamtime logbooks all have the path set to "path=/". This breaks the scheme again (I guess we have sort of "abused" the concept of top groups a little) and it is not possible to work in one of the experiment logbooks in parallel with one's own logbook without having to renew the login when switching the logbook.


Is it possible to modify the elogd such that it first checks if, among the cookies sent, there is one where the path corresponds to the path of the current logbook, and evaluate cookies with "path=/" only if no such cookie is found?

Yoshio
  66318   Wed Apr 15 12:56:18 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.6-2191Re: ROptions value changed in the edit page
> When ROptions items contain the same substring and this substring is also an ROptions item (ex: notdone, 
> done), the value of the entry could change in the edit page. 
> It depends on the item order in the config file. 
> 
> If Options is used (instead of ROptions), it works as expected.
> 
> Is it a bug?
> 
> 
> Examples : 
> 
> #Insert "notdone" as new entry. When you try to edit the entry, the displayed value is "done".
> 
> [test_bad]
> Attributes = Author, Category
> ROptions Category = notdone, done
> 
> #No problem if you change the item order 
> 
> [test_good]
> Attributes = Author, Category
> ROptions Category = done, notdone

Thanks for reporting this bug. I fixed it in SVN revisoin 2193.
Goto page Previous  1, 2, 3 ... 436, 437, 438 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6