Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 728 of 808  Not logged in ELOG logo
ID Date Icondown Author Author Email Category OS ELOG Version Subject
  67959   Fri Jun 5 14:24:34 2015 Idea Stefan Rittstefan.ritt@psi.chInfoAll3.1.0+Different way CSS files are handled

Hi,

I just implemented a different way CSS files are handled in ELOG. Previously, we had the default.css, which could be adjusted for specific needs. Some people did that (like myself). So I changed a few colors etc. When I now implement a new feature in elog, it might need a new CSS class which I put in default.css. But this means that people who have modified this file get it either overwritten, or do not get the new styles.

In order to fix this, the default.css is now called elog.css and is always inluded in any ELOG page. If one specifies a CSS file with "CSS = <file.css>", then this CSS file is loaded in addition to elog.css. So one can put only the modifications into that file and inherits all the rest from elog.css. If new features come in elog.css, the installation with the personalized CSS file will then get the new features from the new elog.css automatically, and just overwrite a few settings in the personalized file. Here is an example:

elog.css:

td {
  color:black;
  font-size:12px;

}

Personalized file special.css, activated with "CSS = special.css" in the elogd.cfg file:

td {
  font-size:18px;
}

This personalized file now overwrites the font size from elog.css to 18 pixel, while maintaining all the rest from elogd.css.

The modification is committed to GIT and will be contained in the next release of elog.

/Stefan

  68055   Wed Jul 22 03:09:39 2015 Idea Banata Wachid Ridwanjogjacard@yahoo.comInfoWindows3.1.0Revision for Indonesian Translation

hello, in my spare time, I try to fix some bugs, typo, and update for Indonesian translation

Attachment 1: elcode_indonesia.html
Attachment 2: eloghelp_indonesia.html
Attachment 3: eloglang.indonesia
#
# Indonesia translation by Banata and SABO Team (sabo.pusair-pu.go.id)
# Revision 1
# A more recent version may be available at:
# https://bitbucket.org/ritt/elog
#

