If an attribute uses MOptions and is also extendable, clicking "Add 
<attribute name>" and entering a value adds the value to the MOptions, but 
does not put the value into the log entry. The log record has that 
attribute blank.
You have to go back into the record and edit it to put the new value in.

> If an attribute uses MOptions and is also extendable, clicking "Add 
> <attribute name>" and entering a value adds the value to the MOptions, but 
> does not put the value into the log entry. The log record has that 
> attribute blank.
> You have to go back into the record and edit it to put the new value in.

I fixed that bug just now, thanks for reporting it. It's available in revision
1.535 under CVS.

Have tried to use "Menu commands =" to list menu commands available as per:
"Menu commands = List, Back, New, Edit, Delete, Find, Config, HELP, Logout"

but it does not seem to work; with command above I get default menu 
structure.

Using:
"Find Menu commands = List, Back, New, Edit, Find, Delete, Config, Logout, 
HELP"

I get the menu I want.
Q what's the difference?????

> Have tried to use "Menu commands =" to list menu commands available as per:
> "Menu commands = List, Back, New, Edit, Delete, Find, Config, HELP, Logout"
> 
> but it does not seem to work; with command above I get default menu 
> structure.
> 
> Using:
> "Find Menu commands = List, Back, New, Edit, Find, Delete, Config, Logout, 
> HELP"
> 
> I get the menu I want.
> Q what's the difference?????

"Find menu commands" apply to the LIST of entries, while "Menu commands" apply
to the page where a SINGLE entry is shown. I know that "Find menu commands" is
a misleading name, but it's historical, I should change it to "Menu commands"
and change the other to "Entry menu commands", does that make more sense?

I can export the Attributes I define easily and the Subject. Can't seem to 
export the Entry Date and the Text fields.

Help.

> I can export the Attributes I define easily and the Subject. Can't seem to 
> export the Entry Date and the Text fields.

The XML export contains both the Entry Date and Text fields. In CSV format,
it's hard to export the Text field since it can span several lines, which would
break the CSV format (one line per entry). Or do you know how multi-line
entries can be encoded in CSV?

> I can export the Attributes I define easily and the Subject. Can't seem to 
> export the Entry Date and the Text fields.

I added at least the date and message ID to the CSV export. New version under CVS.

Hi,

right now I'm testing Elog to use it as a task/todo-log for our small 
workgroup. What I saw so far looks very nice and I like it very much. 
Thanks for the good work.

Playing with all the configuration possibilities I have one issue:
I like to use the "Extendable options" but I can't combine them with 
the "Conditional attributes".

-- snip

Options Area = Area_1{1}, Area_2{2}, Area_51{3}
{1} Options Ressort = Res01, Res whatever, end so on
{2} Options Ressort = somthing else, fill in
{3} Options Ressort = Alien observation, Budget planning
Extendable options = Ressort

-- snip

The "Conditinal Attributes" do have the "Add Ressort" button and the elog-
entry is written with this new attribute. But the new attribute is not 
inserted into the config file.

Long time ago I last read C syntax but mabye the function 
add_attribute_option should take care of the prefix {n} in extendable 
options?

Or do I miss something in the configuration syntax? 

  Regards,

  David

> Playing with all the configuration possibilities I have one issue:
> I like to use the "Extendable options" but I can't combine them with 
> the "Conditional attributes".

That was never ment to work. But I found some time to implement it. If you
download elog255-4.exe from today it whould work. Let me know if you have
problems.

> > Playing with all the configuration possibilities I have one issue:
> > I like to use the "Extendable options" but I can't combine them with 
> > the "Conditional attributes".
> 
> That was never ment to work. But I found some time to implement it. If you
> download elog255-4.exe from today it whould work. Let me know if you have
> problems.

Thanks a lot for fixing this issue, especially as it was never planed. I will
test it on Monday afternoon and will give you a reply.

> > > Playing with all the configuration possibilities I have one issue:
> > > I like to use the "Extendable options" but I can't combine them with 
> > > the "Conditional attributes".
> > 
> > That was never ment to work. But I found some time to implement it. If you
> > download elog255-4.exe from today it whould work. Let me know if you have
> > problems.
> 
Hello Stefan,

the changes I asked for, are working as requested. The extandable options are 
inserted into the correct line of the conditional attributes. 

  Thanks.

PS: While testing on a new demo logbook, I first made the mistake to declare 
both options, the first one and the related one as extendable. But I can imagine 
that this was really never ment to be implemented.

I implemented experimentally RSS feeds into Elog. Before releasing this new
addition, I would like to collect some experience with it. This forum now
supports RSS feeds, for which you can subscribe with a RSS feed reader like
Mozilla Firefox. Please give it a try and send me any feedback.

For an introduction to RSS feeds, please see 

http://www.webreference.com/authoring/languages/xml/rss/intro/

To subscribe to a logbook, enter following URL into your RSS reader:

http://<your-elog-host.domain>/<logbook>/elog.rdf

From the newest Mozilla Firefox browser, you can also click on the RSS box at
the lower right corner of the browser (see attachment).

Great, but what's the corresponding URL for the RSS feed itself

> I implemented experimentally RSS feeds into Elog. Before releasing this new
> addition, I would like to collect some experience with it. This forum now
> supports RSS feeds, for which you can subscribe with a RSS feed reader like
> Mozilla Firefox. Please give it a try and send me any feedback.
> 
> For an introduction to RSS feeds, please see 
> 
> http://www.webreference.com/authoring/languages/xml/rss/intro/

I didn't see the RSS button in Firefox, however the URL:

 	http://midas.psi.ch/elogs/Forum/elog.rdf
