ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 341 of 807

Not logged in

Find | Login | Help

New entries since:

Thu Jan 1 01:00:00 1970

Full | Summary | Threaded | Hide attachments

6454 Entries

Goto page Previous 1, 2, 3 ... 340, 341, 342 ... 805, 806, 807 Next

Tue Jun 9 13:22:25 2015

Re: RSS Feed Not Providing Time Stamps For datetime Attributes

I fixed the problem in the current GIT version.

/Stefan

Kamen Nikolov wrote:

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

Kamen Nikolov wrote:

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 the RSS Title with $Start Time and $Stop Time, but when looking at the RSS title in IE11 browser, I only see the date and not the time. Is there any way I can see the time as well?

Additional info:

I'm also passing the creation time of the Elog with $entry time and this is displaying correctly (both date and time).

Please let me know if I am doing something incorrectly?

Thanks

67976

Tue Jun 9 15:44:49 2015

Re: parse a correctly the username in save_user_config when using Webserver authentication

Hi Christof,

thanks for the patch, I merged it into the current HEAD.

/Stefan

Christof Hanke wrote:

Hi Stefan,

When we use Webserver authentication, we have the correct username already in the variable http_user.

The old way of copying this http_user to "user" is wrong since we don't use the size of http_user.

Instead, just encode the http_user variable directly.

See attached patch against git HEAD.

Christof

67977

Tue Jun 9 16:09:39 2015

Re: logout to external page

I implemented it, but actually called it Logout to URL = <URL>

Christof Hanke wrote:

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.
However, I would also need some means of logging out some where else.

For this I propose a new Configuration option "Logout to page" which redirects to another page if set and "Logout to main" is 0.

See the attached patch (against git HEAD)

Does this make sense to you ?

Christof

PS: Many thanks for the autosave mode, I already used it ;-)

67979

Tue Jun 9 16:46:48 2015

Re: subject line bug on resumit elog entries as new?

Any better now?

David Pilgram wrote:

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 than "A new..."

67981

Tue Jun 9 16:57:06 2015

Re: Documentation of the webserver authentication

Also this made it now to the docs. Thanks.

Christof Hanke wrote:

Hi Stefan,

here is a draft of how you could describe the webserver authentication in your docs.

T/Christof

67983

Tue Jun 9 17:09:22 2015

ELOG Forum: drafts cannot be deleted

> Another strange thing: the draft got submitted when I hit the "Back" button after reopening it.

Well, this is a problem indeed. When edit entries now, drafts gets saved regularly, overwriting your original entry. This is a limitation of the elog database, which cannot do full versioning. So "Back" is actually the same as "Commit without email notification". Or better "Commit some ten seconds ago". Now I 
don't know what the best solution is. I'm tempted to just remove the "Back" button and replace it with a "Delete" button. So people can either submit an entry or delete it completely. Any thoughts?

67988

Tue Jun 9 19:35:28 2015

Re: Problem with a draft message

Just read what I wrote at elog:67983

David Pilgram wrote:

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.

David Pilgram wrote:

Just to comment that I submitted the entry below by pressing the "Back" button!

David Pilgram wrote:

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. I immediately went in and deleted it, but I had expected the "Back" button to have aborted the entry (as it does in 2.9.x) not to submit the entry!

It doesn't seem to have created an email, though. And for the sake of all your users, I'd not want to experiment here on the matter too much!

67991

Wed Jun 10 08:13:50 2015

Re: subject line bug on resumit elog entries as new?

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 make install.

If you want to see which changes are already in the version you are running, look at the 7 digit GIT hash at the bottom of each elog page and compare it with the bitbucket repository:

Jacky Li wrote:

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.

Jack

Goto page Previous 1, 2, 3 ... 340, 341, 342 ... 805, 806, 807 Next

ELOG V3.1.5-3fb85fa6