| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
69600
|
Wed Jan 4 09:39:38 2023 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug fix | All | ELOG V3.1.4-493 | a hack around | Ahh, now I remember. Well, the I put that in like 25 years ago ;-)
Let's assume the user write a very long line and relies on the wrapping of the text box. So the input might look like the
first attachment. Then the user hits submit and gets just one long line (second attachment) and has to scroll one kilometre
to the right to see the full line. So there is an inconsistency between the entry form and what the user sees after the
submission. Having "wrap=hard" tells the browser to put CRLF where the wrapping in the textarea happens, so the text looks
the same during entry and after submission. If we remove the "wrap=hard", we would be back to the situation below in the two
attachments.
Opinions?
Stefan |
| Attachment 1: Screenshot_2023-01-04_at_9.38.51_.png
|
|
| Attachment 2: Screenshot_2023-01-04_at_9.39.09_.png
|
|
|
68714
|
Fri Jan 12 09:54:41 2018 |
 | Xuan Wu | wux@ihep.ac.cn | Question | Linux | 3.1.3 | about attachment | Hi all,
Some elog users of our site(CSNS) mentioned some advice about attachment:
1.Can imagemagick create thumbnail for .bmp file now?
2.Can re-sort the attachments after attachments uploaded by dragging or clicking up/down arrow or anything except deleting and re-upload attachment again?
3.Can add some description under the thumbnail of uploaded attachment? I've suggested them adding the description to the name of attchment or writing the detail in the text area. They are seem not very satisfied with this solution.
Any advice and suggestion will be appreciated.
Cheers |
|
68799
|
Tue May 15 04:41:23 2018 |
| Xuan Wu | wux@ihep.ac.cn | Question | Linux | 3.1.2 | about shiftcheck | Hi all,
I try to implement a shift check list for our facility. The attributes called "a1, a2, b1, b2 etc" are used in original shiftcheck.html， However, we would like to use "1.1, 1.2, 2.1, 2.2 etc". So I try to change the name of checkbox in shiftcheck.html and the attributes in elogd.cfg file to "1.1, 1.2, 2.1, 2.2 etc". The elog web page can display the attributes like "1.1, 1.2...", but the checked value of "on" seems not working. And I have used wirshark to monitor the http package, the request message seems correct, but the service response seems can't deal with attributes like "1.1, 1.2...", so is there a way to work around? |
| Attachment 1: shiftcheck1.png
|
|
| Attachment 2: shiftcheck2.png
|
|
| Attachment 3: shiftcheck3.png
|
|
|
68971
|
Tue May 14 09:40:58 2019 |
 | Xuan Wu | wux@ihep.ac.cn | Comment | Linux | 3.1.3 | add a little function--go to the specified page number | Hi all,