works fine in with Bloglines (http://www.bloglines.com/myblogs

I've installed the lastest elog (v2.5.5)--how do I turn it on for a particular
logbook?

Thanks,
Steve

> I implemented experimentally RSS feeds into Elog. Before releasing this new
> addition, I would like to collect some experience with it. This forum now
> supports RSS feeds, for which you can subscribe with a RSS feed reader like
> Mozilla Firefox. Please give it a try and send me any feedback.
> 
> For an introduction to RSS feeds, please see 
> 
> http://www.webreference.com/authoring/languages/xml/rss/intro/
> 
> To subscribe to a logbook, enter following URL into your RSS reader:
> 
> http://<your-elog-host.domain>/<logbook>/elog.rdf
> 
> From the newest Mozilla Firefox browser, you can also click on the RSS box at
> the lower right corner of the browser (see attachment).

IE 6 chokes on the XML, below is what I get for 
http://midas.psi.ch/elogs/Forum/elog.rdf
(sorry this is in french).
So I assume all rss reader parsing the file with the MS XML parser shall also 
have a problem, this is the case with Avant Browser integrated RSS reader.

Cheer,
Marc

------------------------------------------------------

La page XML ne peut pas être affichée 
Impossible d'afficher l'entrée XML en utilisant la feuille de style XSL. 
Corrigez l'erreur, puis cliquez sur le bouton Actualiser ou réessayez 
ultérieurement. 


--------------------------------------------------------------------------------

Un caractère incorrect a été trouvé dans un contenu de texte. Erreur de 
traitement de la ressource http://midas.psi.ch/elog...

<title>Re: $message id  gives wrong value - Gernman traslalation of Back, posted 
by Ulrich Tr

The <pubDate> item doesn't appear to be a valid RFC-822 date.  Causes some
aggregators to fail when parsing.

The error is shown by Feedvalidator:
http://www.feedvalidator.org/check.cgi?url=http%3A%2F%2Fmidas.psi.ch%2Felogs%2FForum%2Felog.rdf

> I implemented experimentally RSS feeds into Elog. Before releasing this new
> addition, I would like to collect some experience with it. This forum now
> supports RSS feeds, for which you can subscribe with a RSS feed reader like
> Mozilla Firefox. Please give it a try and send me any feedback.
> 
> For an introduction to RSS feeds, please see 
> 
> http://www.webreference.com/authoring/languages/xml/rss/intro/
> 
> To subscribe to a logbook, enter following URL into your RSS reader:
> 
> http://<your-elog-host.domain>/<logbook>/elog.rdf
> 
> From the newest Mozilla Firefox browser, you can also click on the RSS box at
> the lower right corner of the browser (see attachment).

> The <pubDate> item doesn't appear to be a valid RFC-822 date.  Causes some
> aggregators to fail when parsing.

I fixed that, now it passes the Feedvalidator. New version is under CVS.

Thanks to Recai Oktas, who encourage me to complete the Bulgarian
translation for the Debian elog package, the Bulgarian translation is
completed and attached.

Thanks, the file will be contained in the next release.

Could you implemet and option 'admin menu' which gets displayed
when an 'admin' is logged in.  This menu could e.g. also include 'Delete'
while the normal menu would not.

> Could you implemet and option 'admin menu' which gets displayed
> when an 'admin' is logged in.  This menu could e.g. also include 'Delete'
> while the normal menu would not.

You can achieve the same via

Allow delete = <admin name>

I have a computer that has a different idea of its name from the DNS 
server. When I run ELOG and someone clicks "Search" I get a page not found.
I tried starting with "-n <hostname>", but elog still uses gethostname.
The example is that DNS says my machine is "abc.company.com" and netstat -
a says elog is listening on 8080 abc.personaldomain.com

Here is the code from elogd.c:

   /* get host name for mail notification */
   gethostname(host_name, sizeof(host_name));
   phe = gethostbyname(host_name);
   if (phe != NULL)
      phe = gethostbyaddr(phe->h_addr, sizeof(int), AF_INET);
   /* if domain name is not in host name, hope to get it from phe */
   if (strchr(host_name, '.') == NULL && phe != NULL)
      strcpy(host_name, phe->h_name);

I think you should be using tcp_hostname instead of gethostname if it is 
specified.

> I think you should be using tcp_hostname instead of gethostname if it is 
> specified.

Sorry my late reply, I was ill for some time. I implemented your suggestion in
revision 1.522 which is available from CVS.

Note that there is also the "URL = xxx" option in the configuration file which
lets you specify the whole URL including the host name.

know that illness...  :-(  but was the last of the family of 4 people

i'd like to ask for an other usefull change togehter with this and how url's are 
handled by elog:

since there may be spaces in the name of a logbook (ex. "1stWordOfLogbook 
2ndWordOfLogbook") it is very userfriendly to name logbooks. also it's easy th 
make a reference for a other entry by copy and paste:

Display ThisURL = http://localhost:8080/$logbook/$message id

however, using spaces in the logbook name may give a wrong result, because the 
url would be http://localhost:8080/1stWordOfLogbook

and the space as well as the 2ndWordOfLogbook//$message id is only normal text.

may it be possible stefan, to replace the space in an url (starting 
with "http://") with a "+" or "%20"? this would allow to automate some things. 
actual the logbook name has to be hardcoded.


> > I think you should be using tcp_hostname instead of gethostname if it is 
> > specified.
> 
> Sorry my late reply, I was ill for some time. I implemented your suggestion in
> revision 1.522 which is available from CVS.
> 
> Note that there is also the "URL = xxx" option in the configuration file which
> lets you specify the whole URL including the host name.

Ok, I changed that in version 2.5.5-3. Note that one can also use the "elog:..."
substitution, like

Display ThisURL = elog:$logbook/$message id