Gmail uses a type of SMTP authentication which is currently not supported by elog. It's however on the todo list.

Stefan

Hi Stefan,

Thank you very much for your reply. So which SMTP type can I use now? Is outlook OK?

Kevin

This is a local issue  on your network, if you have a mail server setup. SMTP is not handled directly by Elog and neither is any other mail protocal. Elog just sends the requested email to your server for processing to the recipients afaict. And whatever server (or service) you use to handle email sending needs to be able to accept them from your mail server. So after verifying which ones  you want to use; (like OutLook, or gmail, or whatever), then have your local email server set up to work with them. You can prol have a 3rd party do this was well (instead of your own local one) but then they would STILL need to be able to work with whatever guidlines the actual sender (gmail, hotmail..) requires to have mail sent. Email is a lonnng trail of different providers, servers, and other actors..

Halvy

Under linux, only the "root" user can start programs on ports below 1024. If you get problems binding to ports above 1024 (such as 8080) it means that some other program uses already that port. You can check what is running usually with

netstat -l -p

> Hi Stefan,
> 
> I don't know if anyone else would be interested or need this...
> 
> If you have an Roption, and it is not required (maybe...) or have a preset attribute, it is possible to make an
> entry and have replies without any of the attributes in that Roption being selected.
> 
> However, once an attribute in that Roption has been selected, it is not possible to go back (editing) to the
> condition before one was selected on that entry (so far as I can tell).  
> 
> Is a way of cancelling all the possible attributes in an Roption practical?  Would others want it?  It is
> possible with options, as there is a "please select" which can be used to cancel whichever attribute in the
> option that has been selected.
> 
> Regards,  David

The easiest to achieve this is to define another option. Assume you have the three options

One, Two, Three

and you want to "unselect" them. So just add a fourth option like

Unspecified, One, Two, Three

so if you do not want any of the "One, Two, Three", just click on "Unspecified" and you get what you want.

> > Hi Stefan,
> > 
> > I don't know if anyone else would be interested or need this...
> > 
> > If you have an Roption, and it is not required (maybe...) or have a preset attribute, it is possible to make an
> > entry and have replies without any of the attributes in that Roption being selected.
> > 
> > However, once an attribute in that Roption has been selected, it is not possible to go back (editing) to the
> > condition before one was selected on that entry (so far as I can tell).  
> > 
> > Is a way of cancelling all the possible attributes in an Roption practical?  Would others want it?  It is
> > possible with options, as there is a "please select" which can be used to cancel whichever attribute in the
> > option that has been selected.
> > 
> > Regards,  David
> 
> The easiest to achieve this is to define another option. Assume you have the three options
> 
> One, Two, Three
> 
> and you want to "unselect" them. So just add a fourth option like
> 
> Unspecified, One, Two, Three
> 
> so if you do not want any of the "One, Two, Three", just click on "Unspecified" and you get what you want.

This is sort of what I do now, I just wondered if there was a way of clearing that would leave the field completely
blank in the YYMMDDa.log file.

Thanks.

The problem is that the elog database does not allow for a copy of an entry before you make modifications (and therefore get a "draft"). This is actually very simila to other note taking programs. I use Evernote, which constantly synchronizes between devices, and there I also cannot go back to the version before I started making modification. What one would need is a version system (and Evernote has one), so you can go back to the previous verison, the pre-previous version and so on. But this requires a complete redesign of the elog database.

A quick and dirty solution would be to store the origianal entry inside the browser (using JavaScript). You could then restore the initial version with a "cancel" button. But this mechanism relies then on the browser. If you just leave the page, there is no way the browser can put back the old version.

Stefan

Andreas,

Doesn't using the Save Drafts = 0 option result in the old 'Back' button returning (replacing the Delete option) meaning you can revert back to your old (unmodified) version without saving, sure it doesn't save a draft but I'd rather be able to return back and lose the changes I didn't want then mess up an old entry, I guess the back button on the browser could also do what you want?

The issue I had was that entries were being deleted accidently by persons other than those that created them, I reduced the edit time to try and mitigate it but ended up going back to what we had in Ver 2.9.2, a 'Back' button.

Grant