Re: Global change of links, posted by Stefan Ritt on Fri Dec 6 10:58:57 2024
|
You would have to access the raw elgo database files (which are pure ASCII files) and write some script which goes through all files and changes the URLs.
Stefan
| Dr Marta Divall wrote: |
|
Dear All,
We have been using the ELOG for several years and had inserted hyper-links instead of whole files in order to save storage space. From this month our server is moved to a new location with a new address. Is there a way for me to retrospectivelly replace all addresses with the new server file pass?
Thanks in advance,
Best regards,
Marta
|
|
|
Re: Global change of links, posted by Dr Marta Divall on Fri Dec 6 11:06:28 2024
|
Thanks!
| Stefan Ritt wrote: |
|
You would have to access the raw elgo database files (which are pure ASCII files) and write some script which goes through all files and changes the URLs.
Stefan
| Dr Marta Divall wrote: |
|
Dear All,
We have been using the ELOG for several years and had inserted hyper-links instead of whole files in order to save storage space. From this month our server is moved to a new location with a new address. Is there a way for me to retrospectivelly replace all addresses with the new server file pass?
Thanks in advance,
Best regards,
Marta
|
|
|
|
Re: Global "MOptions", posted by Stefan Ritt on Mon Mar 26 13:03:05 2007
|
| Fergus Lynch wrote: | | Would it be an option to have Global "MOptions" - perhaps configured in the 'global options' file - which can be called up and referenced in all logbooks? |
Sure, that's possible alreay with the current version. Just put your MOptions statement under [global] and it will be used in all logbooks. If a specific logbook uses different MOptions, put the a second MOptions list under that logbook's section and it will overwrite the global setting. |
|
Re: Global "MOptions", posted by Fergus Lynch on Tue Mar 27 13:57:44 2007
|
| Stefan Ritt wrote: |
| Fergus Lynch wrote: | | Would it be an option to have Global "MOptions" - perhaps configured in the 'global options' file - which can be called up and referenced in all logbooks? |
Sure, that's possible already with the current version. Just put your MOptions statement under [global] and it will be used in all logbooks. If a specific logbook uses different MOptions, put the a second MOptions list under that logbook's section and it will overwrite the global setting. |
Perfect! Works a treat (I promise to read the manual next time!)
Cheers
Fergus |
|
Re: Getting back from "Find" mode, posted by Stefan Ritt on Tue Nov 15 12:50:37 2005
|
| Yoshio Imai wrote: | There is one question regarding the "Find" function of the elog. Clicking onto "Search" takes the user to the list view on only those entries that match the search conditions. Since we use the list view in "Full" mode by default, this usually is enough to give us an overview of the event we looked for.
Is there a more direct way to get back to the unfiltered list view than selecting an entry and go to "List" or using "Find" again and clicking on "Back"? |
I can easily add another button for that, will put it on the wish list. |
Re: Getting back from "Find" mode, posted by Stefan Ritt on Wed Jan 11 21:12:13 2006 
|
| Yoshio Imai wrote: | | Is there a more direct way to get back to the unfiltered list view than selecting an entry and go to "List" or using "Find" again and clicking on "Back"? |
Yes, just click on the logbook tab on the very top of the page. |
|
Re: German language, posted by Stefan Ritt on Sat Mar 1 14:53:16 2008
|
| Salvatore wrote: |
|
In der Config-Datei habe ich den Eintrag "language = german" vorgenommen. Was unter Windows funktioniert, verweigert mir Linux: Die Umstellung des Logs auf Deutsch. Wer kann helfen?
Salvatore
|
Das kann drei Ursachen haben:
1) Die Installation under Linux ist nicht vollstaendig. Die Datei resources/eloglang.german muss vorhanden und von elogd lesbar sein
2) Der linux-daemon braucht ein Neustart nach jeder Aenderung der Sprache
3) Nochmal ueberpruefen, ob der Eintrag "language = german" auch wirklich vorhanden im richtigen config file ist. |
Re: German language, posted by Salvatore on Sat Mar 1 16:47:57 2008
|
Wen es interessiert:
der Eintrag "eloglang = german" gehoert in das Verzeichnis "usr/lib/elog/resources". Dort wird er von elogd ausgelesen.
| ZStefan Ritt wrote: |
|
| Salvatore wrote: |
|
In der Config-Datei habe ich den Eintrag "language = german" vorgenommen. Was unter Windows funktioniert, verweigert mir Linux: Die Umstellung des Logs auf Deutsch. Wer kann helfen?
Salvatore
|
Das kann drei Ursachen haben:
1) Die Installation under Linux ist nicht vollstaendig. Die Datei resources/eloglang.german muss vorhanden und von elogd lesbar sein
2) Der linux-daemon braucht ein Neustart nach jeder Aenderung der Sprache
3) Nochmal ueberpruefen, ob der Eintrag "language = german" auch wirklich vorhanden im richtigen config file ist.
|
|