ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66542
|
Thu Sep 10 21:43:29 2009 |
| Devin Bougie | dab66@cornell.edu | Bug report | Linux | 2.7.7 | no "submit changes" pop-up with HTML editor |
When locks are enabled, users should see a pop-up window asking them to submit an entry if they edit an entry but then go away from that page or
close the browser without submitting the changes. However, it only appears as though this works when using the plain or ELCode editors. When
using the HTML editor, no such pop-up appears.
If possible, a fix for this would be greatly appreciated.
Many thanks,
Devin |
66547
|
Thu Sep 17 15:52:36 2009 |
| Holger Mundhahs | holger.mundhahs@vtg.com | Bug report | Windows | 2.7.7-2246 | Change / List Change doen't work anymore? |
Hello @all,
I'm not sure if this is a bug, but after upgradeing from 2.7.0 to 2.7.7 the Change <attribute> and List Change <attribute> doesn't work anymore. In my .cfg file I've:
In the old ELOG version I've "RIB-Board" as text in the page and the link works well. But now there is the following code generated:
Is the syntax changed from 2.7.0 to 2.7.7? What's the correct syntax for 2.7.7?
Best regards
Holger |
66548
|
Thu Sep 17 18:18:06 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.7 | Re: no "submit changes" pop-up with HTML editor |
> When locks are enabled, users should see a pop-up window asking them to submit an entry if they edit an entry but then go away from that page or
> close the browser without submitting the changes. However, it only appears as though this works when using the plain or ELCode editors. When
> using the HTML editor, no such pop-up appears.
>
> If possible, a fix for this would be greatly appreciated.
>
> Many thanks,
> Devin
Thanks for reporting this problem, I fixed it in SVN revision 2256. |
66550
|
Thu Sep 17 18:32:59 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.7.7-2246 | Re: Change / List Change doen't work anymore? |
Holger Mundhahs wrote: | Hello @all,
I'm not sure if this is a bug, but after upgradeing from 2.7.0 to 2.7.7 the Change <attribute> and List Change <attribute> doesn't work anymore. In my .cfg file I've:
In the old ELOG version I've "RIB-Board" as text in the page and the link works well. But now there is the following code generated:
Is the syntax changed from 2.7.0 to 2.7.7? What's the correct syntax for 2.7.7?
|
For security reasons (XSS or cross site scripting) , HTML code in attributes is not allowed by default. To turn it on (and if you know what you are doing), add following line to your configuration
Allow HTML = 1 |
66554
|
Fri Sep 18 07:39:02 2009 |
| soren poulsen | soren.poulsen@cern.ch | Bug report | Linux | 2.7.7 | User authorization file corruption |
Hi,
Here is what happens (I think) if E-log encounters a full file system where it keeps the user authorization file:
1. When a user connects, E-log will make a backup of the file. The backup will be corrupt since the file system is full.
2. E-log will modify the contents of the original file, and write it back. The file will be corrupt since the file system is full.
3. Now, both the backup and the normal file are corrupt and you cannot log on, until someone cleans up the file system and restores a valid copy of the file.
Would it be possible to fix this ? Like abort if step 1 is not successful. And restore the backup file if step 2 is not successful.
Thanks a lot for you help
Soren |
66560
|
Fri Oct 16 12:17:15 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.7 | Re: User authorization file corruption |
soren poulsen wrote: |
Hi,
Here is what happens (I think) if E-log encounters a full file system where it keeps the user authorization file:
1. When a user connects, E-log will make a backup of the file. The backup will be corrupt since the file system is full.
2. E-log will modify the contents of the original file, and write it back. The file will be corrupt since the file system is full.
3. Now, both the backup and the normal file are corrupt and you cannot log on, until someone cleans up the file system and restores a valid copy of the file.
Would it be possible to fix this ? Like abort if step 1 is not successful. And restore the backup file if step 2 is not successful.
Thanks a lot for you help
Soren
|
Ok, I finally found some time (I'm pretty busy these days) to add a check for a potential full file system in SVN revision 2258. So before the password file would get corrupted, elog shows an error message about the full file system and just stops to work until space is freed up. |
66563
|
Sat Oct 24 01:10:24 2009 |
| Gabriele Sirri | sirri@bo.infn.it | Bug report | All | 2.7.7-2254 | "Collapse to last = 1" problem when reply twice to the same entry |
Hello.
Please look at the entry 66525 of this forum (just 5 thread before this one):
-> chain.crt, posted by Gerhard Schneider on Thu Sep 3 21:55:52 2009 (66525)
|-> Re: chain.crt, posted by Stefan Ritt on Fri Sep 4 08:33:16 2009 (66526)
|-> Re: chain.crt, posted by Gerhard Schneider on Wed Oct 7 07:56:52 2009 (66556)
When you collapse the thread, it is collapsed to the 66526 instead of the 66556 (more recent)
+ Re: chain.crt, posted by Stefan Ritt on Fri Sep 4 08:33:16 2009
I guess it is because both 66526 and 66556 replies to the first entry.
I have the same problem with Elog v2.7.7-2246 and Windows.
In general, it seems to work well only if you always reply to the last entry of a thread.
Thank you.
b.t.w. : is there any tip to always force reply to the last entry of a thread? |
66565
|
Mon Oct 26 10:15:20 2009 |
| soren poulsen | soren.poulsen@cern.ch | Bug report | Linux | 2.7.7 | Re: User authorization file corruption |
Stefan Ritt wrote: |
soren poulsen wrote: |
Hi,
Here is what happens (I think) if E-log encounters a full file system where it keeps the user authorization file:
1. When a user connects, E-log will make a backup of the file. The backup will be corrupt since the file system is full.
2. E-log will modify the contents of the original file, and write it back. The file will be corrupt since the file system is full.
3. Now, both the backup and the normal file are corrupt and you cannot log on, until someone cleans up the file system and restores a valid copy of the file.
Would it be possible to fix this ? Like abort if step 1 is not successful. And restore the backup file if step 2 is not successful.
Thanks a lot for you help
Soren
|
Ok, I finally found some time (I'm pretty busy these days) to add a check for a potential full file system in SVN revision 2258. So before the password file would get corrupted, elog shows an error message about the full file system and just stops to work until space is freed up.
|
Great. We fully appreciate that your are busy (with other things than E-log).
Thanks for the resolution.
Soren |