Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 28 of 806  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  66841   Tue Jun 8 15:48:06 2010 Question Yoshio ImaiRequestAll2.7.8inline-code
Hi, Stefan!

Sometimes, it is annoying that the
[code]
-Tag creates a line break, because there are situations where verbatim text inside the regular text flow is desirable (just like here). I would like to request an additional elcode-tag
[ilcode]
(in-line code) which translates to
<code>
instead of
<pre>
.

Cheers

Yoshio
  68139   Sun Oct 4 20:29:01 2015 Question Jacky Lizli@hawaii.eduQuestionLinuxV3.1.0-2411f95inline jpg to png

Hi,

We have a user who posted a lot of inline jpg.  The elog system converted those to png and thus cause the size of the elog to expand about ~4x of the original size.  It is caused the problem of entry size too large for email notifications.  Is there a way to turn off the conversion to png picture file?  May I know also know why it converts to png to store on the server?  Thank you very much.

Jacky

  65703   Wed Jan 23 15:37:58 2008 Agree stephanestephane.brisson@synchrotron-soleil.frRequestLinux2.7.1.2004inline button for upload image

Hello,

In elog version 2.7.1.2004, when I want to upload an image, after browsing I obtain a error message like < Upload command not unauthorized>. That is strange is the file is right uploaded in the logbook directory but not appear in the entry.

Thank you for your help.

 

Stéphane

  66492   Wed Aug 5 01:07:04 2009 Warning Richard Stamperr.stamper@rl.ac.ukBug reportAll2.7.7-2246init_resize sometimes not defined

Under some circumstances the New/Edit entry screen can invoke the init_resize() function in the onload handler for the <body> tag, but the init_resize() function is not defined.  In my case there is a log where the encoding is plain text (Default encoding = 1) and the message height is restricted (Message height = 4).  Creating or editing entries in this log generates warnings in the Firefox error console and alert boxes in IE about init_resize being undefined.

I think there is some missing logic.  In revision 2246 of elogd.c

  • at line 9924, if enc_selected = 1 then init_resize() is included in the onload handler, but
  • at line 9801, if enc_selected = 1 but at least one of the  "Message height" or "Message width" attributes is set then the code defining init_resize() is not include

I think you need to duplicate the checks on the Message height and Message width attributes at lines 9924, so that the init_resize() function is only included when defined.

Richard S

  887   Thu Jan 20 16:32:25 2005 Question John Habermannjohn.habermann@wilderness.org.auQuestionLinux increasing the height of the attribute display field
Was wondering  if it was possible to increase the height that the text box
for an attribute is displayed as. I would like to construct a form for a
weekly report which consist of a couple of text area attributes. I have
found the format option and can see how you can increase the width and
number of characters but not the height. This is what is have in the config
file for the log book:

-----------------------
[Weekly Reports]
Comment = The logbook for people to enter their weekly reports

Attributes = Author,Position, Achievements_last_week, Plans for Coming Week,
Issues and Concerns, Other Items to Report
Format Achievements_last_week = 0,messageframe,attribvalue,90,1000

Show text = 0
Enable Attachments = 0
---------------------------

Basically what I would like is for the text field for 4 of the attributes to
be something like the text area for the main body. Is that possible or is a
better way to incorporate the form into the main body somehow?

Thanks for any help. Been using elog for about a month now as a logging tool
for our IT team and this is the first time i have had to ask anything thanks
to the great documentation and the example. Great job Stefan
  68308   Wed Apr 27 21:27:36 2016 Question Devin Bougiedevin.bougie@cornell.eduQuestionLinux3.1.1inactive users
Hello,

Is it possible to remove the "active" checkbox a user sees when they click on "config"?  Alternatively, is it possible to have a new user arrive directly at the logbook they chose, rather than starting out at the config screen?

We are running elog-3.1.1 on SL6 with webserver authentication.  For the most part this works great, but somehow a few users become inactive after they login for the first time.  They claim they didn't un-check "active," but I can't think of any other way this would happen.

Many thanks,
Devin
  Draft   Tue May 10 12:35:40 2022 Reply Andreykowaraj4stuff@gmail.comBug reportMac OSXELOG V3.1.4-493important detail: No ^M after the last
> I think this is a bug report. 
> However, I am not sure whether the problem is in the new version of Apple's WebKit (15.4) or in the ELOG itself.
> 
> When we edit an ELOG record with Safari (as of version 15.4, new WebKit features added) there are extra "newline" symbols (actually ^M) being added after EACH line of the record.
> 
> So, for instance, if I edit the following page:
> ```
> aaa
> aaa
> aaa
> ```
> 
> then after a "Submit" (without actually any changes) the record becomes:
> ```
> aaa
> 
> aaa
> 
> aaa
> ```
> 
> Our current ELOG version is "ELOG V3.1.4-4936b76".
> Could you please have a look? 
  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