Re: Error message: "Attachment #6 of entry #0 not found", posted by Stefan Ritt on Tue Oct 18 08:04:29 2005
|
> 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 |
Re: Error message: "Attachment #6 of entry #0 not found", posted by Charles Duncan on Tue Oct 18 18:13:57 2005
|
> > 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- |
Re: Error message: "Attachment #6 of entry #0 not found", posted by Charles Duncan on Wed Oct 19 15:44:07 2005
|
> > > 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- |
Re: Howto force users to supply an email address when registering?, posted by Stefan Ritt on Thu Oct 20 16:01:49 2005
|
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. |
Re: Howto force users to supply an email address when registering?, posted by Johan Nyberg on Sat Oct 22 00:21:03 2005
|
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 |
Re: Login screen reappears after correct login, posted by Stefan Ritt on Mon Oct 24 14:30:48 2005
|
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? |
Re: Login screen reappears after correct login, posted by Daniel Broers on Mon Oct 24 14:50:58 2005
|
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. |
Re: Login screen reappears after correct login, posted by Stefan Ritt on Mon Oct 24 15:18:46 2005
|
Daniel Broers wrote: | No, cookies are enabled. |
Can you
- Delete all cookies on the client machine and try again
- If the problem persists: Tell you how you access your elogd. Do you use Apache as proxy? Which URL statement do you have in your elogd.cfg? What are the URLs shown in the address bar of your browser?
- Can you start elogd with the "-v" flag, and send me the output shown during an unsuccessful login
|