• ELOG allows you to have different commands for different users. You could allow "New" and "Edit" for normal users, but "Reply" only for administrators.
• You can use "Subst on reply <attribute> = <string>" to set a specifc fields only on reply. 
  • You would hide "status" & "assignee" for new entries or edit (Show Attributes Edit = <list>), and show a "set status" field instead.
  • The line "Subst on reply status = $set status" would take care, that only an administrator can set "status" with a reply to the original entry (+ a "set assignee" field, etc.). While normal users could set "set status", it would not change the "status" field. You could provide a comment or tooltip to explain that.
  • The list view or single entry view should not show the "set status", but only the "status" attribute (List display = <list>, Show Attributes = <list>).
• Use "Propagate attribute = status, assignee" to take care, that the original entry gets their fields set accordingly.

This is how you could do what you want. But bugzilla can do a lot more if you are looking for a bug tracking software.

Cheers, Andreas

Hi Eddy,

Thank you for your response.  I had a feeling that was the case, but I had high hopes! :)  The reason I would like this feature is because I am trying to use ELOG as a software anomaly tracking log, where any user can create an ELOG and fill out "category", "computer" etc, but only administrators can fill out the "status" & "assignee".  If I am lucky, this will be an added feature in a future revision.

Thanks again,

-Terry

Right, spaces won't work. But others work. Andreas, if you just put elog:1 without any link etc. just as plain text, it will be converted automatically into a link.

A workaround is to explicitly specify a link to an elog entry. Press the link button from the editor toolbar, enter a name and copy the full URL from the browser address bar, like here: https://midas.psi.ch/elogs/Forum/68129. If you switch to "Source" (Top left editor toolbar, you can changed the link name manually, like here.

You are right. "Edit" should be more like "Replace". I changed that in the documentation.

I acknowledge the request to replace or append only a specific attribute or attachment, and put it on my to-do list.

Stefan

[-e <id>]                Edit existing message

The "elog" command has no "append" feature. You can either create a new entry, or you can overwrite an old entry. Therefore this is not a bug but the intended bahaviour.

I admit that the documentation is misleading, since overwriting an existing entry is called "editing":

[-e <id>]                Edit existing message

I interprete your posts that you would like to have two new features for the "elog" command:

• to append text to the body of an existing entry
• to add additional attachments to an existing entry

Without a specific application in mind I would like to add a request (for consistency):

• to modify a specific attribute of an existing entry.

Cheers, Andreas

I can confirm this bug.

Yes it was a path issue PHP was not loading correctly environmental path

> > <p>Hi,</p>
> > 
> > <p>I have a problem running elog command from php script. Basically in the php I call system(&quot;elog -h etc etc.. And from the php command line works but not in the browser apparently without errors (php apache 
> logfile no problem), any suggestions?</p>
> 
> Hey,
> this sounds more like a PHP issue.
> Which PHP version are you using? 
> Which webserver? 
> Which php function are you using: shell_exec() or exec()? Try looking at the return of exec()
> Is the elog file set to the correct file permissions to be executed by the webserver?
> Is the elog file in the PHP path or do you take care of defining the correct path?
> 
> 
> eddy