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.
|
Re: New Accounts, posted by Stefan Ritt on Thu Oct 13 21:26:31 2005
|
[quote="Carl Shirey"]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.
|
Re: New Accounts, posted by Carl Shirey on Fri Oct 14 19:20:40 2005
|
[quote="Stefan Ritt"][quote="Carl Shirey"]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.
|
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. |
Re: Next ELOG Release ?, posted by Stefan Ritt on Fri Oct 14 11:07:40 2005
|
> Hello Stefan,
> Did you have a release Date for Elog V2.6.0 ?
> Thanks in Advance.
|
Re: Next ELOG Release ?, posted by Alex H on Fri Oct 14 11:28:28 2005
|
> > Hello Stefan,
> > Did you have a release Date for Elog V2.6.0 ?
> > Thanks in Advance.
|
Long lines in printout, posted by Bertram Metz on Wed Aug 10 10:50:55 2005
|
Hi,
long lines in an entry are not printed correctly (the lines are cut off), if the text is encoded as plain text. This works correctly, if the text is encoded |
Re: Long lines in printout, posted by Stefan Ritt on Mon Sep 5 20:39:15 2005
|
> long lines in an entry are not printed correctly (the lines are cut off), if the text is encoded as plain
> text. This works correctly, if the text is encoded as ELCode. I tried this with Firefox and Internet Explorer.
> Does anybody know a solution for this?
|
Re: Long lines in printout, posted by Bertram Metz on Mon Sep 12 10:44:51 2005
|
> > long lines in an entry are not printed correctly (the lines are cut off), if the text is encoded as plain
> > text. This works correctly, if the text is encoded as ELCode. I tried this with Firefox and Internet Explorer.
> > Does anybody know a solution for this?
|
Re: Long lines in printout, posted by Stefan Ritt on Tue Sep 13 13:33:59 2005
|
Your problem is related with the fact that I changed the formatting from fixed font to proportional font ("ELCode"). This gives you three options:
[LIST]
|
Re: Long lines in printout, posted by Bertram Metz on Thu Oct 13 10:56:29 2005
|
Hi Stefan,
I tried your suggestions with 'page shrinking' and 'message width', but they didn't help. What I do not understand is why this problem occurs only if the
message text is formatted as plain text. The lines are printed correctly, if the text is formatted as EL code or as HTML.
|
Re: Long lines in printout, posted by Stefan Ritt on Thu Oct 13 11:19:09 2005
|
Ok, I found the problem. In the default.css file, you will find a section
[code].messagepre {
|
Re: Long lines in printout, posted by Bertram Metz on Thu Oct 13 13:27:02 2005
|
The lines are still cut, if printed on paper.
I played again with the 'message width' parameter, which actually the key parameter in my problem. I saw in the source, that the default value is now 112,
but it was 76 in the elog version we'd used previously (V2.5.2). If I set 'message width' to 76 again, it works fine for new entries!
|
Re: Long lines in printout, posted by Stefan Ritt on Thu Oct 13 13:51:55 2005
|
[quote="Bertram Metz"]The lines are still cut, if printed on paper.[/quote]
Are you sure? After you change the CSS file, you have to reload the page. I just tried with the very long entry from this thread and got in the Firefox |
Re: Long lines in printout, posted by Bertram Metz on Thu Oct 13 17:45:58 2005
|
You're right. I don't know what I've tested this afternoon ;)
Without the fixed font the text might get very small, if the line is too long.
I think we'll set 'message width' = 76.
|
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.
|
Re: Trying to remove "mailto:" from the email address, posted by Stefan Ritt on Thu Oct 13 08:32:20 2005
|
[quote="Matt Kimball"]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.[/quote]
|
elog fails to connect with "cannot get host name: Success" message, posted by ScottK on Fri Sep 23 17:27:40 2005
|
I can't seem to connect using elog:
elog -h <myhost>:8080 -v -l Servers -a "Type=Routine" -a "Author=ScottK" -m ~/test.txt |
Re: elog fails to connect with "cannot get host name: Success" message, posted by Stefan Ritt on Wed Oct 5 13:24:52 2005
|
[quote="ScottK"]I can't seem to connect using elog:
elog -h <myhost>:8080 -v -l Servers -a "Type=Routine" -a "Author=ScottK" -m ~/test.txt
|
Re: elog fails to connect with "cannot get host name: Success" message, posted by ScottK on Tue Oct 11 15:09:42 2005
|
[quote="Stefan Ritt"][quote="ScottK"]I can't seem to connect using elog:
elog -h <myhost>:8080 -v -l Servers -a "Type=Routine" -a "Author=ScottK" -m ~/test.txt
|
Cannot submit admin password while logbook is named in Chinese, posted by Exaos Lee on Sun Oct 9 20:43:31 2005
|
As the title. |
Re: Cannot submit admin password while logbook is named in Chinese, posted by Stefan Ritt on Mon Oct 10 14:01:14 2005
|
[quote="Exaos Lee"]As the title. [/quote]
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? |
Re: Cannot submit admin password while logbook is named in Chinese, posted by Exaos Lee on Mon Oct 10 19:33:05 2005
|
[quote="Stefan Ritt"][quote="Exaos Lee"]As the title. [/quote]
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? |
Re: Cannot submit admin password while logbook is named in Chinese, posted by Stefan Ritt on Tue Oct 11 09:24:12 2005
|
[quote="Exaos Lee"]Sorry for my poor English. The case is like this: When I set an admin password for my logbook which is named in Chinese, I cannot open
the config page while the password is correct. It seems that the logbook named in Chinese cannot recieve the password submitted. If the logbook is named
other than Chinese, everything is OK. I will repeat the problem and describe it more exactly.[/quote]
|
Some spell mistakes, posted by Exaos Lee on Sun Oct 9 20:49:41 2005
|
I find some new strings from the warnings like this:
[quote]Language error: string "HelpELCode" not found for language "chinese"[/quote]
|
Re: Some spell mistakes, posted by Stefan Ritt on Mon Oct 10 14:09:49 2005
|
[quote="Exaos Lee"]I find some new strings from the warnings like this:
[quote]Language error: string "HelpELCode" not found for language "chinese"[/quote]
|
Re: Some spell mistakes, posted by Exaos Lee on Mon Oct 10 19:26:35 2005
|
[quote] Ok, fixed in the current subversion repository. Better write such things by personal mail to me, since it might not interest the elog community
very much.[/quote]
Sorry. ;-) I will mail you first next time. |
Install error on MacOS X, posted by Exaos Lee on Mon Oct 10 19:22:51 2005
|
Executing "make" on MacOS X is OK, but "make install" failed due to the following error:
[code]
/usr/bin/install -m 0755 -d /usr/local/bin /usr/local/sbin /usr/local/man/man1/ /usr/local/man/man8/
|