> But I want a duplicate entry of the entry.... so that I can reuse the text and other
> items and just change the entrys that need to be changed.
> 
> E.g, you have a work request from one user with some kind of solution on it, then you
> get a similar request from another user and you want to have almost the same
> information in a new entry. Then you just want to create a copy of the old case and
> change whatever needs to be changed.
> 
> I'm not sure if you understand what I tries to do?

Now I understand. What you ask for is not possible right now, but I put it on the
wishlist. The best would be to add a new command "Duplicate" to the menu, which lets you
do exactly what you want.

> > But I want a duplicate entry of the entry.... so that I can reuse the text and other
> > items and just change the entrys that need to be changed.
> > 
> > E.g, you have a work request from one user with some kind of solution on it, then you
> > get a similar request from another user and you want to have almost the same
> > information in a new entry. Then you just want to create a copy of the old case and
> > change whatever needs to be changed.
> > 
> > I'm not sure if you understand what I tries to do?
> 
> Now I understand. What you ask for is not possible right now, but I put it on the
> wishlist. The best would be to add a new command "Duplicate" to the menu, which lets you
> do exactly what you want.

Thank you!

Or what I understand with "Resubmit as new entry", keep the old and create a new entry.
Perhaps you can trigger behavior of resubmit with a switch?
Duplicate Resubmit = 1
(default to 0 - old behavior)

or your idea is good as well.

Or just update the Entrytime if you are using Copy To:
EntryUpdate Copy To = 1

with also solves my case.

(and switch for Move To as well?)


Have a nice evening,

Best regards
Michael

> or your idea is good as well.

Ok, I implemented a 'Duplicate' command (see this forum for example). I guess this is clearer
than modifying some of the existing functionality like 'resubmit' or 'copy to'. With 'copy to'
you probably want to keep all information from the original entry, including the submission
time, when you move it from one logbook into an other. So if we put an 'EntryUpdate Copy To',
this would not be possible any more. The new version is under CVS.

- Stefan

> > or your idea is good as well.
> 
> Ok, I implemented a 'Duplicate' command (see this forum for example). I guess this is clearer
> than modifying some of the existing functionality like 'resubmit' or 'copy to'. With 'copy to'
> you probably want to keep all information from the original entry, including the submission
> time, when you move it from one logbook into an other. So if we put an 'EntryUpdate Copy To',
> this would not be possible any more. The new version is under CVS.


Wow! You are really fast!

I'm going to try it now!

This works for me :)


Thanks for quick response Stefan!


Best regards
Michael

Hi Andreas, I opted for the first solution since the Debian package, although outdated and broken, has some goodies like a systemd unit for managing the daemon which is very handy. I downloaded FCKeditor 2.6.11 from SourceForge (after a long search, seems that CKeditor made its parent almost disappear from the web), unpacked it in the proper folder and not the WYSIWYG editor works. I have just a couple of minor issues: there is no attachment drop area (I had it in my old Debian 6 server) and the editor toolbar has an ugly "Windows 95" look; see the attached image. I can live with these problems but if the can be easily fixed then obviously I would do that, can you give me any hint? Thank you very much.

Elog 3.x comes with CKeditor, not FCKeditor any more! I would actually recommend to use the CKeditor from the current Elog 3.1.1 source package if running together with Elog 3.1.1.