Last default = <n>, posted by Alan Grant on Mon Apr 29 02:41:15 2019
|
According to the doc on the setting "Last default = <n>" it is intended to restrict Quick Filter searches to the last (n) days of entries, however when I add "Last default = 28" to config it still returns entries far older then 28 days when using the filter search. Am I misunderstanding, or implementing it wrong? We must restrict searches through QF to reduce load.
A couple other side questions which are related:
The doc on this setting says: "Last default = <n>
Some logbooks are very big ans searching through all entries with quick filter can be time consuming. This option sets a default value for the Date quick filter, so that by default only the <n> days are displayed." ...... I'm assuming that by saying "only the <n> days are displayed" that it has actually only searched <n> days ................ vs seaching ALL the logbooks but only displaying <n> days. Please confirm.
Also, why wouldn't the "28" days spec display in the Select Period box beside the Quick Filters? Otherwise it appears to me to be a separate and conflicting item. Best regards! |
Re: Last default = <n>, posted by Alan Grant on Mon Apr 29 17:48:13 2019
|
I just changed to Last default = 31 and even restarted elogd.exe but it still finds a given string older than 31 days. Also the default Select Period box value next to the QF's remains at All Entries. My understanding is it shoud behave like Find, where Show Last Default = 31 should default the display to Month, and also only search within the last month of entries.
| Stefan Ritt wrote: |
|
Indeed the description of the "Last default = <n>" option is not clear. I just updated that. If you have a quick filter "Date", then you have different options there like "Last day", "Last 3 days", "Last week", "Last month", "Last 3 months", "Last 6 months", "Last year". Each of these options has an underlying number of days, which are 1, 3, 7, 31, 92, 182, 364. In the "Last default = <n>" option you can only choose one of these seven options. Then this option is selected by default and the filter is applied accordingly. This lets you still change the date filter to a longer time period for example, but then with the penalty of longer search times.
So what you need is "Last default = 31" instead of 28 and it should work.
Stefan
| Alan Grant wrote: |
|
According to the doc on the setting "Last default = <n>" it is intended to restrict Quick Filter searches to the last (n) days of entries, however when I add "Last default = 28" to config it still returns entries far older then 28 days when using the filter search. Am I misunderstanding, or implementing it wrong? We must restrict searches through QF to reduce load.
A couple other side questions which are related:
The doc on this setting says: "Last default = <n>
Some logbooks are very big ans searching through all entries with quick filter can be time consuming. This option sets a default value for the Date quick filter, so that by default only the <n> days are displayed." ...... I'm assuming that by saying "only the <n> days are displayed" that it has actually only searched <n> days ................ vs seaching ALL the logbooks but only displaying <n> days. Please confirm.
Also, why wouldn't the "28" days spec display in the Select Period box beside the Quick Filters? Otherwise it appears to me to be a separate and conflicting item. Best regards!
|
|
|
Re: Last default = <n>, posted by Alan Grant on Wed May 1 15:28:41 2019 
|
I was just referring to "Show last default" (under Find) as a parallel example of how I assume "Last default" should function on the List page.
I also tried values 3 and 7 but "All entries" still displays in the "List period" box. A restart of elogd makes no difference.
Elog v3.1.2, Windows Server 2016 Std, 64 bit.
If you don't mind, I have attached my elogd.cfg. I realize you are quite busy so there is no rush. Thanks.
PS: I just noticed that the attached elogd.cfg indicates version 2.9.2 but it's actually 3.1.2 I have installed (just forgot to update the Welcome line).
| Stefan Ritt wrote: |
|
You say "Show Last Default = 31". This options applies only to the "Find" page, the option "Last Default = 31" works for the quick filter. Probably you have to change "Show Last Default" to "Last Default".
Stefan
| Alan Grant wrote: |
|
I just changed to Last default = 31 and even restarted elogd.exe but it still finds a given string older than 31 days. Also the default Select Period box value next to the QF's remains at All Entries. My understanding is it shoud behave like Find, where Show Last Default = 31 should default the display to Month, and also only search within the last month of entries.
| Stefan Ritt wrote: |
|
Indeed the description of the "Last default = <n>" option is not clear. I just updated that. If you have a quick filter "Date", then you have different options there like "Last day", "Last 3 days", "Last week", "Last month", "Last 3 months", "Last 6 months", "Last year". Each of these options has an underlying number of days, which are 1, 3, 7, 31, 92, 182, 364. In the "Last default = <n>" option you can only choose one of these seven options. Then this option is selected by default and the filter is applied accordingly. This lets you still change the date filter to a longer time period for example, but then with the penalty of longer search times.
So what you need is "Last default = 31" instead of 28 and it should work.
Stefan
| Alan Grant wrote: |
|
According to the doc on the setting "Last default = <n>" it is intended to restrict Quick Filter searches to the last (n) days of entries, however when I add "Last default = 28" to config it still returns entries far older then 28 days when using the filter search. Am I misunderstanding, or implementing it wrong? We must restrict searches through QF to reduce load.
A couple other side questions which are related:
The doc on this setting says: "Last default = <n>
Some logbooks are very big ans searching through all entries with quick filter can be time consuming. This option sets a default value for the Date quick filter, so that by default only the <n> days are displayed." ...... I'm assuming that by saying "only the <n> days are displayed" that it has actually only searched <n> days ................ vs seaching ALL the logbooks but only displaying <n> days. Please confirm.
Also, why wouldn't the "28" days spec display in the Select Period box beside the Quick Filters? Otherwise it appears to me to be a separate and conflicting item. Best regards!
|
|
|
|
|
|
Re: Last default = <n>, posted by Alan Grant on Fri May 3 16:02:33 2019
|
Ok thanks for taking the time to try it out. I definitely still show "All entries" in any case, so I will continue to try to resolve on my end and if I find the cause or solution I will share back on the forum.
First though, I noticed you ran 3.1.4 whereas I'm still on 3.1.2. I'm also on Windows Server 2016 and IE 11. Do you think any of that might make the difference?
| Stefan Ritt wrote: |
|
I just tried your elogd.cfg, and it works fine for me. So no idea what is wrong in your case.
Stefan
|
|
|
Re: Last default = <n>, posted by Alan Grant on Fri May 3 16:29:00 2019
|
Thanks again.
I noticed in the Change Log for 3.1.4 that there's a reference to something done with "Last default" in Sept 2018 so I think I will try to set up a Linux instance and try out 3.1.4. Regards.
Version 3.1.4, released September 26th, 2018
============================================
- Replaced sprintf by snprintf
- Changed midas.psi.ch to elog.psi.ch
- Fixed bug for redirect under two daisy-chained proxies
- Removed while(in_asend) which caused some browsers to block
- Implemented elogd.service for systemd daemon
- Implemented "max email attachment size"
- Limit max request size to 100 MB
- Allow ampersand in user names
- Added code to detect Unicode characters as HTML
- add "Email CSS URL" : use public copy of CSS for emails
- bugfix: replace hard-coded reference of "New" to loc("New")
- add "Subscription columns" : format list of logbooks for subscriptions in columns
- Added "interface" option
- Fixed crash on negative Content-Length in header
- Fixed "?npp=0" crash
- Added confirmation dialog before deleting an attachment
- Implemented "last default" to restrict quick filter display by default on the last n days
- Made header parsing case insensitive
- Switched to TLSv1_
| Stefan Ritt wrote: |
|
Yes I always run the current version from bitbucket. I haven't touched that code for "last default" since a long time, so I don't expect the verison to make a difference. Unfortuantely I have not Windows Server or IE for testing.
| Alan Grant wrote: |
|
Ok thanks for taking the time to try it out. I definitely still show "All entries" in any case, so I will continue to try to resolve on my end and if I find the cause or solution I will share back on the forum.
First though, I noticed you ran 3.1.4 whereas I'm still on 3.1.2. I'm also on Windows Server 2016 and IE 11. Do you think any of that might make the difference?
| Stefan Ritt wrote: |
|
I just tried your elogd.cfg, and it works fine for me. So no idea what is wrong in your case.
Stefan
|
|
|
|
|
Execute attribute, posted by Alan Grant on Fri May 10 04:34:36 2019
|
Apart from an inline shell command that can be run with the Execute attribute, is it possible to run an external script file? I would like to run a Powershell script with the Elog attribute data parameters passed to it upon Submit New entry. |
|
Re: Execute attribute, posted by Alan Grant on Fri May 10 15:01:52 2019
|
I think it was just a matter of my specific interepretation of the documentation, ie: using native OS shell commands vs any script language file containing shell commands or any app for that matter. Nevertheless I think you've answered my questiuon so it's all good. Thanks Stefan.
| Stefan Ritt wrote: |
|
I don't understand your question. There is no "inline" vs. "external" script. Using the "execute new = <command>", you run a script on the server side. Can be powershell under Windows or bash/csh under Linux. I remember however that there has been issues under recent windows in passing parameters to the shell. Linux certainly works fine, we usse it all the time.
| Alan Grant wrote: |
|
Apart from an inline shell command that can be run with the Execute attribute, is it possible to run an external script file? I would like to run a Powershell script with the Elog attribute data parameters passed to it upon Submit New entry.
|
|
|
|
Shell execute, posted by Alan Grant on Tue May 14 06:07:07 2019
|
I have the line in my elog config to run a Powershell script when submitting a New entry. I just send an email as a test:
Execute New = "Powershell.exe -ExecutionPolicy Bypass D:\SendEmail.ps1"
Fyi, the Powershell statement itself (Send-MailMessage -From 'MeterElog@winnipeg.ca' -To 'alangrant@mts.net' -Subject 'New meter entry' -Body 'TEST' -Priority High -DeliveryNotificationOption OnSuccess, OnFailure -SmtpServer 'citygw') works fine and the email is received when running it from the Powershell ISE app directly from the same elog vm server but not from within Elog with the above statement.
I'd like to first confirm that the syntax of the line Execute New = is correct, ie, double quoting the entire command. Can anyone please confirm. |
|