| Time |
Nick |
Message |
| 00:20 |
|
sandbergja joined #evergreen |
| 02:15 |
|
dbwells joined #evergreen |
| 03:26 |
|
laurie joined #evergreen |
| 04:17 |
|
dbwells joined #evergreen |
| 06:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 06:54 |
|
agoben joined #evergreen |
| 07:24 |
|
rjackson_isl_hom joined #evergreen |
| 07:26 |
|
collum joined #evergreen |
| 07:55 |
|
Dyrcona joined #evergreen |
| 08:13 |
|
mantis1 joined #evergreen |
| 08:18 |
|
agoben joined #evergreen |
| 08:18 |
|
dbwells joined #evergreen |
| 08:22 |
|
agoben joined #evergreen |
| 08:24 |
|
dbwells joined #evergreen |
| 08:24 |
|
genpaku joined #evergreen |
| 08:36 |
|
sandbergja joined #evergreen |
| 08:37 |
|
mmorgan joined #evergreen |
| 09:06 |
|
dbwells joined #evergreen |
| 09:38 |
csharp |
any caveats about forcing HTTPS for the OPAC generally? |
| 09:39 |
csharp |
I remember a few years ago jeffdavis (?) had a ticket for forcing HTTPS everywhere and there were some concerns, but I haven't seen any trouble using the OPAC with HTTPS, so maybe those are all gone? |
| 10:01 |
Dyrcona |
csharp: Offline or something like that used to break in the XUL client, other than that go for it. |
| 10:01 |
Dyrcona |
But, the OPAC, never had a problem with HTTPS except for mixed content warnings that I believe we have resolved. |
| 10:02 |
Dyrcona |
csharp: You might also be interested to know that I'm switching our main test/development database to Pg 12 today. |
| 10:03 |
csharp |
yes, I am interested - please keep us informed! :-) |
| 10:04 |
csharp |
thanks for the response - that was my understanding too (that it was XUL related) |
| 10:16 |
|
jvwoolf joined #evergreen |
| 11:07 |
|
nfBurton joined #evergreen |
| 11:42 |
|
khuckins joined #evergreen |
| 12:08 |
|
jihpringle joined #evergreen |
| 12:27 |
|
mrisher joined #evergreen |
| 12:27 |
|
mrisher joined #evergreen |
| 12:37 |
|
jihpringle joined #evergreen |
| 13:45 |
|
nfBurton joined #evergreen |
| 13:46 |
|
nfBurton2 joined #evergreen |
| 14:29 |
|
collum_ joined #evergreen |
| 14:30 |
|
collum__ joined #evergreen |
| 14:31 |
|
collum__ joined #evergreen |
| 14:36 |
|
collum joined #evergreen |
| 14:36 |
|
collum joined #evergreen |
| 14:38 |
csharp |
does anyone have an explanation/docs/etc. about the use of "-1" in this context? https://git.evergreen-ils.org/?p=Evergreen.git;a=blob;f=Open-ILS/src/offline/offline.pl;h=ae972276f4fd679e0e7dd80ea8b8b1910990139f;hb=HEAD#l894 |
| 14:39 |
eby |
does anyone know if a 3.3.5 -> 3.4.1 sql script is going to be made? I see that the updates in 3.4.0->3.4.1 are done in the 3.3.4->3.3.5 but there are about 14 updates that need to be done to get 3.3.5->3.4.1 into the same state as the 3.3.3->3.4.0 and 3.4.0->3.4.1 gets you |
| 14:39 |
csharp |
referred to as "virtual ID" but I don't have confidence about what it means and I'd like to use it |
| 14:39 |
|
collum_ joined #evergreen |
| 14:43 |
Dyrcona |
eby: You can make one yourself. |
| 14:45 |
eby |
yep working on it. was just curious if there was already one to be committed |
| 14:45 |
Dyrcona |
Nope. We don't it that way. |
| 14:45 |
Dyrcona |
If Pastebin would cooperate, I'd paste the link to what I use to make our custom db upgrade scripts. |
| 14:46 |
csharp |
@blame Pastebin |
| 14:46 |
pinesol |
csharp: Your failure is now complete, Pastebin. |
| 14:46 |
Dyrcona |
eby: https://pastebin.com/KQGFPGGV |
| 14:46 |
Dyrcona |
I may have a more recent version... |
| 14:49 |
Dyrcona |
Nope. That looks like the same one that I still use. |
| 14:50 |
eby |
thanks Dyrcona |
| 14:51 |
Dyrcona |
yw. |
| 14:54 |
JBoyer |
csharp, those -1 virtual ids as I understand them will be replaced with the id of the newly created thing, and since $actor->id() is set to -1 a few lines above it's just shorthand for $sr->usr($actor->id()) |
| 14:54 |
|
collum joined #evergreen |
| 14:55 |
JBoyer |
In the item editor for instance I think you can have multiple negative ids, so all of the -1's are updated to X, -2 to Y, etc. as items are batch created. |
| 14:55 |
csharp |
nice - that's very helpful |
| 14:55 |
csharp |
JBoyer++ |
| 14:56 |
JBoyer |
The important thing is that there isn't an au entry with id=-1, depending on what you mean by "like to use it." :) |
| 14:56 |
csharp |
I'm hoping to use it in a similar way to the item editor example - not having to know the ID is helpful |
| 14:58 |
JBoyer |
Ah, ok. It can help to cement its usefulness and prevent any future confusion by skipping the kind of "I already know it's -1" shortcut used in that offline example then. |
| 15:42 |
|
mantis1 left #evergreen |
| 16:48 |
mmorgan |
So having some weirdness with logging into the client after an upgrade. Some users are not able to log in, they just get the menu bar at the top and nothing else. |
| 16:49 |
mmorgan |
Seems to be a Chrome profile issue. One Chrome profile on the same workstation works, and another one doesn't. Any ideas? |
| 16:49 |
jihpringle |
yes, we ran into this after our last upgrade too |
| 16:49 |
mmorgan |
We have a number of Chrome profiles that are seeing the problem. Possibly related, there were websocket connection issues at first. |
| 16:50 |
jihpringle |
our libraries found that resetting their Chrome settings fixed it in most cases |
| 16:50 |
jihpringle |
http://docs.libraries.coop/sitka/_troubleshooting.html#_reset_settings |
| 16:52 |
mmorgan |
jihpringle++ |
| 16:52 |
mmorgan |
jihpringle: Does that mess up extensions, passwords, workstations and the like? |
| 16:53 |
JBoyer |
mmorgan, on my way out, but it could also be caching-related weirdness. Right-clicking on the page and choosing Inspect will pop up the browser console, then you can right-click on the Refresh button to use the Empty Cache and Hard Reload option. It's not disruptive and it's helped out here with similar upgrade shenanigans. |
| 16:54 |
jihpringle |
mmorgan: I don't think so, but it was back in May |
| 16:54 |
jihpringle |
The info for Reset Settings says "This will reset your startup page, new tab page, search engine, and pinned tabs. It will also disable all extensions and clear temporary data like cookies. Your bookmarks, history and saved passwords will not be cleared." |
| 16:54 |
mmorgan |
JBoyer++ |
| 16:55 |
mmorgan |
Ok thanks, that gives us a couple of thing to try. |
| 16:55 |
jihpringle |
good luck, hope one of them fixes it for you :) |
| 17:21 |
mmorgan |
Chrome reset worked for one user, fingers crossed for the others! |
| 17:23 |
|
mmorgan left #evergreen |
| 17:59 |
|
abowling1 joined #evergreen |
| 18:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 18:05 |
|
abowling joined #evergreen |
| 18:16 |
|
jvwoolf joined #evergreen |
| 18:17 |
|
dbwells joined #evergreen |
| 18:30 |
|
mrisher_ joined #evergreen |
| 18:38 |
|
abowling joined #evergreen |
| 19:00 |
|
jvwoolf joined #evergreen |
| 23:23 |
|
khuckins joined #evergreen |
