Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 138 of 806  Not logged in ELOG logo
ID Date Icondown Author Author Email Category OS ELOG Version Subject
  1470   Tue Oct 18 08:02:44 2005 Reply Christian Schultcschult@gmx.deQuestionLinux2.6.0beta2Re: Error message: "Attachment #6 of entry #0 not found"
> > Hi all, I get messages like this 
> > Attachment #16 of entry #0 not found 
> > Please use your browser's back button to go back 
> > always when clicking on an entry in summary or threaded view.  
> > I can only read entries when browsing them in full view. How can i fix this? 
> > regards, Christian 
>  
> I need some more information. Can you send me your elogd.cfg, and show  
> me the URLs your browser displays during your navigation? 
 
Well, this is my elog.conf: 
 
[global] 
logbook tabs = 1 
port = 8081 ; Automatically added in installation. 
Hosts allow = localhost, jazz.cocis.de, 127.0.0.1, 192.168. 
Hosts deny = ALL 
[debian] 
Theme = default 
Comment = debian logbook 
Attributes = Author, Type, Category, Subject 
Required Attributes = Author, Type 
Subst Author = $long_name 
Subst Email = $user_email 
Locked Attributes = Last Revision 
Subst on Edit Last Revision = $date by $long_name 
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other 
Options Category = General, Hardware, Software, Network, Other 
Page Title = ELOG - $subject 
Reverse sort = 1 
Quick filter = Date, Type 
Password file = /var/lib/elog/elogpasswd.pwd 
Admin user = admin 
Reverse sort = 1 
Restrict edit = 1 
Suppress Email to users = 1 
 
This is the URL after logging in: 
http://localhost:8081/debian/17?cmd=List&mode=summary 
 
When i click on one of the entrys, i get thar error message. 
URL: http://localhost:8081/debian/debian/17 
 
It says: "Attachment #17 of entry #0 not found 
  Please use your browser's back button to go back" 
 
regards, Christian 
  1471   Tue Oct 18 08:04:29 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.0beta2Re: Error message: "Attachment #6 of entry #0 not found"
> This is the URL after logging in: 
> http://localhost:8081/debian/17?cmd=List&mode=summary 
>  
> When i click on one of the entrys, i get thar error message. 
> URL: http://localhost:8081/debian/debian/17 
>  
> It says: "Attachment #17 of entry #0 not found 
>   Please use your browser's back button to go back" 

Ah, now I recognize the error. Please update to the newest beta5, it's fixed there.

- Stefan
  1472   Tue Oct 18 18:13:57 2005 Reply Charles DuncanCharles@YorkU.CAQuestionLinux2.6.0beta2Re: Error message: "Attachment #6 of entry #0 not found"
> > This is the URL after logging in: 
> > http://localhost:8081/debian/17?cmd=List&mode=summary 
> >  
> > When i click on one of the entrys, i get thar error message. 
> > URL: http://localhost:8081/debian/debian/17 
> >  
> > It says: "Attachment #17 of entry #0 not found 
> >   Please use your browser's back button to go back" 
> 
> Ah, now I recognize the error. Please update to the newest beta5, it's fixed there.
> 
> - Stefan

Stefan,

where can we get Beta5, I can only find Beta4 on all the download locations.

-Charles-
  1473   Wed Oct 19 15:44:07 2005 Reply Charles DuncanCharles@YorkU.CAQuestionLinux2.6.0beta2Re: Error message: "Attachment #6 of entry #0 not found"
> > > This is the URL after logging in: 
> > > http://localhost:8081/debian/17?cmd=List&mode=summary 
> > >  
> > > When i click on one of the entrys, i get thar error message. 
> > > URL: http://localhost:8081/debian/debian/17 
> > >  
> > > It says: "Attachment #17 of entry #0 not found 
> > >   Please use your browser's back button to go back" 
> > 
> > Ah, now I recognize the error. Please update to the newest beta5, it's fixed there.
> > 
> > - Stefan
> 
> Stefan,
> 
> where can we get Beta5, I can only find Beta4 on all the download locations.
> 
> -Charles-

I downloaded the source from the new web site.

-Charles-
  1475   Thu Oct 20 16:01:49 2005 Reply Stefan Rittstefan.ritt@psi.ch Linux2.6.0beta4Re: Howto force users to supply an email address when registering?

Johan Nyberg wrote:
Is there a way to force the users to supply an email address when they register?


I will happily implement such an email check if you supply me further information. Presume you enter an email address in the form user#domain.com (# instead @). Does your SMPT server then complain, too? What about user@com (without "domain.")? If you check all possibilities and let me know, I will put it in.
  1476   Sat Oct 22 00:21:03 2005 Reply Johan Nybergjohan.nyberg@tsl.uu.se Linux2.6.0beta4Re: Howto force users to supply an email address when registering?

Stefan Ritt wrote:

Johan Nyberg wrote:
Is there a way to force the users to supply an email address when they register?


I will happily implement such an email check if you supply me further information. Presume you enter an email address in the form user#domain.com (# instead @). Does your SMPT server then complain, too? What about user@com (without "domain.")? If you check all possibilities and let me know, I will put it in.


Hi Stefan,

Sorry for the delayed reply. I have run some tests which I will send to you by email.

Johan
  1479   Mon Oct 24 14:30:48 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionOther2.6.0 b4Re: Login screen reappears after correct login

Daniel Broers wrote:
We are running elog perfectly on a solaris machine for some time now.
Except on some client pc's the login screen keeps reappearing after a succesfull login.
We upgraded to version 2.6.0 beta 4 but the problem persists.
Any suggestions?


Do you have cookies disabled on these client pc's maybe?
  1480   Mon Oct 24 14:50:58 2005 Reply Daniel Broersd.broers@amc.nlQuestionOther2.6.0 b4Re: Login screen reappears after correct login

Stefan Ritt wrote:

Daniel Broers wrote:
We are running elog perfectly on a solaris machine for some time now.
Except on some client pc's the login screen keeps reappearing after a succesfull login.
We upgraded to version 2.6.0 beta 4 but the problem persists.
Any suggestions?


Do you have cookies disabled on these client pc's maybe?


No, cookies are enabled.
ELOG V3.1.5-3fb85fa6