New = Baru
Edit = Ubah
Delete = Hapus
Reply = Balas
Find = Cari
Last day = Hari terakhir
Last 10 = 10 terakhir
Config = Konfigurasi
Change password = Ubah sandi
Logout = Keluar
Help = Bantuan
Back = Kembali
Submit = Kirim
First = Pertama
Last = Terakhir
Previous = Sebelumnya
Next = Berikutnya
Copy to = Salin ke
Move to = Pindah ke
Save = Simpan
Cancel = Batal
Wrong password = Sandi salah
Please login = Silahkan masuk
Username = Nama pengguna
Password = Sandi
Old password = Sandi lama
New password = Sandi baru
ELOG change password = Ganti kata sandi ELOG
Several logbooks are defined on this host = Beberapa logbook didefinisikan di host ini
Please select the one to connect to = Silahkan pilih salah satu untuk dihubungkan
Change password for user = Merubah sandi untuk pengguna
Logged in as = Masuk sebagai
Entry date = Tanggal catatan
with = dengan
This is the last entry = Ini adalah catatan terakhir
This is the first entry = Ini adalah catatan pertama
Email sent to = Email dikirim ke
Email notification suppressed = Pemberitahuan email dimatikan
please select = silahkan dipilih
Suppress Email notification = Matikan pemberitahuan email
Resubmit as new entry = Kirim ulang sebagai catatan baru
Attachment = Lampiran
Reply to this = Membalas ini
In reply to = Balasan ke
Fields marked with = Kolom ditandai dengan
are required = diperlukan
Please check that it exists and elogd has write access = Silahkan periksa jika ada dan elogd mempunyai akses tulis
Error: Attribute <b>%s</b> not supplied = Kesalahan: Atribut <b>%s</b> tidak diberikan
Please go back and enter the <b>%s</b> field = Silahkan kembali dan isi di bagian <b>%s</b>
Please use your browser's back button to go back = Silahkan gunakan tombol kembali browser anda untuk kembali
ELOG find = Temukan ELOG
Find = Temukan
Search = Cari
Reset Form = Ulangi Isian
Summary only = Hanya ringkasan
Show attachments = Tampilkan ringkasan
Printable output = Keluaran cetak
Sort in reverse order = Urutkan terbalik
Start date = Tanggal mulai
End date = Tanggal akhir
Year = Tahun
Text = Teks
Search all logbooks = Cari semua logbook
Last %d days = %d hari terakhir
Last %d entries = %d catatan terakhir
No entries found = catatan tidak ditemukan
A new entry has been submitted on %s = Catatan baru telah dikirimkan di %s
Logbook = Logbook
Yes = Ya
No = Tidak
Error deleting message: status = Kesalahan menghapus pesan: status
Error: Command "<b>%s</b>" not allowed = Kesalahan: Perintah "<b>%s</b>" tidak diizinkan
Cannot open file <b>%s</b> = Tidak bisa membuka file <b>%s</b>
Cannot write to <b>%s</b> = Tidak bisa menulis ke <b>%s</b>
No SMTP host defined in [global] section of configuration file = Tidak ada host SMTP yang didefinisikan di bagian [global] di file konfigurasi
Display threads = Tampilkan berkas
Logbook is empty = Logbook kosong
Download = Unduh
and all its replies = dan semua balasannya
Message ID = ID Pesan
Not logged in = Tidak masuk
Login = Masuk
Page %d of %d = Halaman %d dari %d
all entries = semua isian
Login name = Nama login
Full name = Nama lengkap
ELOG user config = Konfigurasi pengguna ELOG
ELOG new user = Pengguna baru ELOG
Admin = Admin
Select user = Pilih pengguna
Remove user = Hapus pengguna
New user = Pengguna baru
Retype new password = Ketik ulang sandi baru
New passwords do not match, please retype = Kata sandi tidak cocok, ketik lagi 
Retype password = Ketik ulang sandi
exists already = sudah ada
Register as new user = Daftar sebagai pengguna baru
A new ELOG user has been registered on %s = Pengguna ELOG baru terdaftar pada %s
Email = Email
User "%s" registered on logbook "%s" = Pengguna "%s" terdaftar pada logbook "%s"
User [%s] has been deleted = Pengguna [%s] telah dihapus
Hit following URL to activate that account = Ikuti URL ini untuk mengaktifkan akun tersebut
ELOG registration = Pendaftaran ELOG
Your ELOG account has been activated on host = Akun ELOG anda sudah diaktifkan pada host
You can access it at = Anda dapat mengaksesnya di
Are you sure to delete these messages? = Apakah anda yakin ingin menghapus pesan ini?
Select = Pilih
All entries = Semua isian
Day = Hari
Week = Minggu
Month = Bulan
Show last = Tampilkan terakhir
Goto page = Pilih halaman
All = Semua
Display = Tampilan
entries per page = entri tiap halaman
Toggle all = Beralih semua
Selected entries = Isian yang dipilih
Collapse = Sembunyikan
Expand = Bentangkan
Full = Penuh
Summary = Ringkasan
Threaded = Rangkaian
Filters = Filter
Mode = Mode
Options = Pilihan
Error: start date after end date = Kesalahan: tanggal mulai setelah tanggal akhir
and all their replies = dan semua balasannya
Upload = Unggah
Requested = Diminta
A new ELOG user wants to register on "%s" = Pengguna ELOG baru ingin mendaftar pada "%s"
Search text also in attributes = Cari teks dalam atribut
Date = Tanggal
ID = ID
Forgot password? = Lupa sandi?
ELOG password recovery = Pemulihan kata sandi ELOG
No Email address registered with user name <i>"%s"</i> = Tidak ada alamat email yang terdaftar dengan nama pengguna <i>"%s"</i>
Error sending Email via <i>"%s"</i> = Kesalahan mengirim email melalui <i>"%s"</i>
Forgot = Lupa
User "%s" registered on host "%s" = Pengguna "%s" terdaftar pada host "%s"
Enter your user name or email address = Masukkan nama pengguna atau alamat email
Password recovery for ELOG %s = Pemulihan sandi untuk ELOG %s
Host = Host
Your ELOG account has been activated = Akun ELOG anda telah diaktifkan
Maximum number of attachments reached = Jumlah maksimum lampiran telah tercapai
on = pada
Entry is currently edited by = Entri saat ini diedit oleh
recipients = penerima
Suppress shell execution = Matikan eksekusi shell
Update = Perbarui
by = oleh
Change %s = Ubah %s
Add new option here = Tambahkan opsi baru di sini
Expand all = Buka semua
Add %s = Tambahkan %s
Synchronization = Sinkronisasi
Error: Value <b>%s</b> not allowed for boolean attributes = Kesalahan: Fehler: nilai <b>%s</b> tidak diizinkan untuk atribut boolean
Error: Attribute option <b>%s</b> not existing = Kesalahan: Opsi atribut <b>%s</b> tidak ada
Last submission = Pengajuan terakhir
Synchronize = Sinkronkan
No mirror server defined in configuration file = Tidak ada server mirror terdefinisi di file konfigurasi
user = pengguna
Maximum number of replies (%d) exceeded = Telah melebihi jumlah maksimum balasan (%d)
Entry can only be edited %1.2lg hours after creation = Entri hanya bisa diedit %1.2lg jam setelah dibuat
Display full entries = Tampilkan entri penuh
No entry selected for deletion = Tidak ada entri yang dipilih untuk dihapus
Cannot read entry from local logbook = Tidak dapat membaca entri dari logbook lokal
Cannot connect to host %s, port %d = Tidak dapat terhubung dengan host %s, port %d
Cannot receive "%s" = Tidak dapat menerima "%s"
Received wrong entry id "%d" = Menerima id entri salah "%d"
Entry #%d is locked on remote server = Entri #%d dikunci pada server jauh
Cannot save remote entry locally = Tidak dapat menyimpan entri jauh ke lokal
local = lokal
remote = jauh
Please delete %s or %s entry to resolve conflict = Harap menghapus %s atau %s untuk menyelesaikan konflik
Error sending local entry = Kesalahan mengirim entri lokal
Local entry submitted = Entri lokal dimasukkan
Error deleting remote entry = Kesalahan menghapus entri jauh
New entry cannot be written to directory "%s" = Entri baru tidak bisa ditulis ke direktori "%s"
Entry %s cannot be read from logbook "%s" = Entri %s tidak dapat dibaca di logbook "%s"
This entry has been deleted = Entri ini telah dihapus
Entries = Entri
Cannot connect to remote server "%s" = Tidak bisa terhubung dengan server jauh "%s"
Remote server is not an ELOG server = Server jauh bukan server ELOG
Incorrect remote ELOG server version %s = Salah versi server ELOG %s
Error accessing remote logbook = Kesalahan mengakses logbook jauh
Invalid HTTP header = Header HTTP salah
No user name supplied to access remote logbook = Tidak ada nama pengguna yang diberikan untuk mengakses logbook jauh
Synchronizing logbook %s with server "%s" = Sinkronisasi logbook %s dengan server "%s"
Configuration has been changed locally and remotely = Konfigurasi telah dirubah lokal dan jauh
Please merge manually to resolve conflict = Slahkan digabungkan manual untuk menyelesaikan konflik
Logbook "%s" does not exist on remote server = Logbook "%s" tidak ada pada server remote
Entry has been changed locally and remotely = Entri telah diganti lokal dan jauh
Entry deleted locally = Entri lokal dihapus
Changed local entry ID to %d = ID lokal entri dirubah ke %d
Entry deleted remotely = Entri dihapus dari jauh
All entries identical = Semua entri sama
Invalid mirror_id or entry_date = mirror_id atau entry_date tidak benar
Synchronize all logbooks = Sinkronisasi semua logbook
Calendar = Kalender
Remote entry received = Entri dari jauh diterima
Pick a date = Pilih tanggal
Please select at least one '%s' = Silahkan pilih paling tidak satu '%s'
Please select a '%s' = Silahkan pilih '%s'
Please enter month for attribute '%s' = Silahkan masukkan bulan untuk atribut '%s'
Please enter day for attribute '%s' = Silahkan masukkan hari untuk atribut '%s'
Please enter year for attribute '%s' = Silahkan masukkan tahun untuk atribut '%s'
Please enter attribute '%s' = Silahkan masukkan atribut '%s'
Entry time = Waktu entri
Start = Mulai
End = Selesai
From = Dari
After = Setelah
to = untuk
Before = Sebelum 
Previous Year = Tahun sebelumnya 
Next Year = Tahun berikutnya
Please enter numeric value for '%s' = Silahkan isi nilai numerik untuk '%s'
Error: Attribute <b>%s</b> must be numeric = Kesalahan: Atribut <b>%s</b> harus numerik
3 Months = 3 Bulan
6 Months = 6 Bulan
Error sending local message = Kesalahan mengirim pesan lokal
Error receiving message = Kesalahan menerima pesan
Are you sure to delete this entry? = Apakah anda yakin menghapus entri ini?
ELOG CSV import = Impor CSV ELOG
Import = Impor
CSV filename = Nama file CSV
Field separator = Pemisah kolom
Edit entry = Edit entri
Delete entry = Hapus entri
CSV Import = Impor CSV
Derive attributes from CSV file = Menurunkan atribut dari CSV
Comma = Koma
Semicolon = Titik koma 
Preview import = Pratinjau impor
CSV import preview of %s = Pratinjau impor CSV dari %s
Too many attributes in CSV file = Terlalu banyak atribut di file CSV
%d entries successfully imported = %d Entri sukses diimpor
No 'Attributes' option present in %s = Tidak ada opsi 'Atribut'di %s
CSV ("," separated) = CSV (dipisahkan ",")
CSV (";" separated) = CSV (dipisahkan ";")
Auto detect = Deteksi otomatis
text = Teks
Column header '%s' must be present in CSV file = Tajuk kolom '%s' harus ada di dalam file CSV
Fill text body = Isi tubuh teks
Please re-enter filename = Silahkan masukkan kembali nama file
Last x = x terakhir
Activate = Aktifkan
Entry has been modified = Entri telah dimodifikasi
No attachment file specified = Tidak ada lampiran yang ditentukan
Delete this logbook = Hapus logbook ini
Rename this logbook = Ubah nama logbook ini
Create new logbook = Buat logbook baru
Syntax error in config file = Kesalahan sintaks di file configurasi
Email notification = Pemberitahuan email
Are you sure to delete logbook "%s"? = Apakah anda yakin menghapus logbook "%s"? 
Logbook "%s" exists already, please choose different name = Logbook "%s" sudah ada, silahkan pilih nama lain
Rename logbook = Ubah nama logbook
Enter new logbook name = Masukkan nama logbook baru
Logbook name = Nama logbook
Use existing logbook as template = Gunakan logbook yang ada sebagai contoh
none = tidak ada
URL is redirected to: = URL diarahkan ke:
Remote config should be received = Konfigurasi dari jauh seharusnya sudah diterima
Local entry should be submitted = Entri lokal harus dimasukkan
Remote entry should be received = Entri jauh seharusnya diterima
Local entry = Entri lokal
%s should be deleted = %s harus dihapus
Entry should be deleted locally = Entri harus dihapus secara lokal
Local entry ID should be changed to %d = ID entri lokal harus dirubah menjadi %d
Remote entry = Entri jauh
Entry should be deleted remotely = Entri harus dihapus dari jarak jauh
Click here to delete %d entries = Klik disini untuk menghapus entri %d
Click here to delete this entry = Klik disini untuk menghapus entri ini
Maximum number of attribute options exceeded = Jumlah maksimum pilihan atribut telah terlewati
Please increase MAX_N_LIST in elogd.c and recompile = Silahkan meningkatkan MAX_N_LIST di elogd.c dan kompilasi ulang
You can "steal" the lock by editing this entry = Anda bisa "mencuri" kunci dengan mengedit entri ini
Several logbooks groups are defined on this host = Beberapa grup logbook didefinisikan pada mesin ini
Please select one to list the logbooks in that group = Silahkan pilih salah satu logbook dari daftar  dalam kelompok
No logbook defined on this server = Tidak ada logbook yang didefinisikan dalam server ini
Goto ELOG home page = Menuju ke halaman utama ELOG
Please enter "%s" = Silahkan masukkan "%s"
Change config file = Ubah file konfigurasi
Please check that it exists and elogd has write access and disk is not full = Silahkan dicek jika ada, mempunuyai hak akses dan disk tidak penuh
Show = Tampilkan
Hide = Sembunyikan
Hide all = Sembunyikan semua
Show all = Tampilkan semua
This logbook requires authentication = Logbook ini memerlukan otentifikasi
Attachment file <b>"%s"</b> empty or not found = File lampiran <b>"%s"</b> kosong atau tidak ditemukan
Case sensitive = Dibedakan
List = Daftar
Date must be between 1970 and 2037 = Tanggal harus antara 1970 dan 2037
... 192 more lines ...
  68101   Wed Aug 26 09:18:17 2015 Idea Andreas Luedekeandreas.luedeke@psi.chQuestionLinux2.9.2Re: Send e-mail based on a hierarchy of attributes?

