ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
69370
|
Mon Jun 14 17:25:02 2021 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | All | V3.1.4 | Bug Report with CSS includes (was Re: How to format a column in list display?) | Okay, found some solution for my problem:
List Change Pikett = <div class="pikett">$Pikett</div>
CSS=pikett.css
And file themes/default/pikett.css contains:
.pikett {
background-color:white;
font-size:16px;
font-family:monospace;
text-align:left;
}
That works like a charm - until I log in to the logbook. Then the include of the CSS in the header is garbled with some "prefix" of random chars:
And a quick check in the source code shows some bad code:
L7615: function "show_html_header"
rsprintf("<link rel=\"stylesheet\" type=\"text/css\" href=\"%s%s\">\n", css_base, css);
Here css_base is a not initialized local variable of the function. In fact the above line is the only reference of that variable char css_base[1000].
The bug is still present in elog-3.1.4-611489b
Andreas Luedeke wrote: |
There is the nice conditional formatting feature for List display:
Cell Style <attribute> <value> = <style>
I would like to use it without conditions: some attributes should always be formatted in a specific way.
Specifically I want a generated attribute (combined from other attributes) to be display in monospace font.
The "Format Pikett = 0, attribname, messagelist " works nicely for the single entry display (pik1), but not for List view (pik-list).
Would it be possible to create a new command "List format <attribute> = <css_class_name>,<css_class_value>,<width>,<size> ", or is there another way to achieve this?
|
|
69372
|
Mon Jun 14 18:51:59 2021 |
| Sebastian Schenk | sebastian.schenk@physik.uni-halle.de | Bug report | All | V3.1.4 | Bug Report with CSS includes (was Re: How to format a column in list display?) | Hi Andreas,
the bug you have found was already reported in an earlier issue, together with the same solution you have found.
https://elog.psi.ch/elogs/Forum/69368
Best wishes,
Sebastian
Andreas Luedeke wrote: |
[...]
That works like a charm - until I log in to the logbook. Then the include of the CSS in the header is garbled with some "prefix" of random chars:
And a quick check in the source code shows some bad code:
L7615: function "show_html_header"
rsprintf("<link rel=\"stylesheet\" type=\"text/css\" href=\"%s%s\">\n", css_base, css);
Here css_base is a not initialized local variable of the function. In fact the above line is the only reference of that variable char css_base[1000].
The bug is still present in elog-3.1.4-611489b
|
|
372
|
Mon Jun 16 17:44:49 2003 |
| nickc1 | nick@nick.com | Bug report | Linux | 2.3.8 | Bug Found | Ive just been alerted to a bug with email notifications in Elog.
Basically if your log book contains a space then the URL that is sent in
emails when creating tickets or updating old entries doesnt put %20 (IEs
space) inthe URL it leaves a space hense breaking the link.
for example
Correct Way prior to 2.3.8
http://192.168.0.1:99/Provisioning%20Request/35
Broken way with new version
http://192.168.0.1:99/Provisioning Request/35
^
Link is broken at this point
My config looks like this
Email Status Assigned = $Owner@abc.co.uk
Email Status Re-Assigned = $Owner@abc.co.uk
Email Status Completed = $Requester@abc.co.uk
Email "Send Update Email" Yes = $Requester@abc.co.uk
Use Email Subject = A Provisioning Ticket has been assigned to you or
completed
Use Email From = NetworkTeam@abc.co.uk |
2148
|
Thu Mar 1 15:55:52 2007 |
| Robert-Jan Schrijvers | Robert-Jan.Schrijvers@isoft.nl | Bug report | Windows | V2.6.3-176 | Bug | when i was editting my Admin file, by mistake i typed the next line:
[a}Options Sessies = p-zis-pr1{1}, p-szh-pro{2}, p-dia-pro{3}, a-zis-ac1{1}, a-zis-ac2{2}, a-dia-acc{3}, ---------------------, Anders
{b} Options Sessies = FSC Pro{4}, FSC Acc{4}, Risc/Bus/Sms Pro{5}, Risc/Bus/Sms Acc{5}, ---------------------, Anders
{c} Options Sessies = BAO, BEH, BAOMPSO, BEHMPSO, Demonstrator, AFS, PTG, BSN, ---------------------, Anders
{d} Options Sessies = Wijziging, Storing
the next thing happened was that eLog created a new log which wasn't editable at all, the only thing i could do was deleting it (i created a monster...;-)
The first line/rule with the [ become the title, all other entries in the Admin file were used as a new Admin file. |
1607
|
Wed Jan 18 17:20:45 2006 |
| Chris Warner | christopher_warner@dcd.uscourts.gov | Bug report | Linux | 2.6 | Buffer Overflow? | Users can access root level directories by using a modified URL. I saw on some security web sites that this was a problem in previous versions. Was it not fixed in 2.6?
To recreate enter http://yourhost.yourdomain.com/../../../../etc/passwd
view your password file in the browser.
If this was previously reported, is there a fix?
Chris Warner |
1769
|
Mon Mar 13 12:51:36 2006 |
| Yoshio Imai | | Bug report | Linux | 2.6.1-1671 | Broken thread structure in Forum? | Hi!
I noticed that this thread seems to be broken in the Forum. When I view the thread start in single view (http://midas.psi.ch/elogs/Forum/1739), I have access to all subsequent posts, but the first reply seems to be interpreted like a new thread, i.e. when clicking onto it (http://midas.psi.ch/elogs/Forum/1741), the thread start is no longer displayed and accessible in the list of posts. Is this intentional, or is it a bug?
Yoshio |
1770
|
Mon Mar 13 12:57:33 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.6.1-1671 | Broken thread structure in Forum? |
Yoshio Imai wrote: | I noticed that this thread seems to be broken in the Forum. When I view the thread start in single view (http://midas.psi.ch/elogs/Forum/1739), I have access to all subsequent posts, but the first reply seems to be interpreted like a new thread, i.e. when clicking onto it (http://midas.psi.ch/elogs/Forum/1741), the thread start is no longer displayed and accessible in the list of posts. Is this intentional, or is it a bug? |
Some how it got screwed up, such that ID 1741 did not have a back-link to 1739. I have no clue how this could have happened, but I fixed it by manually editing the log file. |
1771
|
Mon Mar 13 13:19:09 2006 |
| Yoshio Imai | | Bug report | Linux | 2.6.1-1671 | Broken thread structure in Forum? |
Stefan Ritt wrote: | I have no clue how this could have happened, but I fixed it by manually editing the log file. |
I also have never come across anything like this in our logbooks (approx. 10000 entries), so it doesn't look like a bug. |
|