Hello all,
I have the issue, that we can't list entries older than 1 year, if "Last default = 31" (or any other number, but they are restricted to 1, 3, 7, 31, 92, 182, 364) is active.
The quick filter displays the option for "-- all entries --" but selecting this only reloads the default time frame (31 days).
A workaroud is to select a different time e.g. 1 day and then modifying the URL to ?last=1000 or so, gives acces to the old entries.
But this is not the intended way to do it.
The Find results are also affected by this. e.g. selecting 1.1.2020 to 1.6.2020 with "Last default = 31" yields 0 results.
The "Show last default" atrtribute for 1, 3, 7, 31, 92, 182, 364 work fine and overwrite the "last default" time in the quick filter.
In the Find page, there will be a "All entries" option at the top of the date selection box, if "Show last default" equals to 1, 3, 7, 31, 92, 182 or 364
(2, Bug: it is empty for "Show last default = 0" and not All entries")
Selecting "All entries" or the empty first value in the Find "show last:" date , will give a Find result with the "Last default" time constraint.
Thus it is not possible to get any entry older then the longst period possible (364 days), if you don't know about the workaround.
Best wishes,
Sebastian
PS: I use a self-compiled version of elog up to the 395e101 commit in the bitbucket repository with pull request #7 (which hasn't been merged for over 1,5 years) and a simple patch for our local LDAP. |
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! |
Hi folks,
I want to have Last day be a command in the List display, so I added:
List menu commands = New, Find, Import, Login, Logout, Config, Last day, Help
However, when Last day is selected, the command does not change to Last 2 days.
What is the right way to do this?
Thanks,
Mike
|
Is it possible to create a drop down menu for the last 3 days of log entries. Currently we have the last day, month, 3 month, etc.
Reason being, after a weekend most people would like to view the log entries for the last three days. Can anyone help me out here? |
I would appreciate if elog could provide a simple support for mathematical expressions.
A solution similar to wikimedia should be easy to implement and would help a lot.
http://www.mediawiki.org/wiki/Manual:Running_MediaWiki_on_Windows#Alternative_Solution
The idea is to parse the elog entry for a tag (e.g. <math></math>), extract the code, wrap it into a latex file, and pass this to latex, GhostScript, and ImageMagic. (The latter are already used by Elog, therefore the changes should not be too big.) The resulting image file would then be referenced by the elog html code.
Of course, the FCKeditor would not support LaTeX. However, the majority of elog-useres should be scientists and rather familiar with LaTeX. Therefore it should be fine if the original LaTeX code is saved (e.g. in the ALT-tag of the image) and the replacement "code to image" is undone for editing.
Kind regards,
Jochen |