Yes, this can be done. See below for an example configuration.

Attributes = entrytype, category
Options entrytype = routine{1}, problem{2}
Options category = software, hardware

{1} Email category software =
{1} Email category hardware =
{2} Email category software =
1@opq.rst, 2@uvw.xyz
{2} Email category hardware = a@bcd.efg, h@ijk.lmn

Phil Rubin wrote:

Is there a way to distribute e-mail based on the consideration of several attributes and values?  A simple example:  attributes type and category have several different values, say, routine and problem for type and hardware and software for category, but one would only like messages sent when there's a problem to different sets of hardware or software types.  Thus:

Email

type routine   category hardware = no message

                        category software = no message

type problem  category hardware = a@bcd.efg, h@ijk.lmn

                         category software = 1@opq.rst, 2@uvw.xyz

 

  68121   Tue Sep 22 15:04:55 2015 Idea Edmund Hertleedmund.hertle@kit.eduRequestAll3.1.1Suggestion for tooltips and/or comments

Hey,

if you define a Tooltip at the moment it is only displayed on the attribute. I would like it very much if it would also be displayed on the values (on the right column in the detailed view and on the whole column in the list view), since we are using the tooltips to define the units of the attribute and it would be nice to pop up when you hover a value.

As for the comment it would be nice to have a flag to also show the comment on the detailed view while looking at an entry. At the moment it is only showed when creating a new entry. Again we use this field to define the units.

