Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 595 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Show attachments  Show only new entries    6460 Entries 
Goto page Previous  1, 2, 3 ... 594, 595, 596 ... 806, 807, 808   Next  
ID Date Icon Author Author Emaildown Category OS ELOG Version Subject
  65799   Tue Apr 1 02:04:35 2008 Idea Dennis Seitzdseitz@berkeley.eduRequestAll Duplicate entry suggestion

 We have configured several logbooks to allow users to duplicate an entry in another logbook, which is very useful for entries which apply to more than one category.

However, once the entry is duplicated, subsequent revisions to the original entry are not copied to the duplicate entries.

I can see where implementing that would add a lot of code to ELOG.  Rather than do that, would it be possible to add a configuration option to duplicate only the attributes, and place a link to the original entry in the body of the duplicated entry instead of the full text?

Thanks,

Dennis

  65802   Tue Apr 1 20:31:26 2008 Reply Dennis Seitzdseitz@berkeley.eduRequestAll Re: Duplicate entry suggestion

 

Stefan Ritt wrote:

 

Dennis Seitz wrote:

 We have configured several logbooks to allow users to duplicate an entry in another logbook, which is very useful for entries which apply to more than one category.

However, once the entry is duplicated, subsequent revisions to the original entry are not copied to the duplicate entries.

I can see where implementing that would add a lot of code to ELOG.  Rather than do that, would it be possible to add a configuration option to duplicate only the attributes, and place a link to the original entry in the body of the duplicated entry instead of the full text?

 

I don't know if you are aware, but you can put links to other entries manually into the text. Just enter them in the form elog:65799. You can click on that link which takes you the entry you reference. Unfortunately there is at the moment no automatic way to generate this back link automatically.

 

Thanks, I was not aware of that - usually I have copied and pasted the entire path from my browser.

In any case, can you consider my request for possible future implementation? I think it's a useful function. For now, it's really no big deal to simply copy the url before selecting the Copy To: menu and then replacing the body text with the copied link. But I think it would be more useful to make this happen automatically, so I don't have to ask users to comply voluntarily.

Thank you.

 

  65804   Tue Apr 1 21:24:17 2008 Idea Dennis Seitzdseitz@berkeley.eduRequestAll attachment indicator in summary view

 It would be nice to have the option of including an attachment indicator column in summary view to show if an entry has any attachments.

Thanks.

  65873   Wed May 7 17:10:07 2008 Question Dennis Seitzdseitz@berkeley.eduQuestionAlllatest$entry time not readable by Subst, else not datetime type?
I posted this on the end of an earlier thread but I thought it might be better to repost as a separate thread:


Thank you for pointing out the method to identify an attribute as a datetime type so that it will sort properly. I now have created my "Last Edit" attribute in several
preexisting logbooks.

I want to use
Start page = ?rsort=Last Edit
to set the default sorting of each logbook to be by Last Edit.

However, all of the entries made before I added Last Edit have no value for that field, so they are all grouped together at the end of the sort. So I
decided to go through the older entries and set Last Edit equal to the original entry date, as a starting value.

I tried to use the command
Subst on edit Last Edit = $entry time
but it gives a "-" for the Last Edit value when I edit an entry.

I think this is because $entry time is not a variable supported by Subst. Can you add that support, or else tell me if you know a better way to go about
doing what I'm attempting? Is there perhaps a way to globally process a group of entries in a logbook and set one attribute's value to be equal to
another's? To reiterate, I want to initialize Last Edit = $entrytime for all entries that have not been re-edited.

Thanks
  65888   Wed May 21 21:06:38 2008 Idea Dennis Seitzdseitz@berkeley.eduRequestAll Make Email All = <list> override Suppress Email checkbox

 I would like to be notified by email of some logbook entries regardless of whether the user has chosen to suppress email or not.

This way I will always be aware of new entries, and users will still have the option of notifying a larger group of other users, or not.

As far as I can tell, presently the Suppress Email checkbox overrides Email All.

  66040   Mon Nov 10 19:40:43 2008 Entry Dennis Seitzdseitz@berkeley.eduBug report 2.7.3-2109Show/Hide links are displayed but don't work if Show attachments = 0

If I add this statement to a logbook config file:

Show attachments = 0

When viewing and individual entry, attached images are not displayed, which is as intended, but the links Show/Hide and Show All/Hide All are still displayed although they do nothing when clicked except switch between Show and Hide. Clicking on an image opens it in a separate window.

Could you make show/hide and show/hide all work? This way, by default the images are not displayed, but the default could be overridden on a case by case basis as desired, and the images displayed inline in the same window with the entry. 

Thanks!

 

  66069   Fri Nov 21 18:21:36 2008 Question Dennis Seitzdseitz@berkeley.eduQuestionAlllatestRe: Re: $entry time not readable by Subst, else not datetime type? - possible Preset bug?

Dennis Seitz wrote:

Stefan Ritt wrote:

Dennis Seitz wrote:
Do you mean '$entry time', or did you create a new parameter? (I don't see $entry date in the elogd.cfg reference)


Yes, of course I mean '$entry time', sorry for the misspelling.


Well, we really appreciate the way you keep adding features and making improvements. I thought you might have slipped a new one in!



FYI, I think there's a little bug in the datetime vs $date implementation.

Here's a section of my config file implementing a "Last Edit" field:

Type Last Edit = datetime
Preset Last Edit =$date
Locked Attributes = Last Edit
Subst on edit Last Edit = $date
Start page = ?rsort=Last Edit

I expected that "Preset Last Edit =$date" would set Last Edit to the current date when I create a new entry. In fact that leaves the field empty, or at least not in datetime format.

I found that using this instead works:
Preset Last Edit =$entry time

which seems contradictory since
Subst on edit Last Edit = $date
works fine.
  66080   Tue Nov 25 17:01:55 2008 Reply Dennis Seitzdseitz@berkeley.eduQuestionAll2.7.3Re: Re: $entry time not readable by Subst, else not datetime type? - possible Preset bug?

Stefan Ritt wrote:

Dennis Seitz wrote:
FYI, I think there's a little bug in the datetime vs $date implementation.

Here's a section of my config file implementing a "Last Edit" field:

Type Last Edit = datetime
Preset Last Edit =$date
Locked Attributes = Last Edit
Subst on edit Last Edit = $date
Start page = ?rsort=Last Edit

I expected that "Preset Last Edit =$date" would set Last Edit to the current date when I create a new entry. In fact that leaves the field empty, or at least not in datetime format.

I found that using this instead works:
Preset Last Edit =$entry time

which seems contradictory since
Subst on edit Last Edit = $date
works fine.


Do you have an old version of elog? Using the current version with a configuration file:
Attributes = Author, Type, Last Edit
Type Last Edit = datetime
Preset Last Edit =$date
Locked Attributes = Last Edit
Start page = ?rsort=Last Edit

I get the correct behavior:



Yes, I'm using 2.7.3 - I'll try upgrading, sorry. I'll reply with the outcome.
Goto page Previous  1, 2, 3 ... 594, 595, 596 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6