Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 217 of 793  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subject
  67975   Tue Jun 9 15:28:53 2015 Reply Midas Userstefan.ritt@psi.chBug reportWindows3.1.0-3Re: Attribute not updated
> I saw in the doc that an attribute cant be bigger than 100 char. but I couldn't figure the maximum size for options...  I'm wondering if the issue comes from the browser not refreshing correctly or if its elog..

The number of possible options is limited in elog to 100. This is defined by MAX_N_LIST in elogd.h. You can try to increase it and recompile elogd, but no guarantee that this works.

The reason that it *sometimes* work is really a bug, I should do better limit checkings...

/Stefan
  67974   Tue Jun 9 15:22:03 2015 Reply Midas Userstefan.ritt@psi.chBug reportOtherthis oneRe: edit somebody else's draft
> this elog offers me to edit a draft message, then yells at me "only some other user can edit this draft!!!".
> methinks I should only be offered to edit draft messages that I own or I can edit. K.O.

I changed this behaviour now, so authors can only edit their own drafts. Furthermore, drafts are not shown any more in the elog lists. In addition, deleting of entries is allowed now again in this forum, so if someone creates a draft by accident, he/she can delete it.

/Stefan
  67973   Tue Jun 9 13:22:25 2015 Reply Stefan Rittstefan.ritt@psi.chQuestionWindowsV2.9.0-239Re: RSS Feed Not Providing Time Stamps For datetime Attributes

I fixed the problem in the current GIT version.

/Stefan

Kamen Nikolov wrote:

Can anyone help? Do I need to do something different or could this possibly be a bug that is fixed in a newer version?

Thanks,

Kamen

Kamen Nikolov wrote:

Hello,

I am using the RSS feed feature of Elog (V2.9.0-2396). I have a couple of attributes of type "datetime" (Start Time and Stop Time). I don't have a "Time Format" statement, so just using the default format. I am passing the Start Time and Stop Time attributes to the RSS Title with $Start Time and $Stop Time, but when looking at the RSS title in IE11 browser, I only see the date and not the time. Is there any way I can see the time as well?

Additional info:

I'm also passing the creation time of the Elog with $entry time and this is displaying correctly (both date and time).

Please let me know if I am doing something incorrectly?

Thanks

 

 

  67972   Tue Jun 9 13:01:50 2015 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows3.1.0Side effects of draft messages (was Fixed text)

I changed it such that drafts are not shown at all in ELOG. The only way you realize them is if you hit "new", and you will be prompted if there is any pending draft.

Andreas Luedeke wrote:
Hi Stefan,
I got an answer to a forum entry before I actually finished writing my post! It is obviously possible to reply to a draft message.
I think it would be excellent if draft messages would only be shown to their authors (except maybe in case of an anonymous author).
It feels wrong if I watch people while they making an entry ;-)
Anyway, it is just an idea.
Cheers
Andreas

 

Neal Grafton wrote:

Thanks Andreas

We are still playing around with ideas, just thought I'd ask, didn't think it was possible.

We are ok with setting attributes but this is new to us as yet so may have more questions later.

 

Andreas Luedeke wrote:
Hi Neal,
you can preload words into one attribute field, but one field is either editable or not, you cannot protect single words in a field.
But the ELOG way to solve this would be to have multiple attributes: you would get one entry field for each attribute.
Just look at this logbook: it has the attributes Icon, Author, Author Email, Category, OS, ELOG Version and Subject.
You can change the content of each attribute (except of "Author", that field is made here to be not editable), but as a normal user you cannot change the names in front of the fields.
Did you've set up the demo logbook and played around with it? Because your question suggests to me that you don't figured out yet what ELOG does. Or as a direct answer: no, it does not make sense to me ;-)
But I'm sure you'll figure it out: ELOG is best learned by trial and error.
Kind Regards
Andreas
Neal Grafton wrote:

Sorry I call this field that you write in the subject field, a little confusing.

So is there anyway to fix the indicated words in place in this typing space so you can enter the text you want next to them but be unable to delete them. (does this make sense?)

Neal

