Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 759 of 806  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject
  793   Tue Nov 16 17:49:54 2004 Question damon nettlesnettles@phgrav.phys.lsu.edu   elog password access without users
is there a way to set up a logbook so that a password is required to get
into it, but no username?
  797   Tue Nov 16 18:07:31 2004 Question Stefan Rittstefan.ritt@psi.ch   Re: elog password access without users
> i
  794   Tue Nov 16 18:07:31 2004 Question Stefan Rittstefan.ritt@psi.ch   Re: elog password access without users
> is there a way to set up a logbook so that a password is required to get
> into it, but no username?

Have a look under "Access control" in the manual. What you need is "Read
Password".
  795   Tue Nov 16 22:06:29 2004 Question damon nettlesnettles@phgrav.phys.lsu.edu   Re: elog password access without users
> > is there a way to set up a logbook so that a password is required to get
> > into it, but no username?
> 
> Have a look under "Access control" in the manual. What you need is "Read
> Password".

thanks. that seems to get me the functionality i needed. is there any way to
get rid of the username line when using the "Read Password" feature? as it is
now, you can either leave it blank or enter anything you want, so long as you
use the correct password it still works. however, to keep users from getting
confused, i think it would be better to only have a box asking you for the
password and not both the password and username.
  796   Tue Nov 16 22:45:24 2004 Reply Stefan Rittstefan.ritt@psi.ch   Re: elog password access without users
> thanks. that seems to get me the functionality i needed. is there any way to
> get rid of the username line when using the "Read Password" feature?

No, this is an HTTP standard. The dialog box is generated by your browser, and I
do not know any way to prevent it.
  801   Sat Nov 20 19:44:57 2004 Entry Ognyan Kulevogi@fmi.uni-sofia.bgRequestAll Partial Bulgarian translation
Hi, we are using ELOG for keeping track of a server maintainance.  I've
translated some of ELOG's strings.  The file is attached.  There will be
more translations, when I get inspired again ;-)
Attachment 1: eloglang.bulgarian
# To use Bulgarian translation, add the following lines to [global]:
#   Charset = windows-1251
#   Language = bulgarian

New = Създаване
Edit = Редактиране
Delete = Изтриване
Reply = Отговаряне
Download = Изтегляне
Find = Търсене
Select = Избиране
Last day = Последен ден
Move to = Преместване към
Copy to = Копиране към
Config = Настройване
Admin = Администриране
Login = Влизане
CSV Import = Импортиране на CSV
Logout = Излизане
Help = Помощ

Date = Дата
Author = Автор
Type = Тип
Category = Категория
Subject = Тема
Text = Текст

Back = Връщане
Submit = Запазване

New user = Нов потребител
Save = Запазване
Requested = Заявен
Activate = Активиране
Please login = Моля, влезте
Username = Потребител
Password = Парола
ID = ID
Logbook = Дневник
Goto ELOG home page = Сайт на ELOG
Upload = Слагане
Cancel = Прекъсване
Update = Обновяване
Search = Търсене
Last 10 = Последни 10
Change %s = Промяна на %s
Delete this logbook = Изтриване на този дневник
Rename this logbook = Преименуване на този дневник
Create new logbook = Създаване на нов дневник
Remove user = Изтриване на потребител
Forgot = Забравяне
Synchronize = Синхронизиране
Page %d of %d = Страница %d от %d
Logged in as = Влязъл сте като
Last x = Последен
Full = Пълен
Summary = Обобщен
Threaded = Нишковиден
Previous = Предишна
Last = Последна
First = Първа
Next = Следваща
First entry = Първи запис
Previous entry = Предишен запис
Next entry = Следващ запис
Last entry = Последен запис
Message ID = ID на съобщение
Entry time = Време на записа
Reply to this = Отговаряне на това
Please enter attribute '%s' = Моля, въведете атрибут "%s"
No attachment file specified = Не е зададен файл за прикачане
Submit modified ELOG entry? = Запазване на променен запис
Entry has been modified = Записът е променен
are required = са задължителни
Fields marked with = Полетата отбелязани с
Add %s = Добавяне на %s
please select = моля, изберете
Submit as HTML text = Запазване като HTML
Suppress Email notification = Подтискане на уведомяване чрез ел.поща
Resubmit as new entry = Запазване като нов запис
Attachment = Прикачен файл
GetPwdFile = GetPwdFile
A old entry has been updated on %s = Стар запис е обновен с %s
Email sent to = Изпращане на ел.поща до
  819   Fri Nov 26 17:13:27 2004 Smile damon nettlesnettles@phgrav.phys.lsu.edu   Securing Elog with SSL and Apache
there is a guide on the contributions logbook at

elog:Contributions/11

for securing Elog using SSL and Apache.
  820   Thu Dec 2 14:39:50 2004 Question Heiko Scheith.scheit@mpi-hd.mpg.deRequestLinux implement 'hide attribute' and 'sort attribute'
Could you implement a 'hide attribute' and 'sort attribute' config option?
While sort is probably not so easy to do the hide option would already 
be very useful.  What I want to do is to use elog to collect bibtex entries
which are then used to generate a bibtex file.  So, e.g. if the entry 
type 'Article' is selected I would like that all fields that do not make
sense are hidden.  Currently I just lock them.  The config looks like
this:

Attributes                  = Login, Bibtex Key, Entry Type, Address,
Annote, Author, Booktitle, Chapter, Crossref, Edition, Editor, Howpublished,
Institution, Journal, Key, Month, Note, Number, Organization, Pages,
Publisher, School, Series, Title, Type, Volume, Year, URL, Short Comment
Options Entry Type          = Article{1}, Book{2}, Booklet{3}, InBook{4},
InCollection{5}, InProceedings{6}, Manual{7}, MastersThesis{8}, Misc{9},
PhDThesis{a}, Proceedings{b}, TechReport{c}, Unpublished{d}
Required Attributes         = Entry Type
; ARTICLE
{1} Comment Author          = [required]
{1} Comment Journal         = [required]
{1} Comment Title           = [required]
{1} Comment Year            = [required]
{1} Locked Attributes       = Address, Annote, Booktitle, Chapter, Crossref,
Edition, Editor, Howpublished, Institution, Key, Organization, Publisher,
School, Series, Type


Instead of Locking the attributes, hiding them altogether would make the
entry form look much nicer.  
A further improvement would be to sort the attributes, e.g. for author I
would sort the like this, i.e. the more important entries first:

{1} Sort Attributes    = Author, Title, Journal, Volume, Pages, Year, Month,
Number, Note

Attributes not mentioned in the sort line could then be displayed 
in any order. 
ELOG V3.1.5-3fb85fa6