ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
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: |
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! |
66617
|
Tue Nov 17 12:29:24 2009 |
| Steve Williamson | StephenWilliamson@Barnsley.gov.uk | Request | Linux | 2.7.7-2264 | Re: Re: List View: Attachments icon |
Thanks for all of the contributions - all I meant in my original suggestion was that I'd like to be able to define which column(s) should hold the Attachments paperclip in the Full and Summary List Views, which I use all the time, to reduce the need to scroll horizontally on every page. This would be similar to being able to specify where the Edit control appears by specifying the Edit attribute in the "List Display" list.
... and I really didn't want to ruin another of Stefan's weekends or confuse anybody! |
65993
|
Sun Oct 12 20:40:32 2008 |
| Steve Nahn | nahn@mit.edu | Question | Linux | 2.7.4-2111 | Maximum number of mail recipients |
Just wondering if there is still a maximum number of mail recipients? I saw a number of 112 floating around in old forum entries, and I need more, like currently 300. When I try it, the elogd hangs, not much output to speak of, but won't reply to Apache on its port. Any quick fix (like changing a def'd variable somewhere?) |
67146
|
Wed Nov 9 20:15:38 2011 |
| Steve Nahn | nahn@mit.edu | Bug report | Linux | 2.9.0 | Global Synchronization with 2.9.0 |
Hi
I just updated my mirror server, which I just use as a backup to my main server, to 2.9.0 and found that after logging in (the selection page is not protected, but the individual logbooks are) and coming back to the selection page I no longer get the "Synchronize all logbooks" even though I am an admin user. The relevant code is in elogd.c in the show_selection_page() routine:
/* only admin user sees synchronization link */
if (is_admin_user("global", getparam("unm"))) {
rsprintf("<tr>\n");
rsprintf("<td colspan=13 class=\"seltitle\">\n");
rsprintf("<a href=\"?cmd=Synchronize\">%s</a></td>\n", loc("Synchronize all logbooks"));
rsprintf("</tr>\n");
}
what is happening is that after logging in to a logbook and coming back to the selection page, the "unm" parameter is not set, so getparam("unm") returns NULL, who clearly is not in the admin user list. The strange thing is that in an individual logbook the unm (and uname) parameters are working fine, and I have admin rights - can change the global config file, do an individual synchronization, etc. It is just from the selection page that the unm parameter is not working.
In fact, I commented out the if statement above, just to see if I could get synchronized using the link, and that failed too, with a message "No user name supplied for remote access" even though I do have a "mirror user" statement in my config. Again, if I do each one individually it all works. In addition, the cron synchronization (i.e. mirror cron) also works fine.
Obviously this isn't crucial, just a pain that can be worked around, but if anyone has any ideas I'd be glad to hear them.
Steve
PS Another feature request: when you forget to set an icon in this forum and then use the "back button" it shouldn't force you to rewrite the whole message over again! |
599
|
Wed Jul 14 21:35:32 2004 |
| Steve Jones | steve.jones@freescale.com | Question | All | 2.5.3 | Question on how "Format <attribute> = " works |
It is not clear to me how "Format <attribute> = " works. At first I thought
it would allow me to rearrange how attributes are organized on the html
"page" using
# <flags> Sum of following flags:
* 1: Display attribute in same line as previous attribute
* 2: Display radio buttons or check boxes in separate lines (if applicable)
but this does not result in any behavior that I can see. I must admit that
I am not sure what "Values used for single message display page:" means.
My goal is to provide a more compact page, taking small attributes and
running them across the page rather than straight down.
Thanks |
600
|
Wed Jul 14 21:47:47 2004 |
| Steve Jones | steve.jones@freescale.com | Request | All | 2.5.3 | Wishlist: TOOLTIP for ATTRIBUTES |
Using the COMMENT feature to add guidance to an ATTRIBUTE works great, but
is it possible to add a TOOLTIP <ATTRIBUTE> = so as to save screen space?
For a complex entry form it is desireable to try and have everything in a
single window and this, I think, would help.
Thanks |
603
|
Wed Jul 14 22:52:18 2004 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.5.3 | Possible Formatting bug: Summary view |
I've run into a situation where the SUMMARY view of a logbook will extend
beyond the righthand border, thus requiring the user to scroll right. This
does not occur in FULL or THREAD mode. Long lines in the TEXT attribute
appear to be "pushing" the display too far to the right. Limiting the
number of displayed summary lines works unless the first line is too long.
A temporary fix for this is to set summary lines = 0 |
604
|
Wed Jul 14 22:54:43 2004 |
| Steve Jones | steve.jones@freescale.com | Request | All | 2.5.3 | Re: Wishlist: TOOLTIP for ATTRIBUTES |
> > Using the COMMENT feature to add guidance to an ATTRIBUTE works great, but
> > is it possible to add a TOOLTIP <ATTRIBUTE> = so as to save screen space?
>
> Where should the tooltip appear? In the entry form or when an entry is
> displayed, or even in the tabular listing? I can put a title arround the
> attribut names such as
>
> <div title="Please enter some subject here">Subject:</div>
>
> which gets interpreted by most browsers as a tooltip. However it's not
> apparent to the user that leaving the cursor on top of "Subject" opens a
> tooltip, especially since the cursor is displayed as the text cursor (vertical
> bar), not as an arrow over the attribute. Do you have a link to a public web
> page which uses tooltips?
>
> > For a complex entry form it is desireable to try and have everything in a
> > single window and this, I think, would help.
>
> Aiming for running elog on you PDA? Let me know if you succeed...
In the Entry form I am thinking, as this is when most people need some help.
Perhaps the user could be clued in with a "Mouse-over each attribute for Help"
COMMENT at the top.
As for the PDA, no, it's just that some people around here get confused if they
have to scroll down. Not a big thing . . . ;-> Hmmm, PDA . . . |