Andreas Luedeke wrote:
Dear Neal,
I don't understand your example. There is no such thing as a "subject field". You can define an attribute called "subject", like in this logbook.
But I would guess that you want to have five attributes "Time Off", "Reason", etc. that cannot be altered after an entry has been created? That's easy.
Or do you want to protect entries with specific content not to be deleted? That is not easy.
Please explain in more detail what you want to achieve, and I'll be happy to help.

Cheers, Andreas

Neal Grafton wrote:

I'd like to fix text or table in the subject field that can't be deleted or moved. 

Can that be done in config? Example - 

Time Off:

Reason:

Update By:

Estimated On time:

Detail:

 

 

 

 

 

 

  67971   Tue Jun 9 12:51:07 2015 Reply Stefan Rittstefan.ritt@psi.chQuestionLinuxV3.1.0-241Re: subject line bug on resumit elog entries as new?

I fixed both issues, now resubmitting an entry or submitting a new entry both yields "New LEOG entry".

Jacky Li wrote:

Hi,

I updated an old elog entry and resubmit it as new by checking the box resubmit as new.   Does the subject line should said it is a "New ELOG entry" instead of "Updated ELOG entry"?  Thank you.

Also when some people submit a new elog, the subject line is "Updated ELOG entry".  This is a bit odd.  I can't reproduce that bug when I did my test. 

Jacky 

 

  67970   Tue Jun 9 12:40:44 2015 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows3.1Re: LDAP docs

I do not officially support LDAP, since I don't have any server to test it. So it comes as a third party's contibution from https://github.com/vykozlov/elog-ldap.

To my knowlede LDAPS has not been implemented. You could post an issue the the github repository to ask the original author.

/Stefan

Stephen G wrote:

Thank you, I am looking to do LDAPS over 636 where would the certificate go (Does it go in the SSL folder?).

David Wallis wrote:

This is what I've been able to figure out, in terms of the elogd.cfg file:

LDAP server = server.domain:389
LDAP userbase = ou=people,o=domain.com,dc=domain,dc=com
LDAP login attribute = uid
LDAP register = 0

Stephen G wrote:

Could someone point me to the LDAP configuration docs, I searched to no avail.  I'm sure there is some big red ldap config button it, but I just can't find it.

 

 

 

  67969   Tue Jun 9 12:11:19 2015 Reply Stefan Rittstefan.ritt@psi.chCommentLinuxELOG V3.1.0-ac7Re: Emails generated by Elog

I fixed both issues in the current GIT version. Please double check it.

Stefan Ritt wrote:

I acknowledge these two bugs and will fix them soon.

David Pilgram wrote:

I am one who received an email every time there is a new entry in this forum.

I have just noticed that since May 20, every email contains the message "An old ELOG entry has been updated: "

whereas before that date, the vast majority say "A new ELOG entry has been submitted: "

Is this something to do with the saving of draft messages?

Talking of which, I see my draft of this message shows up in the forum before I have submitted it.

 

 

  67968   Tue Jun 9 09:39:14 2015 Reply Stefan Rittstefan.ritt@psi.chInfoAll3.1.0+Re: Different way CSS files are handled

Ok, fixed again.

Andreas Luedeke wrote:

Hi Stefan,

there is a little problem with the Makefile (on SL5 and SL6): the following line:

        @$(INSTALL) -m 0644 themes/default/* $(ELOGDIR)/themes/default/

/usr/bin/install: omitting directory `themes/default/icons'
make: *** [install] Error 1

When I go back to the old Makefile construct:

        @$(INSTALL) -m 0644 themes/default/icons/* $(ELOGDIR)/themes/default/icons/
        @for file in `find themes/default -type f` ;\
          do \
            if [ ! -f $(ELOGDIR)/themes/default/`basename $$file` ]; then  \
              $(INSTALL) -m 0644 $$file $(ELOGDIR)/themes/default/`basename $$file` ; \
           fi; \
          done

then it seems to work again.

Cheers

Andreas

Stefan Ritt wrote:

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

 

 

ELOG V3.1.5-fe60aaf