| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
257
|
Fri Mar 21 16:52:12 2003 |
 | Recai Oktas | roktas@omu.edu.tr | Info | | | Re: Re: Elog and SSL | Ooops, I destroyed the original post, now how can we fix this :) |
|
66622
|
Wed Nov 18 13:51:55 2009 |
| soren poulsen | soren.poulsen@cern.ch | Question | Windows | 2.7.6-2236 | Re: Re: Elog & SSL Export to CSV , Problem |
| Stefan Ritt wrote: |
|
| Chuck Brost wrote: |
|
Stefan, would it be possible to make the following change so that the document is not cached and at the same time it is possible to save it.
The change would entail replacing the "Pragma: no-cache" directive with an "Expires: " <HTTP-date> where <HTTP-date> is the same as Date header value. Please see section 14.21 of http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
Hopefully there are no other side effects to this change.
|
ok, so I removed the "Pragma: no-cache". With IE it looks fine now, and if I repeat it two times it always gets is from elog and not from the cache due to the "Expires:" statement. The "no-cache" came from old days when some browsers did not yet support the "Expires" tag. I hope that this is better now, so let's see when we get the first complaints. The modification is in SVN revision 2265.
|
This seems to work fine. |
|
66621
|
Tue Nov 17 19:31:46 2009 |
| Heinzmann | catman333@web.de | Bug report | Windows | 2.7.7 2246 | Re: Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5 |
| David Spindler wrote: |
|
| Stefan Ritt wrote: |
|
| David Spindler wrote: |
|
I upgraded 2.7.5 rev 2175 to 2.7.7 rev 2246 last Thursday. I tested it with several logbooks with no problems. However I received a rep[ort today that it was down. I discovered whenever I tried to open a logbook entitled "Equipment Reservation" in the folder "EquipmentReservations" Elog would crash. I checked the elog.log file with no entries in it other than showing when it was restarted. I backed up to 2.7.5 and had no porblems with the same logbook. I repeated the upgrade to 2.7.7 with the crash problem returning. I am now back on 2.7.5 with no problems.
I just decided to try 2.7.6 rev 2239 and had the same results as 2.7.7.
This is running under Win2K with SP4 as an automatic service on port 80.
I am also running Elog V2.7.4-2118 on a different port (8080) simultaneously with no problems.
If you wish I will send the elog.cfg file. Anything else I can do to help, please let me know.
|
I need to reproduce your problem. Therefore I need the configuration and the xxxxxxa.log file containing the offending entries. You can strip it down to the minimum needed to do the crash.
|
In the process of trying to reduce it to a minimum I discovered that the entry that appears to be causing the crash is this:
|
Hi,
I´m using 2.7.7 rev 2246 and tested it with my logbooks without any problems. But today I had no chance to reach them anymore. Strange.
Regards,
Michael
|
|
1974
|
Tue Oct 10 16:15:21 2006 |
| Ben Shepherd | bjs54@dl.ac.uk | Request | All | 2.6.2-1714 | Re: Re: 'Inline' button for attachments |
| Stefan Ritt wrote: |
| Ben Shepherd wrote: | Hi,
and it does exactly what you want. |
cool! thanks. |
|
2085
|
Mon Nov 20 22:20:22 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.6.2-1734 | Re: Re: $long_name in Moptions |
| Fergus Lynch wrote: | Hi,
Is there a way of having $long_name in 'Moptions'?
We use ELOG (amongst other things!) to allocate work out to Developers (who are all configured as ELOG users) I would like to use 'checkbox' functionality to allocate out a task to more than one developer. Currently only a single developer is chosen from a drop down list. |
This was not possible until now, so I implemented the option
Type <attribute> = muserlist
which gives you checkboxes (= multi-userlist) for all users instead of a drop down list. This feature is implemented starting from revision 1758 and it will be contained in the next release of elog. |
|
2086
|
Tue Nov 21 09:44:30 2006 |
| Fergus Lynch | flynch@alternativenetworks.com | Question | Windows | 2.6.2-1734 | Re: Re: $long_name in Moptions |
| Stefan Ritt wrote: |
| Fergus Lynch wrote: | Hi,
Is there a way of having $long_name in 'Moptions'?
We use ELOG (amongst other things!) to allocate work out to Developers (who are all configured as ELOG users) I would like to use 'checkbox' functionality to allocate out a task to more than one developer. Currently only a single developer is chosen from a drop down list. |
This was not possible until now, so I implemented the option
Type <attribute> = muserlist
which gives you checkboxes (= multi-userlist) for all users instead of a drop down list. This feature is implemented starting from revision 1758 and it will be contained in the next release of elog. |
WowThat was quick, I'll implement this morning. Many thanks for introducing this, ELOG is such a good tool.
Many Thanks
Fergus |
|
2087
|
Tue Nov 21 11:14:48 2006 |
| Fergus Lynch | flynch@alternativenetworks.com | Question | Windows | 2.6.2-1734 | Re: Re: $long_name in Moptions |
| Stefan Ritt wrote: |
| Fergus Lynch wrote: | Hi,
Is there a way of having $long_name in 'Moptions'?
We use ELOG (amongst other things!) to allocate work out to Developers (who are all configured as ELOG users) I would like to use 'checkbox' functionality to allocate out a task to more than one developer. Currently only a single developer is chosen from a drop down list. |
This was not possible until now, so I implemented the option
Type <attribute> = muserlist
which gives you checkboxes (= multi-userlist) for all users instead of a drop down list. This feature is implemented starting from revision 1758 and it will be contained in the next release of elog. |
Hi Stefan, apologies if I am being a bit dense (!) When I download the latest windows binary it extracts to ELOG V2.6.2-1749. Where could I get revision 1758 >
Thanks in advance
Fergus |
|
66069
|
Fri Nov 21 18:21:36 2008 |
 | Dennis Seitz | dseitz@berkeley.edu | Question | All | latest | Re: Re: $entry time not readable by Subst, else not datetime type? - possible Preset bug? |
| Dennis Seitz wrote: |
| Stefan Ritt wrote: |
| Dennis Seitz wrote: | | Do you mean '$entry time', or did you create a new parameter? (I don't see $entry date in the elogd.cfg reference) |
Yes, of course I mean '$entry time', sorry for the misspelling. |
Well, we really appreciate the way you keep adding features and making improvements. I thought you might have slipped a new one in! |
FYI, I think there's a little bug in the datetime vs $date implementation.
Here's a section of my config file implementing a "Last Edit" field:
Type Last Edit = datetime
Preset Last Edit =$date
Locked Attributes = Last Edit
Subst on edit Last Edit = $date
Start page = ?rsort=Last Edit
I expected that "Preset Last Edit =$date" would set Last Edit to the current date when I create a new entry. In fact that leaves the field empty, or at least not in datetime format.
I found that using this instead works:
Preset Last Edit =$entry time
which seems contradictory since
Subst on edit Last Edit = $date
works fine. |
|
|
ELOG V3.1.5-3fb85fa6 |