subject line bug on resumit elog entries as new?, posted by Jacky Li on Fri May 29 22:32:20 2015
|
Hi,
I updated an old elog entry and resubmit it as new by checking the box resubmit as new. Does the subject line should said it is a "New
ELOG entry" instead of "Updated ELOG entry"? Thank you. |
Re: subject line bug on resumit elog entries as new?, posted by Stefan Ritt on Tue Jun 9 12:51:07 2015
|
I fixed both issues, now resubmitting an entry or submitting a new entry both yields "New LEOG entry".
Jacky
Li wrote:
Hi, |
|
Re: subject line bug on resumit elog entries as new?, posted by David Pilgram on Tue Jun 9 16:17:06 2015
|
Hi Stefan,
I see that you've updated the elog running this forum today, 5 versions after you reported fixing the "A new elog entry has been entered"
and "An old elog entry has been updated" issue. But the emails coming out are still all of the "An old elog entry...", rather |
|
Re: subject line bug on resumit elog entries as new?, posted by Stefan Ritt on Tue Jun 9 16:46:48 2015
|
Any better now?
David
Pilgram wrote:
Hi Stefan, |
|
Re: subject line bug on resumit elog entries as new?, posted by David Pilgram on Tue Jun 9 16:51:55 2015
|
Hi Stefan,
The email sent from here had he expected (correct) message "A new ELOG entry..."
Thanks, David. |
|
Re: subject line bug on resumit elog entries as new?, posted by Jacky Li on Tue Jun 9 22:31:59 2015
|
Hi,
I compiled the 3.1.0-2 source rpm from the download area. Unless there is a minor release, I think the problem is still there. Thank
you. |
Re: subject line bug on resumit elog entries as new?, posted by Stefan Ritt on Wed Jun 10 08:13:50 2015 
|
Making a new release takes me about an hour (compile under Windows, Linux, Mac OSX), so I don't do it for each little change. If you want to follow
the development closely, I recommend that you learn to compile elog from the GIT repository. It's pretty easy: a git
pull, followed by a make and |
Problem with a draft message, posted by David Pilgram on Tue Jun 9 17:17:11 2015
|
Hi Stefan,
I had started to write a completely different bug report, but then realised I had not checked a detail. I had written about one sentence.
So I decided to abort the message, and hit the "back" button. Only I found that this had created a new entry in the elog listings. |
|
Re: Problem with a draft message, posted by David Pilgram on Tue Jun 9 17:21:25 2015
|
Just to comment that I submitted the entry below by pressing the "Back" button!
David
Pilgram wrote:
Hi Stefan, |
|
Re: Problem with a draft message, posted by David Pilgram on Tue Jun 9 17:23:27 2015
|
Just to comment that the expected emails that one would have expected with the last two entries have either
been held up or simply have not been generated and sent - both the preceeding entries were submitted by using the "Back" button, this
time I'll use the "Submit" button, which should generate a email. |
|
Re: Problem with a draft message, posted by Stefan Ritt on Tue Jun 9 19:35:28 2015
|
Just read what I wrote at elog:67983
David
Pilgram wrote:
Just to comment that the expected emails that one would have expected |
|
Re: Problem with a draft message, posted by David Pilgram on Tue Jun 9 20:26:00 2015
|
I missed or don't remember that post. My vote is replace "Back" with "Delete" - or "Abort"
Stefan
Ritt wrote:
Just read what I wrote at elog:67983 |
logout to external page, posted by Christof Hanke on Wed May 6 11:00:14 2015
|
Hi Stefan,
I am happy to see that you include the webserver authentication.
So I can now login at some other page and then access elog. |
|
Re: logout to external page, posted by Stefan Ritt on Tue Jun 9 16:09:39 2015
|
I implemented it, but actually called it Logout to URL = <URL>
Christof
Hanke wrote:
Hi Stefan, |
|
Re: logout to external page, posted by Christof Hanke on Tue Jun 9 16:58:28 2015
|
Yes, I saw it on bitbucket, also all the commits. Thanks!
Stefan
Ritt wrote:
I implemented it, but actually called it |
Documentation of the webserver authentication, posted by Christof Hanke on Wed May 6 12:31:04 2015
|
Hi Stefan,
here is a draft of how you could describe the webserver authentication in your docs.
T/Christof |
|
Re: Documentation of the webserver authentication, posted by Stefan Ritt on Tue Jun 9 16:57:06 2015
|
Also this made it now to the docs. Thanks.
Christof
Hanke wrote:
Hi Stefan, |
parse a correctly the username in save_user_config when using Webserver authentication, posted by Christof Hanke on Wed May 6 15:13:11 2015
|
Hi Stefan,
When we use Webserver authentication, we have the correct username already in the variable http_user. |
|
Re: parse a correctly the username in save_user_config when using Webserver authentication, posted by Stefan Ritt on Tue Jun 9 15:44:49 2015
|
Hi Christof,
thanks for the patch, I merged it into the current HEAD.
/Stefan |
|
Attribute not updated, posted by Francois Cloutier on Wed May 13 14:58:46 2015
|
Good day,
I'm populating 2 fields based on the Option set in a third one.
|
|
Re: Attribute not updated, posted by Francois Cloutier on Wed May 13 15:19:55 2015
|
I also tried with :
{1, 53} Preset #Parution = 1
{2, 54} Preset #Parution = 2
|
|
Re: Attribute not updated, posted by Andreas Luedeke on Thu May 14 02:02:45 2015
|
Hi Francois,
as far as I know there is a limit on the number of conditions you can use (See elog:67303).
I guess you did hit that limit.
|
|
Re: Attribute not updated, posted by Francois Cloutier on Thu May 14 02:27:58 2015
|
> Hi Francois,
> as far as I know there is a limit on the number of conditions you can use (See elog:67303).
> I guess you did hit that limit.
|
Re: Attribute not updated, posted by Andreas Luedeke on Thu May 14 04:59:03 2015
|
> Seriously, I really hope It could make it... Could you try it on your side ?
|
|
Re: Attribute not updated, posted by Francois Cloutier on Thu May 14 05:08:06 2015
|
>
> > Seriously, I really hope It could make it... Could you try it on your side ?
>
|
|
Re: Attribute not updated, posted by Midas User on Tue Jun 9 15:28:53 2015
|
> I saw in the doc that an attribute cant be bigger than 100 char. but I couldn't figure the maximum size for options... I'm wondering if the issue comes
from the browser not refreshing correctly or if its elog..
|
|
edit somebody else's draft, posted by Konstantin Olchanski on Wed May 20 01:54:55 2015
|
this elog offers me to edit a draft message, then yells at me "only some other user can edit this draft!!!".
methinks I should only be offered to edit draft messages that I own or I can edit. K.O. |
|
Re: edit somebody else's draft, posted by David Pilgram on Wed May 20 22:12:49 2015
|
> this elog offers me to edit a draft message, then yells at me "only some other user can edit this draft!!!".
> methinks I should only be offered to edit draft messages that I own or I can edit. K.O.
I find it odd that I can see someone elses draft, but never one that I am in the middle of composing (using a
|
|
Re: edit somebody else's draft, posted by Stefan Ritt on Fri May 22 13:50:31 2015
|
> > this elog offers me to edit a draft message, then yells at me "only some other user can edit this draft!!!".
> > methinks I should only be offered to edit draft messages that I own or I can edit. K.O.
> I find it odd that I can see someone elses draft, but never one that I am in the middle of composing (using a
|
|
Re: edit somebody else's draft, posted by Midas User on Tue Jun 9 15:22:03 2015
|
> this elog offers me to edit a draft message, then yells at me "only some other user can edit this draft!!!".
> methinks I should only be offered to edit draft messages that I own or I can edit. K.O.
|
|
RSS Feed Not Providing Time Stamps For datetime Attributes, posted by Kamen Nikolov on Fri May 8 00:18:12 2015
|
Hello,
I am using the RSS feed feature of Elog (V2.9.0-2396). I have a couple of attributes of type "datetime" (Start Time and Stop
Time). I don't have a "Time Format" statement, so just using the default format. I am passing the Start Time and Stop Time attributes to |
|
Re: RSS Feed Not Providing Time Stamps For datetime Attributes, posted by Kamen Nikolov on Tue May 26 22:03:05 2015
|
Can anyone help? Do I need to do something different or could this possibly be a bug that is fixed in a newer version?
Thanks,
Kamen |
|
Re: RSS Feed Not Providing Time Stamps For datetime Attributes, posted by Andreas Luedeke on Wed May 27 10:50:41 2015
|
Hi Kamen,
I've just tried it for V3.1.0 (6ab0fd5) and the described behaviour is unchanged.
It is even worse if you
don't specify the "RSS Title": datetime attributes are just displayed as seconds of the epoch then.
I think this is a feature
of ELOG at the moment.
You'll either need to dig into the code yourself or wait for Stefan to fix it.
I |
|
Re: RSS Feed Not Providing Time Stamps For datetime Attributes, posted by Stefan Ritt on Tue Jun 9 13:22:25 2015
|
I fixed the problem in the current GIT version.
/Stefan
Kamen |