This is an example of how we use these options:

attributes = Fill Number, Beam Current, Beam Energy, Beam Lifetime, RF Voltage S2, RF Voltage S4, RF Frequency, Synchrotron Frequency

Comment Beam Current = in mA
Comment Beam Energy = in GeV
Comment Beam Lifetime = in hh:mm
Comment RF Voltage S2 = in kV
Comment RF Voltage S4 = in kV
Comment RF Frequency = in MHz
Comment Synchrotron Frequency = in kHz

Tooltip Beam Current = in mA
Tooltip Beam Energy = in GeV
Tooltip Beam Lifetime = in hh:mm
Tooltip RF Voltage S2 = in kV
Tooltip RF Voltage S4 = in kV
Tooltip RF Frequency = in MHz
Tooltip Synchrotron Frequency = in kHz

Cheers

eddy

  68135   Wed Sep 30 09:28:39 2015 Idea Andreas Luedekeandreas.luedeke@psi.chQuestionWindows2.7.3Re: Syntax for conditional list display
Hi Terry,
if you really want to do it, you can find a way to make it work. But it is not straight forward and not what ELOG is made for. Here some ideas how it could work:
  • ELOG allows you to have different commands for different users. You could allow "New" and "Edit" for normal users, but "Reply" only for administrators.
  • You can use "Subst on reply <attribute> = <string>" to set a specifc fields only on reply. 
    • You would hide "status" & "assignee" for new entries or edit (Show Attributes Edit = <list>), and show a "set status" field instead.
    • The line "Subst on reply status = $set status" would take care, that only an administrator can set "status" with a reply to the original entry (+ a "set assignee" field, etc.). While normal users could set "set status", it would not change the "status" field. You could provide a comment or tooltip to explain that.
    • The list view or single entry view should not show the "set status", but only the "status" attribute (List display = <list>, Show Attributes = <list>).
  • Use "Propagate attribute = status, assignee" to take care, that the original entry gets their fields set accordingly.

