Re: Error message: "Attachment #6 of entry #0 not found", posted by Christian Schult on Tue Oct 18 08:02:44 2005
|
> > 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 |
|
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- |
Howto force users to supply an email address when registering?, posted by Johan Nyberg on Thu Oct 20 14:15:14 2005
|
Hi,
Today I noticed that a user had registered without supplying an email address. I am using Self Register = 3, which means I recieve an email from elogd when a new user wants to register. Apparently, I forgot to check that the users email field was empty. This empty email field led to a situation in which no email notifications were sent to the users. The elogd log file looks like this for a user with a registered email address:
20-Oct-2005 12:20:21 [<snip>] {AGATA SDA} RCPT TO: <johan.nyberg@tsl.uu.se>
20-Oct-2005 12:20:21 [<snip>] {AGATA SDA} 250 Ok
while it looks like this for a user with an epmty email address:
20-Oct-2005 12:20:22 [<snip>] {AGATA SDA} RCPT TO: <>
20-Oct-2005 12:20:22 [<snip>] {AGATA SDA} 501 Bad address syntax
When elogd hits this error it stops the process of sending emails, which means that no emails
at all are sent to any of the users. After manually adding the email address of the user with an empty address,
automatic email notification work again.
Is there a way to force the users to supply an email address when they register?
Johan |
|
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 |
Preset text overriden after preview, posted by Yoshio Imai on Wed Oct 26 16:00:00 2005
|
Hi, Stefan!
I have run across a problem with preset texts. We have defined a form to be filled in when the operator selects a specific combination of attributes. This form appears correctly, but after filling in the form, clicking on "Preview" leads to an error: the preview text is correct, but the actual text entry field is overriden again with the empty form. Clicking on "Submit" at this point then submits only the empty form, and the information filled in is lost.
When clicking on "Submit" without previewing, the text is entered correctly to the elog. Do you know where the problem might come from?
Thanks in advance
Yoshio |
|