Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 574 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6457 Entries 
Goto page Previous  1, 2, 3 ... 573, 574, 575 ... 806, 807, 808   Next  
ID Date Icon Author Author Emaildown Category OS ELOG Version Subject
  67153   Tue Dec 13 22:18:04 2011 Reply Eoin Butlereoin.butler@cern.chQuestionLinux2.7.7-1Re: Cascading menus???

ron murphy wrote:

This may be already answered somewhere around here, but I could not find it. 

Question: Is it possible to have a pull down will a sub menu.  Something like,

 

Entry 1

Entry 2 --> Entry 2a

                   Entry 2b

                   Entry 2c

Entry 3

Entry 4

 The way I do this is

Attributes = Author, Subject, Run, Type, Hardware, Software, 

Options Type = Announcement{1}, Shift_Summary{2}, Physics_Discussion{3}, Analysis{4}, Hardware{5}, Software{6}
Options Hardware = Computers, Cryostat/Vacuum, DAQ, Environment Sensors, Magnets
Options Software = Analysis/Simulations, Control/Measurement, Detector, Linux, MIDAS, Sequencer, Windows
Show Attributes = Author, Type, Subject
{5} Show Attributes = Author, Type, Subject, Hardware
{6} Show Attributes = Author, Type, Subject, Software

 

  67752   Fri Jan 16 13:41:18 2015 Entry Eoin Butlereoin.butler@cern.chRequestAll-Configure default time range in 'Find'

Hello,

We have a very large elog database, and executing a 'Find' on the whole range takes several minutes, locking other users out of the elog for that time. It would be very nice if there could be an option to set the default value of the 'search last ...' option on the find page. Thanks in advance!

  67754   Mon Jan 19 11:09:31 2015 Reply Eoin Butlereoin.butler@cern.chRequestAll-Re: Configure default time range in 'Find'

Yes, this works, but users inevitably forget to select "last week" or whatever, and just leave it blank, which means their search unintentionally takes a long time. It would be much better if one could configure it to default to something "fast".

Stefan Ritt wrote:

Have you tried in the "Find" page to set a start date, or select "Show last: Month". This shoudl speed up searching quit a bit.
  67760   Thu Jan 22 17:04:03 2015 Reply Eoin Butlereoin.butler@cern.chRequestAll-Re: Configure default time range in 'Find'

This looks like exactly what I wanted, thanks!

Stefan Ritt wrote:

I added a new optoin "Show last default = <days>", where one can pre-set the "Show last" drop-down box. I think this is a good idea, so now people can configure their elog to a certain default in this parameter. Of course all settings in the Find page are AND'ed together, so if one restricts the search to tha last week, but then looks for a date more in the past, the result will be zero by definition. The change is in the GIT repository. If you cannot recompile the code yourself, you have to wait for the next release.

David Pilgram wrote:

By the way, in further testing, the "Show last" selection over-rides whatever two dates are selected, so if you ask for any entry in Dec 2014, but the "Show last" selects "week", nothing is found - very quickly.  I trust that is what you're after, Eoin.  I'll keep my change to the coding, but that's personal choice.

 

  67231   Mon Apr 9 15:02:24 2012 Question Grantenzedder@me.comBug reportWindows2.9.1Preset Text?
Hi Stefan,

I'm having a problem with 'Preset Text' now behaving differently in the latest release (2.9.1)?
My config file for example has always had: 'Preset Text = This is a test.', previously 'This is a test' was put
verbatim into the text area, now it seems to think whatever follows 'Preset Text =' is always a file and I end
up with 'File <i> This is a test. <i> cannot be found'?

I did notice a 'Print warning if "preset text" file cannot be found' line in the latest release notes, does this
now mean wherever I have used the method above I will now need to make a text file to match?

I'm using them embedded in conditional attributes if that makes any difference?

Thanks for your help.
  67652   Tue Jan 14 21:50:50 2014 Question Grantenzedder@me.comQuestionAll2.9.2Users logged out?

 Hi All,

I'm looking for a way (or if it is even possible?) for users to browse between logbooks without being logged out of their current logbook if they click on a logbook they are not authorised to access?
If they accidentally choose the wrong logbook they are forced to log back in again?

No guest access has been configured on any log.

TIA
 

  69795   Wed Jul 10 17:43:07 2024 Question Enrico Gamberinienrico.gamberini@cern.chBug reportLinux3.1.5-20240226broken http response when deployed on OpenShift

Hello!

We're setting up ELOG on OpenShift. ELOG is installed on a Alma Linux 9 image. The container and the elog demo works fine executing the docker image locally.

When deployed on OpenShift, we get a weird response, that results in a 502 Bad Gateway. The broken response looks like:
 

# curl -v -H 'X-Forwarded-User: enrico.gamberini@cern.ch' https://psi-elog-container2-elisa-epdtdi.app.cern.ch/demo/

<html>redir</html>
HTTP/1.1 200 Document follows
HTTP/1.1 200 Document follows
Server: ELOG HTTP 3.1.5-23df00d
Content-Type: text/html;charset=ISO-8859-1
Set-Cookie: elmode=Summary; path=/demo; expires=Friday, 07-Dec-35 06:30:26 GMT;
Pragma: no-cache
Cache-control: private, max-age=0, no-cache, no-store
 

Notice the HTML tag before the HTTP header, as well the duplicate HTTP header.

I understand that it might be difficult to reproduce, but any input would be very welcome!

Thanks!

Best,
Enrico

  69796   Thu Jul 11 15:25:19 2024 Reply Enrico Gamberinienrico.gamberini@cern.chBug reportLinux3.1.5-20240226Re: broken http response when deployed on OpenShift

Sorry for posting again but something else came up.

Actually, building from source (elog-3.1.5-1.tar.gz) works just fine on OpenShift too.

The problem described below only happens when installing the packaged binary elog-3.1.5-20240226.el9.x86_64.rpm.

Best,
Enrico

Enrico Gamberini wrote:

Hello!

We're setting up ELOG on OpenShift. ELOG is installed on a Alma Linux 9 image. The container and the elog demo works fine executing the docker image locally.

When deployed on OpenShift, we get a weird response, that results in a 502 Bad Gateway. The broken response looks like:
 

# curl -v -H 'X-Forwarded-User: enrico.gamberini@cern.ch' https://psi-elog-container2-elisa-epdtdi.app.cern.ch/demo/

<html>redir</html>
HTTP/1.1 200 Document follows
HTTP/1.1 200 Document follows
Server: ELOG HTTP 3.1.5-23df00d
Content-Type: text/html;charset=ISO-8859-1
Set-Cookie: elmode=Summary; path=/demo; expires=Friday, 07-Dec-35 06:30:26 GMT;
Pragma: no-cache
Cache-control: private, max-age=0, no-cache, no-store
 

Notice the HTML tag before the HTTP header, as well the duplicate HTTP header.

I understand that it might be difficult to reproduce, but any input would be very welcome!

Thanks!

Best,
Enrico

 

Goto page Previous  1, 2, 3 ... 573, 574, 575 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6