This is how you could do what you want. But bugzilla can do a lot more if you are looking for a bug tracking software.

Cheers, Andreas

Terry L wrote:

Hi Eddy,

Thank you for your response.  I had a feeling that was the case, but I had high hopes! :)  The reason I would like this feature is because I am trying to use ELOG as a software anomaly tracking log, where any user can create an ELOG and fill out "category", "computer" etc, but only administrators can fill out the "status" & "assignee".  If I am lucky, this will be an added feature in a future revision.

Thanks again,

-Terry

Edmund Hertle wrote:

Hey Terry,

I don't think this is possible, since in general you cannot define config settings in a way that it would only affect specific users. For example, you also cannot have different themes for different users (as stated here: https://midas.psi.ch/elogs/Forum/68112 )

Cheers

eddy

Terry L wrote:

Good Morning,

I would like to limit the ability to edit certain attributes in an ELOG logbook, depending on the user who is logged in.  I.e. if "guest" or a standard "login user" is logged in, I only want to allow the user to edit "attribute1" & "attribute2" of say, 5 attributes.  However, if an Admin user or specific user, say "Terry" or "Bob" is logged in, I want to allow ALL 5 attributes to be editable.  To expand on this, I may want to even limit the visibility of the attributes as well.

I've read though "Condition Attributes" section of the help page, but it is not clear to me how/if I can do this?  Is that section even relevant to what I want to accomplish?