I added an input widget for pagination. I'd like to share it here, maybe someone needs. If there are many pages, specifying the page number will be useful.
The picture and patch code are in the attachment
Regards,
Xuan |
| Attachment 1: pagination.png
|
|
| Attachment 2: goto.patch
|
--- elogd.c.org 2019-05-14 10:12:01.891558950 +0800
+++ elogd.c 2019-05-14 10:44:38.165898395 +0800
@@ -19407,6 +19407,26 @@ void show_page_navigation(LOGBOOK * lbs,
rsprintf("<a href=\"%s\">%s</a>\n", ref, loc("All"));
}
+ sprintf(ref, "");
+ build_ref(ref, sizeof(ref), "", "", "", "");
+
+ rsprintf("<input id=\"setPage\" title=\"Goto\" type=number size=\"6\" onChange=\'getPage(\"%d\");\'>", num_pages);
+ rsprintf("<script language=\"JavaScript\" type=\"text/javascript\">\n");
+ rsprintf("<!--\n");
+ rsprintf("function getPage(max)\n");
+ rsprintf(" {\n");
+ rsprintf(" var value = document.getElementById('setPage').value;\n");
+ rsprintf(" value = parseInt(value);\n");
+ rsprintf(" if(value > max)\n");
+ rsprintf(" value = max;\n");
+ rsprintf(" if(value < 1)\n");
+ rsprintf(" value = 1;\n");
+ rsprintf(" var url = 'page' + value + \"%s\";\n", ref);
+ rsprintf(" window.location.href = url;\n");
+ rsprintf(" }\n");
+ rsprintf("//-->\n");
+ rsprintf("</script>\n");
+
rsprintf("</span></td></tr>\n");
}
|
|
1840
|
Thu May 25 19:41:51 2006 |
| Mark Bergman | mark.bergman@uphs.upenn.edu | Request | Linux | 2.6.1 | add field type to automatically email CC | I've got logbooks where I'm submitting entries on behalf of other users, or where other people should be notified of the ticket. This isn't a fixed list of people, and shouldn't be hard-coded into a config file. I've got a field to enter the user's e-mail address, but there's no action associated with that data.
I'd like to see a new field type that allows the entry of e-mail addresses, where each addresses supplied with the logfile entry would be automatically "CC'ed" in the notification e-mail. Ideally, people on the CC list would be (optionally) CC'ed when there are replies or edits to the original elog entry.
For example (snippet of fictional elogd.cfg):
-------------------------------
[web site]
Welcome Title = Issues regarding the web site
MOptions Category = Add links, Change content, Broken Link, Other
CCMailTo = Notification List
Attributes = Author, Category, Severity, Subject, Entry ID, Status, User, Login
Extendable Attributes = Category, Severity, Subject, Status, User, Login, Notification List
Required Attributes = Category, Subject, Status, User
------------------------------- |
|
855
|
Sun Dec 19 17:11:07 2004 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | Request | | | admin menu | Could you implemet and option 'admin menu' which gets displayed
when an 'admin' is logged in. This menu could e.g. also include 'Delete'
while the normal menu would not. |
|
67342
|
Tue Sep 18 17:57:47 2012 |
| Szu-Ching Peckner | speckner@nd.edu | Question | Linux | latest | admin user access admin page, not config page | We have multiple logbooks. Each user is admin user for his/her own logbook.
I want user be able to modify config file, but no access to user setting, such as see user list, change password, new user, remove user.
[logbook1]
Admin user = user1
Login user = user1, user2
Allow Config = user1
List Menu commands = Admin, Config
user1 click on Admin, it opens config file, when user1 click on save, user1 is brought to Config page, which has select user list on top, Change password, Remove user, New user buttons on bottom. Is there a way that admin user has access to config file, but no access to user info at all (not even presented to them). Is there a way after user1 click save, page doesn't go to that config page?
I could put
Deny Change password =
Deny Remove user
Deny New user
so when user1 click on those buttons, user1 will get command not allowed. However I would rather have user1 not even see that page.
|
|
1814
|
Wed May 3 00:16:42 2006 |
| Mark Bergman | mark.bergman@uphs.upenn.edu | Request | Linux | 2.6.1 | allow per-logfile attributes to be added/subtracted from the global settings | I think it would be a big enhancement to allow per-logbook attributes to be additions or subtractions from the global attributes, rather than replacing the global settings.
For example, the [global] section of my elogd.cfg reads:
Attributes = Author, Type, Category, Severity, Subject, Entry ID, Status
Extendable Attributes = Type, Category, Severity, Subject, Status
Options Category = Hardware, Software (OS and utilities), Software (Application), Network, Security, Other
Options Severity = None, Low, Medium, High, Critical
Options Status = Open, Closed, In-Progress, Suspended
Options Type = To-Do, Problem Report, Problem Fixed, Informational Note, Software Installation, Configuration, Other
Required Attributes = Type, Category, Subject, Status
I've also got an logbook for each server for hardware issues. Within those logbooks, I'd like to keep all the fields except the software fields, and add fields for memory and storage.
Adding 7 definitions to each server logbook makes the config file huge and difficult to edit, and it means that a future change to the global settings wouldn't propagate to the individual log files. I'd really like to do something like:
[server47]
-Options Category = Software (OS and utilities), Software (Application)
+Options Category = Storage, Memory
-Options Type = Software Installation
+Options Type = RAM Installation, Drive upgrade
As I see it, the initial "-" sign in front of an attribute or option would indicate that the fields listed should be deleted from the global set (if the field name is an exact match), and a leading "+" indicates that the given fields would be added to the global attribute of the same name, for that specific logbook.
The current behavior--without a leading "+" or "-" would be unchanged, so that existing config files don't change.
Thanks,
Mark |
|