Re: how to sort entry, posted by Stefan Ritt on Thu Mar 27 09:10:46 2008
|
| jee wrote: |
|
i mean , is there a button that when i push it , then it only shows valuable enties which i preset before, the button may add in the "List | New | Edit | Reply | Duplicate | Find | Config | Logout | Help"
is that possible? pls show the command.
thank you for reply me!
|
No, there is no button for that. |
|
Re: change language, posted by svrmarty on Thu Mar 27 09:23:25 2008
|
| Stefan Ritt wrote: |
|
| svrmarty wrote: |
|
i've installed the debian package on my system
there's only one config file, /etc/elog.conf
i've tried to change the language, in [global] with Language = german,
then restarting the daemon, but it doesn't work.
please help me, where can i change the default(all) language and which settings should i do.
|
I'm not maintainer of the Debian package, you should direct your question to Recai <roktas@omu.edu.tr> (in principle he should read this forum). If you start elogd manually with the strace command like:
strace -r -o tmp.log -e trace=open /usr/local/elog/elogd
and check in tmp.log from where elogd opens its elogd.cfg. Then change the appropriate elogd.cfg (NOT elog.conf). After you change it, you have to restart elogd.
|
in the trace is only one config file
0.000103 open("/etc/elog.conf", O_RDONLY) = 3
0.000047 open("/etc/elog.conf", O_RDONLY) = 3 |
|
Re: change language, posted by svrmarty on Thu Mar 27 09:30:03 2008
|
|
svrmarty wrote:
|
|
| Stefan Ritt wrote: |
|
| svrmarty wrote: |
|
i've installed the debian package on my system
there's only one config file, /etc/elog.conf
i've tried to change the language, in [global] with Language = german,
then restarting the daemon, but it doesn't work.
please help me, where can i change the default(all) language and which settings should i do.
|
I'm not maintainer of the Debian package, you should direct your question to Recai <roktas@omu.edu.tr> (in principle he should read this forum). If you start elogd manually with the strace command like:
strace -r -o tmp.log -e trace=open /usr/local/elog/elogd
and check in tmp.log from where elogd opens its elogd.cfg. Then change the appropriate elogd.cfg (NOT elog.conf). After you change it, you have to restart elogd.
|
in the trace is only one config file
0.000103 open("/etc/elog.conf", O_RDONLY) = 3
0.000047 open("/etc/elog.conf", O_RDONLY) = 3
there's a bug in the debian package
0.000033 open("resources/eloglang.german", O_RDONLY) = -1 ENOENT (No such file or directory)
0.000264 open("/usr/share/elog/resources/eloglang.german", O_RDONLY) = -1 ENOENT (No such file or directory)
it's searching for the files in the wrong directory.
i've solved it with
#/usr/share/elog$ ln -s . resources
|
|
|
Re: FCKeditor not active, posted by Alain Hugentobler on Wed Apr 2 01:27:20 2008
|
| Kevin O'Sullivan wrote: |
|
I'm using ELOG version 2.7.3-2058 and have been trying to get FCKeditor to work. This, to my understanding from the documentation, is supposed to be a part of elog by default after version 2.7.0 and from looking at the configuration syntax manual, it looks as though FCKeditor should be on with the default settings. I done nothing to turn it off and none of the obvious fixes seem to do anything. I've posted the text of my configuration file below, what did I do wrong?
|
Got the same problem, solved by manually unzipping "scripts/fckeditor.zip" from the sources to the installation directory (/usr/local/elog/scripts)
A better solution is to modify the Makefile :
@unzip -q -f scripts/fckeditor.zip -d $(ELOGDIR)/scripts/
which doesn't work on my Ubuntu 8.04; however changing to:
@unzip -q scripts/fckeditor.zip -d $(ELOGDIR)/scripts/
does... |
|
Re: FCKeditor not active, posted by Kevin O'Sullivan on Wed Apr 2 03:34:43 2008
|
| Alain Hugentobler wrote: |
|
| Kevin O'Sullivan wrote: |
|
I'm using ELOG version 2.7.3-2058 and have been trying to get FCKeditor to work. This, to my understanding from the documentation, is supposed to be a part of elog by default after version 2.7.0 and from looking at the configuration syntax manual, it looks as though FCKeditor should be on with the default settings. I done nothing to turn it off and none of the obvious fixes seem to do anything. I've posted the text of my configuration file below, what did I do wrong?
|
Got the same problem, solved by manually unzipping "scripts/fckeditor.zip" from the sources to the installation directory (/usr/local/elog/scripts)
A better solution is to modify the Makefile :
@unzip -q -f scripts/fckeditor.zip -d $(ELOGDIR)/scripts/
which doesn't work on my Ubuntu 8.04; however changing to:
@unzip -q scripts/fckeditor.zip -d $(ELOGDIR)/scripts/
does...
|
That fixed it!
Thanks Alain. |
|
Re: FCKeditor not active, posted by Stefan Ritt on Wed Apr 2 09:19:55 2008
|
| Alain Hugentobler wrote: |
|
| Kevin O'Sullivan wrote: |
|
I'm using ELOG version 2.7.3-2058 and have been trying to get FCKeditor to work. This, to my understanding from the documentation, is supposed to be a part of elog by default after version 2.7.0 and from looking at the configuration syntax manual, it looks as though FCKeditor should be on with the default settings. I done nothing to turn it off and none of the obvious fixes seem to do anything. I've posted the text of my configuration file below, what did I do wrong?
|
Got the same problem, solved by manually unzipping "scripts/fckeditor.zip" from the sources to the installation directory (/usr/local/elog/scripts)
A better solution is to modify the Makefile :
@unzip -q -f scripts/fckeditor.zip -d $(ELOGDIR)/scripts/
which doesn't work on my Ubuntu 8.04; however changing to:
@unzip -q scripts/fckeditor.zip -d $(ELOGDIR)/scripts/
does...
|
I didn't realize that the Ubuntu version of unzip does not support the -f flag. Anyhow it's not really necessary, so I removed it from the distribution. The fix will be contained in the next release. |
Problems with elog client, posted by Yoshio Imai on Wed Apr 9 14:41:12 2008
|
Hi!
Since our upgrade to elog 2.7.3, it is not possible any more to edit an existing elog entry using the elog client with -e <id> option. The only console output is "Error transmitting message". Submitting an entry via the client is not problem.
Running the server with -v option does not yield any output at the time of the edit attempt. Running the client with -v option also doesn't help, because whatever the other options, only the help page is printed out and nothing else done. Btw, there is now a conflict between -s for "use SSL" and -s for the "subdir" option.
Any ideas?
Yoshio |
|
Re: Problems with elog client, posted by Stefan Ritt on Wed Apr 9 23:03:53 2008
|
| Yoshio Imai wrote: |
|
Since our upgrade to elog 2.7.3, it is not possible any more to edit an existing elog entry using the elog client with -e <id> option. The only console output is "Error transmitting message". Submitting an entry via the client is not problem.
Running the server with -v option does not yield any output at the time of the edit attempt. Running the client with -v option also doesn't help, because whatever the other options, only the help page is printed out and nothing else done. Btw, there is now a conflict between -s for "use SSL" and -s for the "subdir" option.
Any ideas?
|
The problem had to do with the integration of native SSL into elog/elogd. I tried to fix it in revision 2099. Please give it a try. I have not tried yet the SSL mode, but I changed the -s for "subdir" to -d not to collide with SSL. |
|