Can anyone provide some guidance?

Thank you for your time & help!

Sincerely,

Terry

 

 

 

  68213   Tue Jan 12 11:35:55 2016 Idea Johan Forsbergjohan.forsberg@maxlab.lu.seRequestLinuxV3.1.0-2411f95Prefill attributes for new post

Hi all,

I have a use case for ELOG where I need to be able to "prefill" some attributes in the "cmd=new" form, based on the URL.

To illustrate, imagine a link that takes the user directly to the form for creating a new post, with the "Subsystem" attribute already filled out to "Vacuum".

Is this possible already? I've tried naively using URL parameters (e.g. "&Subsystem=Vacuum") but that does not work. If it's not implemented, I think it would be a useful feature to have (and quite important for my particular use case). I could create a new post first using the "elog" tool, with the desired attributes set, but it makes more sense to defer the actual creation of the post to the user, i.e. he/she might change their mind before pressing "submit".

Thanks,

Johan Forsberg, MAX IV Laboratory, Sweden

  68214   Tue Jan 12 11:48:57 2016 Idea Andreas Luedekeandreas.luedeke@psi.chRequestLinuxV3.1.0-2411f95Re: Prefill attributes for new post
Hi Johan,
yes, it is possible. And you were actually very close :-)
In order to pass preset-parameters within a URL, you just need to prefix the fieldname with a "p". In your example, you would write "...&pSubsystems=Vacuum".
Here is an example for the Linux Demo logbook:
https://midas.psi.ch/elogs/Linux+Demo/?cmd=New&pAuthor=Santa+Claus&pSubject=Christmas+Presents&pType=Problem+Fixed&pCategory=Hardware
 
This feature is even already documented: https://midas.psi.ch/elog/userguide.html#misc :-)
 
I wish you a Happy New Year!
Andreas
Johan Forsberg wrote:

Hi all,

I have a use case for ELOG where I need to be able to "prefill" some attributes in the "cmd=new" form, based on the URL.

To illustrate, imagine a link that takes the user directly to the form for creating a new post, with the "Subsystem" attribute already filled out to "Vacuum".

Is this possible already? I've tried naively using URL parameters (e.g. "&Subsystem=Vacuum") but that does not work. If it's not implemented, I think it would be a useful feature to have (and quite important for my particular use case). I could create a new post first using the "elog" tool, with the desired attributes set, but it makes more sense to defer the actual creation of the post to the user, i.e. he/she might change their mind before pressing "submit".

Thanks,

Johan Forsberg, MAX IV Laboratory, Sweden

 

  68217   Tue Jan 12 15:06:42 2016 Idea Johan Forsbergjohan.forsberg@maxlab.lu.seQuestionLinuxELOG V3.1.0-241Monitoring a logbook for changes

Hi again!

I've another need that you probably already thought of :)

I'd like to be able to efficiently monitor a logbook for changes (new or edited posts) somehow. The most reasonable way I've found so far is to periodically poll a search that looks for posts after the time of the last poll. But that might note be very efficient, especially if the polling period gets short (or number of clients grows).

Is there some other feature that could be used for this? I was thinking maybe the ETag or Last-Modified HTTP header field could be used to show changes to a logbook by just reading the headers, but it would also require HEAD request support which does not seem to be there.

Cheers,

Johan

ELOG V3.1.5-3fb85fa6