| Time |
Nick |
Message |
| 00:09 |
|
dat_ joined #evergreen |
| 06:02 |
|
nhilton joined #evergreen |
| 06:17 |
|
eeevil joined #evergreen |
| 07:15 |
|
artunit joined #evergreen |
| 07:47 |
|
eeevil joined #evergreen |
| 07:48 |
|
mtate joined #evergreen |
| 07:57 |
|
Callender joined #evergreen |
| 07:58 |
|
akilsdonk joined #evergreen |
| 08:06 |
|
rjackson-isl joined #evergreen |
| 08:22 |
|
Ghid0rah joined #evergreen |
| 08:24 |
Ghid0rah |
Good morning all. Does anyone know if there is a way to test Evergreen's email notification configuration in Evergreen 2.7.2? |
| 08:29 |
|
mrpeters joined #evergreen |
| 08:37 |
|
mmorgan joined #evergreen |
| 08:47 |
|
graced joined #evergreen |
| 08:52 |
|
Shae joined #evergreen |
| 08:59 |
|
phasefx joined #evergreen |
| 09:20 |
Stompro |
@later tell Ghid0rah There are several ways to debug action/triggers. You can take a look at the tables under action_trigger.* to see what is being processed. You can take a look at /openils/var/log/osrfsys.log while running action_trigger_runner.pl to see exactly what is happening. You can also add the --verbose argument to action_trigger_runner.pl to see more details of what it is doing. |
| 09:20 |
pinesol_green |
Stompro: The operation succeeded. |
| 09:22 |
tsbere |
He could probably place a copy hold for himself with email notification turned on, then check the copy in, then wait to see if he got an email too. :P |
| 09:23 |
tsbere |
(though depending on what the state of configuration is that may not provide a lot of info as to what is wrong if it doesn't show up) |
| 09:29 |
|
TaraC joined #evergreen |
| 09:35 |
|
maryj joined #evergreen |
| 09:37 |
|
BigRig joined #evergreen |
| 09:37 |
|
abowling joined #evergreen |
| 09:38 |
|
yboston joined #evergreen |
| 10:12 |
|
aubjordan joined #evergreen |
| 10:20 |
|
Dyrcona joined #evergreen |
| 10:50 |
kmlussier |
When a change is made to one of the templates in action_trigger.event_definition, do any other changes (roll bricks, etc) need to be made in order for the new event_definition code to take effect? |
| 10:50 |
kmlussier |
The change in question is to the PO JEDI template. |
| 10:52 |
tsbere |
kmlussier: I don't believe anything else has to be done. Though obviously already-fired events won't use the new template. |
| 10:52 |
kmlussier |
Yup. This would have been a new event. |
| 10:53 |
kmlussier |
Thanks tsbere! |
| 11:13 |
|
vlewis joined #evergreen |
| 11:27 |
|
mllewellyn joined #evergreen |
| 11:30 |
|
nhilton joined #evergreen |
| 11:44 |
kmlussier |
berick++ |
| 12:02 |
|
nhilton joined #evergreen |
| 12:28 |
|
kitteh_ joined #evergreen |
| 12:35 |
|
RoganH joined #evergreen |
| 12:54 |
|
RoganH joined #evergreen |
| 13:07 |
|
jihpringle joined #evergreen |
| 13:18 |
|
buzzy joined #evergreen |
| 13:57 |
|
akilsdonk joined #evergreen |
| 14:16 |
|
chatley joined #evergreen |
| 15:17 |
|
RoganH joined #evergreen |
| 16:08 |
|
bmills joined #evergreen |
| 17:13 |
|
bshum joined #evergreen |
| 17:13 |
|
mceraso joined #evergreen |
| 17:13 |
|
mrpeters left #evergreen |
| 17:13 |
|
kmlussier joined #evergreen |
| 17:20 |
aubjordan |
When creating a report that is pulling info on transited items is it possible to not have it pull info on items that have completed its transit? |
| 17:21 |
aubjordan |
I hope that makes sense |
| 17:22 |
eeevil |
aubjordan: yes, just filter for dest_recv_time (I don't recall the label) is NULL |
| 17:23 |
eeevil |
that will get you transits that have not yet arrived |
| 17:26 |
aubjordan |
I keep forgetting about NULL |
| 17:29 |
|
mmorgan left #evergreen |
| 17:29 |
aubjordan |
What I am seeing is different though. |
| 17:30 |
aubjordan |
I ran a report looking a for all transits over a given time frame. What I am trying to filter out is those that are no long in transit or at another library. |
| 17:31 |
aubjordan |
Im thinking it may be two separate reports. |
| 18:35 |
|
buzzy joined #evergreen |
| 18:36 |
csharp |
aubjordan: run the report on the unfiltered data, then use Excel to get fancy |
| 19:22 |
|
conlinism joined #evergreen |
| 19:23 |
conlinism |
hello |
| 19:23 |
csharp |
conlinism: hi |
| 19:24 |
conlinism |
hows it going? |
| 19:26 |
conlinism |
If I were looking to get involved in contributing to the web front end of Evergreen, how would I do that? |
| 19:35 |
csharp |
~contribute |
| 19:35 |
pinesol_green |
Interested in contributing to the Evergreen project? Please see http://www.evergreen-ils.org/dokuwiki/doku.php?id=contributing and http://evergreen-ils.org/dokuwiki/doku.php?id=eg_developer_overview. |
| 19:35 |
csharp |
conlinism: basically, read this^^, then install evergreen on a test server and start hacking! |
| 19:39 |
conlinism |
thanks! |
| 20:22 |
|
rangi joined #evergreen |
| 20:36 |
|
nhilton joined #evergreen |
| 20:40 |
|
burper joined #evergreen |
| 20:40 |
|
burper left #evergreen |
| 21:20 |
|
burper joined #evergreen |
| 21:20 |
|
burper left #evergreen |
| 22:15 |
|
bmills joined #evergreen |
