ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 267 of 807

Not logged in

Find | Login | Help

Full | Summary | Threaded | Show attachments

6451 Entries

Goto page Previous 1, 2, 3 ... 266, 267, 268 ... 805, 806, 807 Next

Tue Nov 10 15:00:15 2009

Re: Dynamic attribute values

Steve Williamson wrote:

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.

66595

Tue Nov 10 21:36:21 2009

soren poulsen

soren.poulsen@cern.ch

Question

Linux

2.7.7

Re: Automatically generated incrementing tags (#)

Stefan Ritt 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.

66600

Fri Nov 13 14:28:25 2009

Steve Williamson

StephenWilliamson@Barnsley.gov.uk

Question

Linux

2.7.5

Re: Dynamic attribute values

Stefan Ritt wrote:

Steve Williamson wrote:

I'm doing something wrong but can't work out what!

Preset Receipt Date = $date

Preset Response Required = $shell(gawk 'BEGIN{ print $Receipt Date + 86400 * 7}')

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!

66609

Fri Nov 13 15:40:05 2009

Re: fckeditor is not running

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.

66611

Fri Nov 13 17:03:03 2009

Re: Show dropdown menus as a function of selecting an option in another dropdown menu

Diogo Alves wrote:

Hello,

I'm having some difficulties in having a tasks manager up and running.

The total attributes list is:

- Attributes = List, Project, SubProject, SubSubProject, Title, Priority, Context, Status, Due Date, Start Date, Alarm, Repeat

I would like to have the interface display the following attribute when I click "New":

- List (Options = Personal, Work)

After choosing a List "Personal" I would like to have the following attributes available for edit:

- List (Options = Personal, Work)

- Project (Options = Dummy1)

- Title

- Priority (Options = ...)

- Context (Options = ...)

- Status (Options = ...)

- Due Date (datetime)

- Start Date (datetime)

- Alarm (datetime)

- Repeat (Options = ...)

After choosing the Project "Dummy1" I would like to have the following attributes available for edit:

- List (Options = Personal, Work)

- Project (Options = Dummy1)

- SubProject (Options = Dummy2)

- Title

- Priority (Options = ...)

- Context (Options = ...)

- Status (Options = ...)

- Due Date (datetime)

- Start Date (datetime)

- Alarm (datetime)

- Repeat (Options = ...)

where Dummy2 is an option of the SubProject attribute only because Dummy1 was the chosen option of attribute Project.

What happens is that when I choose Dummy1 from the Project attribute, the SubProject attribute is not displayed in order to be editable.

Is there a way around this?

Thank you.

Kind Regards,

Diogo

Here's the configuration file relative to the "Tasks" logbook:

================================================

Password file = passwords.pwd
Self register = 0
Admin user = someuser
Login user = someuser
Allow password change = 1
Theme = default
Comment = Task Manager

Attributes = List, Project, SubProject, Title, Priority, Context, Status, Due Date, Start Date, Alarm, Repeat
List display = ID, Date, Author, List, Title, Priority
Show Attributes Edit = List

Options List = Personal{1}, Work{2}
Options Priority = High, Medium, Low, None
Options Context = @ Home, @ Work - IST
Options Status = Not Started, Start Delayed, Started, Started - On Hold, 1/4 Done, 1/4 Done - On Hold, 1/2 Done, 1/2 Done - On Hold, 3/4 Done, 3/4 Done - On Hold, Done
Options Repeat = Hourly, Daily, Weekdays, Weekend days, Weekly, Monthly, Yearly

{1} Show Attributes Edit = List, Project, Title, Priority, Context, Status, Due Date, Start Date, Alarm, Repeat
{1} Options Project = Dummy1{11}
{11} Show Attributes Edit = List, Project, SubProject, Title, Priority, Context, Status, Due Date, Start Date, Alarm, Repeat
{11} Options SubProject = DummyChild1

Extendable options = List, Project, SubProject, SubSubProject
Type Due Date = datetime
Type Start Date = datetime
Type Alarm = datetime
Required Attributes = List, Title
Reverse sort = 1
Default encoding = 0 ; ELcode
Thumbnail size = 500

There is one "feature" which causes this not to work. If an option is present several times (in your case "Show Attributes Edit"), the first one is taken which fulfills the current condition(s). So what happens is you select List=Personal, which triggers condition "1". Then you select "Dummy1", which triggers condition "11". Now elog goes top down, finds that List=Personal, so sets condition "1", then continues, finds {1} Show Attributes Edit = ... and takes this one. What I propose is to do the following:

Options List = Personal{1}, Work{2}
...
{3} Show Attributes Edit = List, Project, SubProject, Title, Priority, Context, Status, Due Date, Start Date, Alarm, Repeat
{3} Options SubProject = DummyChild1
{1} Show Attributes Edit = List, Project, Title, Priority, Context, Status, Due Date, Start Date, Alarm, Repeat
{1} Options Project = Dummy1{3}

Note that {3} Show Attributed Edit come before {1} Show Attributes Edit, so as soon as you select "Dummy1", the first "Show Attributes Edit" gets 
activated which contains "SubProject".

66613

Mon Nov 16 23:04:25 2009

Subscribe to logbooks: Linux Demo, Database, etc.. regarding enable automatic email notifications

Hello Stefan,

how can I activate the part like: Subscribe to logbooks: Linux Demo, Database, etc.. regarding enable automatic email notifications

like below

Discussion forum about ELOG

Logged in as "Heinzmann"

Login name:
Full name:
Email:
Subscribe to logbooks: (enable automatic email notifications)	Linux Demo Database Forum Config Examples Contributions Vulnerabilities