Display Attribute no longer works in Beta 5?, posted by Ulrich Trüssel on Fri Oct 7 08:53:00 2005 
|
Just changed from Beta 2 to Beta 5:
I'm using Display Attribut = [elog:$logbook/$message id] as a reference link for other entries (ex.: Display Referenz = [elog:$logbook/$message id]). also see the attached elogd.cfg file.
With Beta 2 (not testet with Beta 3 or 4!) this worked very well -> see attached Display Attribute with 260-b2.jpg file.
With Beta 5 is seems no longer to work -> see attached Display Attribute with 260-b5.jpg file.
ANy ideee what's wrong in my elogd.cfg??? Thanks! |
|
Re: Cannot submit admin password while logbook is named in Chinese, posted by Stefan Ritt on Mon Oct 10 14:01:14 2005
|
| Exaos Lee wrote: | | As the title. |
There is no possibility to change an admin password. You probably mean that you logged in as admin and cannot change your own password, is that right? Do you use user level access via "password file = ..."? What is your elogd.cfg? I tried to switch language to German and I can change my own password via the config page. |
|
Trying to remove "mailto:" from the email address, posted by Matt Kimball on Wed Oct 12 23:59:13 2005
|
We are using ver 2.5.4. As users enter new requests into the system, they would like email notifications. I have added the $user_email into a "notifications" section that we created. The email address that gets entered is "mailto:user@domain.com". Is there a way to remove the "mailto:"? Attached is my config file.
Thanks
Matt |
|
New Accounts, posted by Carl Shirey on Thu Oct 13 19:15:48 2005
|
I hope you can help me Stefan.
The problem that I am having is when someone request a account on elog I received e-mail message to activate there account. I click on the link from my e-mail to activate the account it takes me to the logon page. I log on and then I get a massage that the web does not exist.
What I found out was the elog Damon stops, and I have to restart it and everything work fine.
Here is a copy of me Elog config.
Also can you tell me how you set up the Subtext and the Show new entry buttons on the main page of the elog.
Thank for your help |
|
Next ELOG Release ?, posted by Alex H on Fri Oct 14 11:06:30 2005
|
Hello Stefan,
Did you have a release Date for Elog V2.6.0 ?
Thanks in Advance. |
|
How to connect to an ELOG server running behind apache+ssl using the elog command line program?, posted by Johan Nyberg on Sat Oct 15 16:50:25 2005
|
Hi,
I need to post a large number of "old" messages to one of my logbooks and I am trying to modify the script doelog (see http://midas.psi.ch/elogs/Contributions/10) to suit my needs. I am using apache + ssl for secure logins to my ELOG server. The doelog script uses the elog utility program, which is useful for posting ELOG messages from scripts or from the command line. My problem is that I cannot talk to my ELOG server with elog.
Here is what happens:
-------------------------------------------------------------------------------------------------
$ elog -v -h my.server.org -p 443 -l mylogbook -a Category=Other-u myusername mypasswd testmsg
Successfully connected to host my.server.org, port 443
Request sent to host:
POST /mylogbook/ HTTP/1.0
Content-Type: multipart/form-data; boundary=---------------------------1028A8C27FFD1021AAB342B
Host: my.host.org
User-Agent: ELOG
Content-Length: 811
Content sent to host.
Response received:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>400 Bad Request</title>
</head><body>
<h1>Bad Request</h1>
<p>Your browser sent a request that this server could not understand.<br />
Reason: You're speaking plain HTTP to an SSL-enabled server port.<br />
Instead use the HTTPS scheme to access this URL, please.<br />
<blockquote>Hint: <a href="https://my.server.org/"><b>https://my.server.org/</b></a></blockquote></p>
<hr>
<address>Apache Server at <a href="webmaster@my.server.org">my.server.org</a> Port 443</address>
</body></html>
Error transmitting message
-------------------------------------------------------------------------------------------------------
Access to the logbook works perfectly if I use a web browser. If I can find out how to use the elog command line program to connect to my ELOG server running behind apache+ssl, I think I can change the doelog script to suit my needs. Any help is appreciated.
Johan |
|
Error message: "Attachment #6 of entry #0 not found", posted by Christian Schult on Sun Oct 16 10:33:23 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 |
|
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 |