Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 753 of 806  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6445 Entries 
Goto page Previous  1, 2, 3 ... 752, 753, 754 ... 804, 805, 806   Next  
ID Date Icon Authordown Author Email Category OS ELOG Version Subject
  67935   Tue May 26 11:26:12 2015 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionWindows3.1.0Re: Fixed text
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:

 

  67938   Wed May 27 08:41:05 2015 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionWindows3.1.0Re: Fixed text
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:

 

 

 

  67940   Wed May 27 08:54:27 2015 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionWindows3.1.0Side effects of draft messages (was Fixed text)
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:

 

 

 

 

 

  67941   Wed May 27 10:50:41 2015 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionWindowsV2.9.0-239Re: RSS Feed Not Providing Time Stamps For datetime Attributes
Hi Kamen,
I've just tried it for V3.1.0 (6ab0fd5) and the described behaviour is unchanged.
It is even worse if you don't specify the "RSS Title": datetime attributes are just displayed as seconds of the epoch then.
I think this is a feature of ELOG at the moment.
You'll either need to dig into the code yourself or wait for Stefan to fix it.
 
I have an idea for a quick workaround:
you can create new hidden attributes, that contains a copy of the datetime attribute as a string, set by the subst command. You could then use those string attribute in the "RSS Title": that should work.
 
Cheers
Andreas
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

 

 

  67944   Fri May 29 09:38:40 2015 Question Andreas Luedekeandreas.luedeke@psi.chRequestOther3.1.0ELOG Version field in elogs/Forum
Hi Stefan,
could we change the format of the "ELOG Version" field in this logbook, that one can enter the full git revision
number?
That would be 13 characters.

Cheers
Andreas
  67945   Fri May 29 09:46:11 2015 Reply Andreas Luedekeandreas.luedeke@psi.chBug reportLinux3.1.0-2ELOG Forum: drafts cannot be deleted
I wanted to reply to the post "Three problems..." and then changed my mind. 
But since this logbook does not allow to delete entries (not even my own) I was neither able to remove the draft
nor the final entry.

Another strange thing: the draft got submitted when I hit the "Back" button after reopening it.

Cheers
Andreas
  67960   Fri Jun 5 19:01:05 2015 Reply Andreas Luedekeandreas.luedeke@psi.chInfoAll3.1.0+Re: Different way CSS files are handled

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

 

  67961   Fri Jun 5 19:08:17 2015 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinux3.1.0-2Re: ckeditor "Insert Timestamp" bug (was: Three problems with elogd 3.1.0-2)
I can confirm that there is currently a problem with the ckeditor "Insert Timestamp" button.
It apparently calls javascript code in ckeditor/plugins/timestamp/plugin.js
to catch a string from the URL "../../?cmd=gettimedate"
(I think this is one too many "../", but anyway). if you try this for the Forum:
https://midas.psi.ch/elogs/Forum/?cmd=gettimedate
it returns the wrong string. It is "Forum" instead of the date.

PS to David: The subject "Three problems ..." is not giving any indication what it is about. I would find it better in this case to post three entries to the Forum, each with a striking title :-)

David Wallis wrote:

Additional info:

"Time format = %Y" results in "2015" being pasted into the edit window when I hit the "time stamp" button.

"Time format = %m/%Y" results in the string "06/2015"

"TIme format = %m/%d/%Y" results in the string "06/04"

"Time format = %m/%d %H" results in the string "06/04 "

David Wallis wrote:

I just updated to the latest official release (V3.1.0-2411f95) and have these problems:

  1. The Time Stamp button pastes the logbook name when "Time format" is not specified in elogd.cfg, and when it is set to "%m/%d/%Y %H:%M", it adds the string "5/28/."
  2. Drag and drop for attachments dosn't work on either Chrome 37.0.2062.94 (64-bit) or FIrefox 31.5.3 (both on Linux). D&D works on the midas.psi.ch demo page. On my logbooks, the "drop attachements here" area does not have a dashed line border
  3. Auto-saving does not seem to be working.

The "Syntax of elogd.cfg" help file doesn't seem to reflect some of these features... it took me a while to find the settings for LDAP authentication. Am I just missing some settings for these features?

My users are loving the new functionality added in 3.1!

 

 

Goto page Previous  1, 2, 3 ... 752, 753, 754 ... 804, 805, 806   Next  
ELOG V3.1.5-3fb85fa6