fckeditor is not running, posted by Heinzmann on Wed Nov 4 01:49:30 2009
|
Hello Stephan,
the fckeditor is not running.
I have installed elog 2.7.7 rev. 2246 on windows xp.
I have not changed the default config after the installation:
Theme = default
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
I have started the elog server manually to see if the editor will start, below you will find the output:
elogd 2.7.7 built Jul 31 2009, 13:01:20 revision 2246
Indexing logbooks ... done
Server listening on port 8080 ...
How can I activate the editor?
Thanks,
Michael
|
Re: fckeditor is not running, posted by Heinzmann on Wed Nov 4 23:53:58 2009
|
Heinzmann wrote: |
Hello Stephan,
the fckeditor is not running.
I have installed elog 2.7.7 rev. 2246 on windows xp.
I have not changed the default config after the installation:
Theme = default
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
I have started the elog server manually to see if the editor will start, below you will find the output:
elogd 2.7.7 built Jul 31 2009, 13:01:20 revision 2246
Indexing logbooks ... done
Server listening on port 8080 ...
How can I activate the editor?
Thanks,
|
I have found the problem:
the fckeditor folder contains not all necessary files after installation of Elog version 2.7.7.
I have downloaded the fckeditior manually from:
http://www.fckeditor.net/.
and replaced the faulty one with the new one.
Now the editor is running fine and I see the menu bar when I choose Encoding HTML:
elogd 2.7.7 built Jul 31 2009, 13:01:20 revision 2246
FCKedit detected
Indexing logbooks ... done
Server listening on port 8080 ...
Stefan could you please ckeck if some files are missing in the fckeditor folder within the elog version 2.7.7 rev. 2246.
Thanks
|
Re: fckeditor is not running, posted by Stefan Ritt on Fri Nov 13 15:40:05 2009
|
Heinzmann wrote: |
I have found the problem:
the fckeditor folder contains not all necessary files after installation of Elog version 2.7.7.
I have downloaded the fckeditior manually from:
http://www.fckeditor.net/.
and replaced the faulty one with the new one.
Now the editor is running fine and I see the menu bar when I choose Encoding HTML:
elogd 2.7.7 built Jul 31 2009, 13:01:20 revision 2246
FCKedit detected
Indexing logbooks ... done
Server listening on port 8080 ...
Stefan could you please ckeck if some files are missing in the fckeditor folder within the elog version 2.7.7 rev. 2246.
|
Yepp, the editor source code is completely missing in rev. 2.7.7. Thanks for pointing that out. I will include it in 2.7.8 which I will release pretty soon. |
Paper clip showing attachment not always present, posted by David Pilgram on Wed Nov 11 19:53:57 2009
|
Hi Stefan,
I must have seen this before, but only just "noticed" it.
If you attach a picture or pdf to the first entry in a tread, there is then a paperclip after the thread display
line. This shows up in threaded view or collapsed threaded view.
If you then attach a picture or pdf to a subsequent entry, the paperclip icon does not show up in threaded
display, (it is still there on the initial entry) but if the attachment is to the latest entry it shows up in
treaded collapsed display (collapse on last=1, of course). If collapse on last=0, then initial entry shows on
threaded, collapsed, and that has the icon as expected.
When the icon does show, you can click on it and get the correct attachment to show/launch reader or whatever.
It would appear to be a bug that the attachment icon does not appear in the threaded display (for any entry
other than the initial one).
(sorry about the first posting, hit the wrong key sequence in error)
Regards,
David Pilgram. |
Re: Paper clip showing attachment not always present, posted by David Pilgram on Fri Nov 13 10:57:03 2009
|
I may have made this sound as if the issue occurs if the first entry in a thread has an attachment; in fact it
happens whether or not there is an attachment to the first entry.
Hope this makes matters a bit clearer.
> Hi Stefan,
>
> I must have seen this before, but only just "noticed" it.
>
> If you attach a picture or pdf to the first entry in a tread, there is then a paperclip after the thread display
> line. This shows up in threaded view or collapsed threaded view.
>
> If you then attach a picture or pdf to a subsequent entry, the paperclip icon does not show up in threaded
> display, (it is still there on the initial entry) but if the attachment is to the latest entry it shows up in
> treaded collapsed display (collapse on last=1, of course). If collapse on last=0, then initial entry shows on
> threaded, collapsed, and that has the icon as expected.
>
> When the icon does show, you can click on it and get the correct attachment to show/launch reader or whatever.
>
> It would appear to be a bug that the attachment icon does not appear in the threaded display (for any entry
> other than the initial one).
>
> (sorry about the first posting, hit the wrong key sequence in error)
>
> Regards,
>
> David Pilgram. |
Re: Paper clip showing attachment not always present, posted by Stefan Ritt on Fri Nov 13 15:07:57 2009
|
> It would appear to be a bug that the attachment icon does not appear in the threaded display (for any entry
> other than the initial one).
Yes, that's indeed a bug. I fixed it in SVN revision 2266. |
Re: Paper clip showing attachment not always present, posted by David Pilgram on Fri Nov 13 15:10:34 2009
|
Thanks Stefan!
(But I'll wait and see if you do anything about Steve's point...so I'll download "after work"!).
> > It would appear to be a bug that the attachment icon does not appear in the threaded display (for any entry
> > other than the initial one).
>
> Yes, that's indeed a bug. I fixed it in SVN revision 2266. |
Dynamic attribute values, posted by Steve Williamson on Wed Oct 7 16:17:34 2009
|
Hi
I'm doing something wrong but can't work out what!
I've created a new logbook with some date attributes that need to keep in step, e.g. one date ("receipt date") is set to the date the new record is created and another ("response required") to 7 days later. The logbook doesn't use threaded messages, just a single page for each log entry with Submin/Preview/Back. The dates are set with:
Preset Receipt Date = $date
Preset Response Required = $shell(gawk 'BEGIN{ print $Receipt Date + 86400 * 7}')
"receipt date" and "response required" are set correctly when the log is written but if I change "receipt date" then "response required" is not altered - presumably because Preset only works on "New". Tho I haven't found a way to make this dynamic with Subst.
When the log is updated later a third date may be entered ("proposal submitted") and this should calculate a fourth date ("proposal expires"). Again, I thought I could do this with some sort of "Subst" but can't work out how. If I use Subst then the value of "proposal expires" isn't changed at all and if I use Subst On Edit then the value isn't changed until I go in to edit the log when the correct "proposal expires" date gets calculated and displayed, e.g.:
Subst On Edit Proposal Expires = $shell(gawk 'BEGIN{ if ($Proposal Sumbitted > 0) {print $Proposal Submitted + 86400 * 30}}')
Am I trying to do the impossible, and is there a document that will help me to understand when different updates (Preset, Subst, Subst On..., Change etc) happen and comparing their use?
A great piece of software - though I sometimes find it hard to get my head round all that it can be bent to do!
regards
Steve
|
Re: Dynamic attribute values, posted by Stefan Ritt on Tue Nov 10 15:00:15 2009
|
Steve Williamson wrote: |
Hi
I'm doing something wrong but can't work out what!
I've created a new logbook with some date attributes that need to keep in step, e.g. one date ("receipt date") is set to the date the new record is created and another ("response required") to 7 days later. The logbook doesn't use threaded messages, just a single page for each log entry with Submin/Preview/Back. The dates are set with:
Preset Receipt Date = $date
Preset Response Required = $shell(gawk 'BEGIN{ print $Receipt Date + 86400 * 7}')
"receipt date" and "response required" are set correctly when the log is written but if I change "receipt date" then "response required" is not altered - presumably because Preset only works on "New". Tho I haven't found a way to make this dynamic with Subst.
When the log is updated later a third date may be entered ("proposal submitted") and this should calculate a fourth date ("proposal expires"). Again, I thought I could do this with some sort of "Subst" but can't work out how. If I use Subst then the value of "proposal expires" isn't changed at all and if I use Subst On Edit then the value isn't changed until I go in to edit the log when the correct "proposal expires" date gets calculated and displayed, e.g.:
Subst On Edit Proposal Expires = $shell(gawk 'BEGIN{ if ($Proposal Sumbitted > 0) {print $Proposal Submitted + 86400 * 30}}')
Am I trying to do the impossible, and is there a document that will help me to understand when different updates (Preset, Subst, Subst On..., Change etc) happen and comparing their use?
|
Just try with the current version, where I reworked the "Subst" commands. See elog:66592. "Subst" work now only on "New", and "Subst on Edit" only works when editing an entry. |
Re: Dynamic attribute values, posted by Steve Williamson on Fri Nov 13 14:28:25 2009
|
Stefan Ritt wrote: |
Steve Williamson wrote: |
Hi
I'm doing something wrong but can't work out what!
I've created a new logbook with some date attributes that need to keep in step, e.g. one date ("receipt date") is set to the date the new record is created and another ("response required") to 7 days later. The logbook doesn't use threaded messages, just a single page for each log entry with Submin/Preview/Back. The dates are set with:
Preset Receipt Date = $date
Preset Response Required = $shell(gawk 'BEGIN{ print $Receipt Date + 86400 * 7}')
"receipt date" and "response required" are set correctly when the log is written but if I change "receipt date" then "response required" is not altered - presumably because Preset only works on "New". Tho I haven't found a way to make this dynamic with Subst.
When the log is updated later a third date may be entered ("proposal submitted") and this should calculate a fourth date ("proposal expires"). Again, I thought I could do this with some sort of "Subst" but can't work out how. If I use Subst then the value of "proposal expires" isn't changed at all and if I use Subst On Edit then the value isn't changed until I go in to edit the log when the correct "proposal expires" date gets calculated and displayed, e.g.:
Subst On Edit Proposal Expires = $shell(gawk 'BEGIN{ if ($Proposal Sumbitted > 0) {print $Proposal Submitted + 86400 * 30}}')
Am I trying to do the impossible, and is there a document that will help me to understand when different updates (Preset, Subst, Subst On..., Change etc) happen and comparing their use?
|
Just try with the current version, where I reworked the "Subst" commands. See elog:66592. "Subst" work now only on "New", and "Subst on Edit" only works when editing an entry.
|
Thanks for that - it works perfectly. Another success for elog! |
Automatically generated incrementing tags (#), posted by soren poulsen on Wed Oct 14 16:31:46 2009
|
Hi,
I am using the # character to generate automatically incrementing numbers for new messages.
My issue is that # is evaluated when you hit "New" but E-log is only aware of the new value being used when you hit "Submit".
So, two E-logs can have the same value substituted for # if two E-logs are being edited in parallel.
Maybe someone has a solution to this ?
Soren Poulsen
|
Re: Automatically generated incrementing tags (#), posted by soren poulsen on Wed Oct 14 16:46:57 2009
|
soren poulsen wrote: |
Hi,
I am using the # character to generate automatically incrementing numbers for new messages.
My issue is that # is evaluated when you hit "New" but E-log is only aware of the new value being used when you hit "Submit".
So, two E-logs can have the same value substituted for # if two E-logs are being edited in parallel.
Maybe someone has a solution to this ?
Soren Poulsen
|
The solution is to use "Subst" instead of "Preset". |
Re: Automatically generated incrementing tags (#), posted by soren poulsen on Mon Oct 26 15:43:55 2009
|
soren poulsen wrote: |
soren poulsen wrote: |
Hi,
I am using the # character to generate automatically incrementing numbers for new messages.
My issue is that # is evaluated when you hit "New" but E-log is only aware of the new value being used when you hit "Submit".
So, two E-logs can have the same value substituted for # if two E-logs are being edited in parallel.
Maybe someone has a solution to this ?
Soren Poulsen
|
The solution is to use "Subst" instead of "Preset".
|
This is not really resolved, since "Subst" creates a new number on both "New" and "Reply". I would like "Subst" to create a new number only on "New" and preserve this number through replies throughout the thread. I would like to be able to say "Subst thread = #" to make a new number for the thread and combine it with "Subst on reply thread = $thread" to preserve the number on replies, but this does not work. Maybe someone has already done this ?
Soren |
Re: Automatically generated incrementing tags (#), posted by soren poulsen on Sun Nov 8 23:29:35 2009
|
soren poulsen wrote: |
soren poulsen wrote: |
soren poulsen wrote: |
Hi,
I am using the # character to generate automatically incrementing numbers for new messages.
My issue is that # is evaluated when you hit "New" but E-log is only aware of the new value being used when you hit "Submit".
So, two E-logs can have the same value substituted for # if two E-logs are being edited in parallel.
Maybe someone has a solution to this ?
Soren Poulsen
|
The solution is to use "Subst" instead of "Preset".
|
This is not really resolved, since "Subst" creates a new number on both "New" and "Reply". I would like "Subst" to create a new number only on "New" and preserve this number through replies throughout the thread. I would like to be able to say "Subst thread = #" to make a new number for the thread and combine it with "Subst on reply thread = $thread" to preserve the number on replies, but this does not work. Maybe someone has already done this ?
Soren
|
This can be solved with something like "Subst <attr> = $shell(cmd...) where cmd calculates a new value of attr, as a function of #, when attr does not already have a value. This thread is closed.
Soren
|
Re: Automatically generated incrementing tags (#), posted by Stefan Ritt on Tue Nov 10 14:42:11 2009
|
soren poulsen wrote: |
soren poulsen wrote: |
soren poulsen wrote: |
Hi,
I am using the # character to generate automatically incrementing numbers for new messages.
My issue is that # is evaluated when you hit "New" but E-log is only aware of the new value being used when you hit "Submit".
So, two E-logs can have the same value substituted for # if two E-logs are being edited in parallel.
Maybe someone has a solution to this ?
Soren Poulsen
|
The solution is to use "Subst" instead of "Preset".
|
This is not really resolved, since "Subst" creates a new number on both "New" and "Reply". I would like "Subst" to create a new number only on "New" and preserve this number through replies throughout the thread. I would like to be able to say "Subst thread = #" to make a new number for the thread and combine it with "Subst on reply thread = $thread" to preserve the number on replies, but this does not work. Maybe someone has already done this ?
Soren
|
I just reworked the "Subst" command to make it more consistently. Now "Subst on Edit" and "Subst on Reply" are executed after the entry submission, and they are mutually exclusive. So all you need right now is
Subst Tag = #
and it will not increment when editing or replying to an existing entry. The fix is in SVN revision 2264. |
Re: Automatically generated incrementing tags (#), posted by soren poulsen on Tue Nov 10 21:36:21 2009
|
Stefan Ritt wrote: |
soren poulsen wrote: |
soren poulsen wrote: |
soren poulsen wrote: |
Hi,
I am using the # character to generate automatically incrementing numbers for new messages.
My issue is that # is evaluated when you hit "New" but E-log is only aware of the new value being used when you hit "Submit".
So, two E-logs can have the same value substituted for # if two E-logs are being edited in parallel.
Maybe someone has a solution to this ?
Soren Poulsen
|
The solution is to use "Subst" instead of "Preset".
|
This is not really resolved, since "Subst" creates a new number on both "New" and "Reply". I would like "Subst" to create a new number only on "New" and preserve this number through replies throughout the thread. I would like to be able to say "Subst thread = #" to make a new number for the thread and combine it with "Subst on reply thread = $thread" to preserve the number on replies, but this does not work. Maybe someone has already done this ?
Soren
|
I just reworked the "Subst" command to make it more consistently. Now "Subst on Edit" and "Subst on Reply" are executed after the entry submission, and they are mutually exclusive. So all you need right now is
Subst Tag = #
and it will not increment when editing or replying to an existing entry. The fix is in SVN revision 2264.
|
Thanks a lot for doing this change. |
Reply on item not allowed moving item to other logbook, posted by Eddy Berends on Mon Nov 9 11:50:05 2009
|
After I moved an item from one logbook to another one I cannot reply on this item anymore.
When the submit button is clicked it returns: Submit not allowed
This eLog server running Linux is sync'd with an server running Windows XP.
On the windows server the funcionality is working perfect(so no Submit is not allowed on a reply) |
Re: Reply on item not allowed moving item to other logbook, posted by Stefan Ritt on Tue Nov 10 14:24:26 2009
|
Eddy Berends wrote: |
After I moved an item from one logbook to another one I cannot reply on this item anymore.
When the submit button is clicked it returns: Submit not allowed
This eLog server running Linux is sync'd with an server running Windows XP.
On the windows server the funcionality is working perfect(so no Submit is not allowed on a reply)
|
Check your configuration file for the destination logbook, probably you have only restricted rights there ("Guest menu", "Login user" ???) |
Export Text to a csv File, posted by Michael Dannmeyer on Tue Nov 10 12:50:48 2009
|
Hello,
is it possible to export the Text Field and the entries in this field to a csv file? If yes, what are the settings to do this?
Regards
Michael
|
Re: Export Text to a csv File, posted by Stefan Ritt on Tue Nov 10 12:54:47 2009
|
Michael Dannmeyer wrote: |
Hello,
is it possible to export the Text Field and the entries in this field to a csv file? If yes, what are the settings to do this?
Regards
Michael
|
A CSV file is by definition one line per entry. So if you have several lines in your Text Field, how will you be able to squeeze this into one line?
Alternatively you can export to XML, which contains the Text Field, then do a manual conversion to something else. |
Re: Export Text to a csv File, posted by Michael Dannmeyer on Tue Nov 10 13:06:26 2009
|
Stefan Ritt wrote: |
Michael Dannmeyer wrote: |
Hello,
is it possible to export the Text Field and the entries in this field to a csv file? If yes, what are the settings to do this?
Regards
Michael
|
A CSV file is by definition one line per entry. So if you have several lines in your Text Field, how will you be able to squeeze this into one line?
Alternatively you can export to XML, which contains the Text Field, then do a manual conversion to something else.
|
Thanks for your fast answer. |
width of the Text column in the summary list view, posted by Fabio Rossi on Fri Nov 6 12:49:22 2009
|
I have "Summary lines = 1" in the config file. The first line visualized in the summary list, in the Text column, is truncated. I'm using the default style.
Which is the way to set the number of character displayed? |
Re: width of the Text column in the summary list view, posted by Stefan Ritt on Fri Nov 6 13:46:38 2009
|
Fabio Rossi wrote: |
I have "Summary lines = 1" in the config file. The first line visualized in the summary list, in the Text column, is truncated. I'm using the default style.
Which is the way to set the number of character displayed?
|
I added a new parameter
Summary line length = x
for you. This is included in SVN revision 2262 (if you can compile it yourself) and will be contained in the next release. |
Re: width of the Text column in the summary list view, posted by Fabio Rossi on Fri Nov 6 18:08:20 2009
|
Stefan Ritt wrote: |
Fabio Rossi wrote: |
I have "Summary lines = 1" in the config file. The first line visualized in the summary list, in the Text column, is truncated. I'm using the default style.
Which is the way to set the number of character displayed?
|
I added a new parameter
Summary line length = x
for you. This is included in SVN revision 2262 (if you can compile it yourself) and will be contained in the next release.
|
I have already tested your patch backporting the change to 2.7.7.1. It works like a charm.
Thank you very much! |
Access control, group level, posted by Niklas on Mon Nov 2 11:17:20 2009
|
Hi elog experts =)
Anyone know if it's possible to have access control per group-level?
For instance:
Group A = B,C
Group B = LogA
Group C = LogB, LogC
Group C: Read password = abc
?
//NH |
Re: Access control, group level, posted by Stefan Ritt on Tue Nov 3 09:24:15 2009
|
Niklas wrote: |
Hi elog experts =)
Anyone know if it's possible to have access control per group-level?
For instance:
Group A = B,C
Group B = LogA
Group C = LogB, LogC
Group C: Read password = abc
//NH
|
I added your vote to the wishlist
https://midas.psi.ch/elog/wishlist.html |