Bill, I think this sounds fine, but would make two possible suggestions.
1) I think we should get some kind of release built before bug-squashing week,
to be usable for anyone wanting that sort of testing path during the following
week. That could easily happen late on the 7th, or we could
Not sure if I will order a shirt, but just a shout-out to whoever made the
conference logo this year. The overlay of the four branch logos is simple,
brilliant, and beautiful.
Sincerely,
Dan
From: Open-ils-general
Dear Evergreen Community,
I am writing to offer myself as release manager for the upcoming 3.0 release.
Our library is an independent academic installation, and having recently
celebrated 7 years on Evergreen, a fairly early adopter. I served as release
manager for 2.5 and 2.6, release cycles
Hello Janet,
It appears a late change to that feature did not get fully implemented. It
originally exported as MARC-XML, but was changed to export as MARC21 instead.
However, the dialog box still includes the ".xml" extension by default.
If you manually change the extension to something more
Hello Justin,
Those ‘file not found’ errors are normal, and should be harmless. For example,
the ‘nls’ lookups are for translation, and since the fallback files are already
English, there is no need to provide English translation files. They certainly
aren’t related to your 500 error.
That
LOST". A
check in the database for entries in money.account_adjustment only shows note
entries for "System: OVERDUE REVERSED FOR CLAIMS-RETURNED" right now.
-Brent
On 1/27/16 3:06 PM, Dan Wells wrote:
Hello Brent,
Those adjustments should already have a note, but it looks li
ust payments for "System: VOIDED OVERDUE FOR LOST". A
check in the database for entries in money.account_adjustment only shows note
entries for "System: OVERDUE REVERSED FOR CLAIMS-RETURNED" right now.
-Brent
On 1/27/16 3:06 PM, Dan Wells wrote:
Hello Brent,
Those adjustments should a
Hello Brent,
Those adjustments should already have a note, but it looks like your note
column is not displaying. Try adding it from the column picker in the upper
right corner of that box. The note should say “System: VOIDED OVERDUE FOR
LOST”. (Certainly not the best note as far as wording
.org<mailto:mmor...@noblenet.org>
On Mon, Jan 11, 2016 at 9:27 AM, Dan Wells
<d...@calvin.edu<mailto:d...@calvin.edu>> wrote:
Hello Rosie,
I think you are right in that this scenario (block holds when available, allow
holds for unavailable parts) is not supported by the current code
Hello Rosie,
I think you are right in that this scenario (block holds when available, allow
holds for unavailable parts) is not supported by the current code.
Unfortunately, I think getting it supported also won’t be especially simple,
especially from the UI side.
It’s simple to check if
Hello Jim,
We’re using Syrup here at Calvin. We just started our second semester using
it, so we’re still relatively green. Our install is also somewhat customized
for local needs.
Sincerely,
Dan
Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133
From:
Hello Lezlie,
Again, it isn't quite the same as how it works in Vandelay, but there is
another built-in method for autogenerating barcodes which can work almost
anywhere in Evergreen. If you try to create (or edit) an item and you use a
barcode starting with '@@', the system will
We also do more or less exactly what Jennifer and others have outlined in more
detail. When the scanning is done, we generally pull our missing list directly
from the DB, with a query something like the one listed below (adjust to suit),
which we then import into Excel for staff/student
Jesse,
Getting back to what you are trying to accomplish, is there a particular reason
you are exporting your MARC records? If you're just migrating the whole
database to a new server, I'd say exporting and reimporting the MARC isn't
something you'd need (or want) to do. It's also possible
Hello all,
This came up in Kathy's recent thread asking about the patron editor, and
rather than hijack that thread, I'd like to broaden the conversation a little,
because the same usability issues will affect many areas of the staff client.
To cut straight to the point, I strongly believe
Hello Rogan,
One question: since the conference this year is later than it has typically
been, do we still want to aim for 6 months out (which would put us in
November), or stick to a Sept./Oct. event? It would of course be nice to know
the 2016 conference dates to help decide, but I’m not
The Evergreen 2.6.6 maintenance release is now available.
Quick Links
* Download Page - http://evergreen-ils.org/egdownloads/
* List of Bugs Fixed - https://launchpad.net/evergreen/+milestone/2.6.6
* Changelog - http://evergreen-ils.org/downloads/ChangeLog-2.6.5-2.6.6
Hello all,
This email is an open invitation to join the #opw-evergreen channel,
particularly from 9am-noon eastern on Wednesdays and Fridays (our regular OPW
group meeting times). Given the duration of these events, we're opting to keep
using the separate channel for now and see how things
Hello all,
We currently sync to two different student information systems, one for the
college and one for the seminary. Evergreen does have a possible way to
classify identifiers (i.e. record their sources) via the
config.identification_type table as linked to the actor.usr.ident_type field.
Hello all,
With apologies for the general state of limbo for maintenance releases for 2.5
and 2.6, I just want to quickly note that the next releases are now scheduled
for next Wednesday, 11/5. I also want to mention that this will be the *last*
bugfix release for 2.5. (Security fixes for
Hello all,
Maintenance releases 2.6.3 and 2.5.7 are now available for preview testing:
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6.3.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6.3.tar.gz.md5
Hello all,
With apologies for the delays, maintenance releases 2.6.2 and 2.5.6 are now
available for preview testing:
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6.2.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6.2.tar.gz.md5
Hello all,
Just a quick note for anyone waiting, the maintenance releases for 2.5 and 2.6
are currently delayed. Please plan on these releases next week instead.
Thank you,
Dan
Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133
Assistant
From:
open-ils-general-boun...@list.georgialibraries.orgmailto:open-ils-general-boun...@list.georgialibraries.org
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Dan
Wells
Sent: Thursday, May 29, 2014 9:08 AM
To: 'open-ils-general'
Subject: [OPEN-ILS-GENERAL
Hello all,
Maintenance releases 2.6.1 and 2.5.5 are now available for preview testing:
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6.1.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6.1.tar.gz.md5
Hello Bill,
Thanks for the update. I have some thoughts about both of your questions, but
will focus on the link issue for now.
I’m not quite sure how to answer because I feel like we’re not asking the right
question. Rather than ask how links should behave, we might instead ask, what
One thing I'm not sure you can do in the reporter is group filters. For
example, I don't think you could pull 650a and 911b. Instead, you effectively
end up with the cross product of 650ab and 911ab. Sometimes this limitation
matters, sometimes it doesn't.
Also, if I'm mistaken, I'd love to
So why bother with a web based client? I only had to write a very small
HTML5 app to realize it is a nightmarish moving target of pain. Raise your
hand if you would willingly use
HTML/CSS/DOM/JS for anything if it wasn't the lowest common demoninator that
everything reads in an almost but
not
Hello Bill,
Thanks for the update.
I know others feel differently, but I don’t think we should rule out using
iframes for catalog integration. Iframes are actually pretty close in many
respects to the way the catalog “integrates” into the current (XUL) staff
client. The usual problems with
Struggling with some connectivity issues and lost part of my message. This:
That said, I believe we could rework some bits of the TPAC (and it might not
take much at all) to essentially use
the same templates to dynamically fetch a frameless TPAC “core” for displaying
inline in the staff
Hello Linda,
I don't fully understand how you built your holdings, but it looks like you
found something that worked for you.
Your update is failing on a record which already has both versions of the call
number (correct with '.' and incorrect with 'space'). See here:
Hello Paul,
You've pretty much nailed your problem as being the extra decimals before your
Cutters. While that's normal for an LC call number, I've looked around and
found nothing to make me believe that's common or accepted practice for DDC.
That said, as far as I can tell, the standard
but we have a year' case.
Dan
Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133
-Original Message-
From: open-ils-general-boun...@list.georgialibraries.org
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Dan
Wells
Sent: Friday
Hello all,
With 2.6.0 cut 10 days ago, it is high time for me to give one final update
before I pass the torch. I haven't given a formal email progress summary since
the beta (though a verbal update was given at the conference), so we'll be
looking back at both the RC and the 2.6 final
Hello Holly,
The browser-based client will be a normal website from the perspective of your
browser, so you'll be able to do any sort of window/tab management supported by
the browser. So, yes, you'll be able to do what you're asking about.
Dan
Daniel Wells
Library Programmer/Analyst
Hekman
Shall we accept Ben Shum's proposal to be Release Manager for Evergreen 2.7?
+1
, Calvin College
616.526.7133
From: open-ils-general-boun...@list.georgialibraries.org
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Dan
Wells
Sent: Wednesday, April 16, 2014 12:57 PM
To: 'open-ils-general'
Subject: [OPEN-ILS-GENERAL] 2.6.0 Available for Testing [RM2.6
Hello all,
Continuing the theme of new releases, 2.5.4 is now also available for preview
testing:
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.5.4.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.5.4.tar.gz.md5
Hello all,
I am happy to announce that a build of 2.6.0 is now available in the preview
area:
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6.0.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6.0.tar.gz.md5
I'm fine with the decision and consensus, but want to add one thing. I've met
a fair number of users who have a difficult time managing multiple windows in
an ongoing way (call them the closers). We obviously don't have any such
folks responding to this thread, but I think we should be open
Galen, I was deliberately vague in my earlier email, and hope you will
understand if I continue to be :)
I think it is fine to proceed with a separation mindset and see how it turns
out.
Thanks,
Dan
Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133
Hello all,
I am happy to announce that a build of the 2.6 release candidate is now
available in the preview area:
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6-rc1.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6-rc1.tar.gz.md5
Hello all,
The 2.6 release candidate has not yet been cut. Two of the blockers are still
in need of final review:
https://bugs.launchpad.net/evergreen/+bugs?field.tag=2.6-rc-blocker
Actually, though, the bigger reason we are waiting is that there are reports of
search issues on a production
Hello Bill,
Thanks for bringing this up! I think this is absolutely the linchpin for
getting the web staff client rolling.
Since this code is still so fresh, it seems ripe for hacking, so I've created a
conference Hackfest page and added this there.
Hello all,
Just a quick reminder that if we want 2.6 to stay on target, today is the goal
date for getting things reviewed and committed. We are to the point that we
certainly won't push forward until things are ready, so depending on how today
goes, I'll try to better define what ready means
Hello all,
Friday was the last day to assign bugs to RC1, and now it's time for what we
hope will be the last big push for getting 2.6 polished up and out the door.
The goal is to have things squared up by end-of-day on Wednesday, March 12, as
that should give us plenty of time to get things
of levity. Perhaps a
sing-along could lift a few spirits around here :)
2.next (2-Point-Next)
by Dan Wells
(tune: Tomorrow from Annie)
This code will come out
2-point-next!
Bet your bottom dollar by 2-point-next
this will run.
Just thinkin' about
2-point-next,
Clears away my anger towards the RM
Hello all,
I am working on a separate wrap up email for the 2.6 beta which was cut last
Tuesday, but since time is mercilessly marching on, I decided I should
highlight the planned schedule for the 2.6 RC which is nearly upon us. This
Friday, March 7, is the last day for targeting medium and
Hello all,
A more thorough beta summary email is pending, but this preview build is now
available for download and testing.
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6-beta1.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6-beta1.tar.gz.md5
Hello all,
The release candidate for Evergreen 2.5.3 is now available for download and
testing.
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.5.3.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.5.3.tar.gz.md5
Hello all,
We've collectively made a great deal of progress on the beta-targeted bugs, and
I've been really happy to see all the extra review effort. It looks like a
couple of the feature branches could use a few more minutes of baking, so I am
going to delay cutting the beta until Friday.
Hello all,
As most should be aware, the beta review period is scheduled to run through end
of day tomorrow. I've gone through the list of targeted bugs and marked 6 (so
far) which I consider to be blockers for getting the beta released:
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Dan
Wells
Sent: Wednesday, February 05, 2014 5:42 PM
To: 'open-ils-general'
Subject: [OPEN-ILS-GENERAL] 2.6 Beta Schedule and Bug List [RM2.6]
Hello all,
Based on the feedback I have received, the cutoff for targeting bugs
Hello all,
The 2.6 alpha is several weeks old, and we are already in the thick of the beta
process. But, as a friend of mine once said, better late than sorry, so here
is a quick summary of what we accomplished during the 2.6 alpha period, and
also some much deserved recognition for those who
Hello all,
Based on the feedback I have received, the cutoff for targeting bugs at
2.6.0-beta1 will be *Tuesday, February 11 at noon EST*. At that time, I will
create both an RC milestone (for new bugs) and an Evergreen-next milestone (for
new features not getting into 2.6). Please do not
Hello all,
The initially proposed 2.6 timeline called for a beta bug assignment deadline
of tomorrow, 2/4. That deadline is being extended. Right now it is
tentatively set for Friday, but may be pushed back a few days more pending
additional developer feedback.
I hope and expect to have
Hello all,
The first packaged release of Evergreen 2.6, alpha1, is now available for
download and testing.
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6-alpha1.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.6-alpha1.tar.gz.md5
616.526.7133
From: open-ils-general-boun...@list.georgialibraries.org
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Dan
Wells
Sent: Thursday, January 16, 2014 4:39 PM
To: 'open-ils-general'
Subject: [OPEN-ILS-GENERAL] Evergreen 2.5.2 Release Candidate Uploaded
Hello all
Hello all,
The review period for 2.6.0-alpha1 is underway. After some bug shuffling over
the last few days, it looks like we now have 38 bugs which are ready for
inclusion in the alpha (not counting 'Incompletes'). As sent in the previous
email, you can see the list here:
Hello all,
Just a quick reminder that today is the last day to target bugs for inclusion
in 2.6 alpha. As in past releases, new features will still be permitted until
beta, which is scheduled for early February. That said, the sooner something
is ready and targeted, the more likely it will
, Dan Wells
d...@calvin.edumailto:d...@calvin.edu wrote:
Hello all,
Just a quick reminder that today is the last day to target bugs for inclusion
in 2.6 alpha. As in past releases, new features will still be permitted until
beta, which is scheduled for early February. That said, the sooner
Hello all,
The release candidate for Evergreen 2.5.2 is now available for download and
testing.
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.5.2.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.5.2.tar.gz.md5
Hello all,
First, thank you to everyone for the show of support in keeping me on for 2.6.
A few people did express concern that I might be over-burdened as I continue as
the maintainer for 2.5. I think that concern is valid, but I think we can also
take a wait-and-see approach to the issue.
Hello Matthias,
The only usable user account credentials on a default Evergreen install are
those which you specify when using the --admin-user and --admin-pass
option to eg_db_config. Does that help?
Also, please note that installing Evergreen requires installing both OpenSRF
and
Hello all,
The release candidate for Evergreen 2.5.1 is now available for download.
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.5.1.tar.gz
http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.5.1.tar.gz.md5
Hello all,
I am happy and relieved to announce the first general release of Evergreen 2.5,
version 2.5.0. As usual for full releases, you may check out the Changelog,
read the release notes, or download the installation files here:
http://evergreen-ils.org/egdownloads/
I also want to
Hello all,
It's been two weeks since 2.5 RC1, and while testing and feedback for the RC
has been scant, I am eager to cut 2.5.0 as soon as possible. My primary source
of confidence is the fact that my library has been running 2.5 in production
since 10/13, but that enthusiasm is tempered by
Hello all,
I am pleased to announce that Evergreen 2.5-rc1 is now available for download.
Once again, thank you to the many folks who put in some extra time to help us
get to this point! You can grab RC1 from the downloads page here:
http://evergreen-ils.org/egdownloads/
Given the
Hello all,
Friday marked the first beta release of Evergreen 2.5. You can download it
here:
http://evergreen-ils.org/egdownloads/
As noted in my previous email, we are a bit behind schedule, and looking back,
I think vacation season ending, plus Hack-a-Way activity, plus general
Hello all,
[NOTE: This message was sent yesterday, but I am told that list problems
prevented it from getting through, so this is a resend.]
The purpose of this email is to announce the official delay of the 2.5 release,
and to establish a new timeline for release. A number of factors are
Hello all,
The beta-blockers for 2.5 are all tagged and ready for review. You can see
them here:
https://bugs.launchpad.net/evergreen/+bugs?field.tag=2.5-beta-blocker
I lowered the count from the 35 planned to 30 because a) this email is a day
late, and b) I wanted to leave room for any I
Hello all,
This is just a quick reminder that today, 9/10, is the last day to target
features for inclusion in 2.5. This is not a guarantee that your feature will
get in if targeted today, but it has a pretty good chance.
Thanks,
Dan
Daniel Wells
Library Programmer/Analyst
Hekman Library,
Hello folks,
Hard to believe, but we'll soon be at the end of the 2.5 alpha1 targeting
phase. Please continue targeting bugs at '2.5.0-alpha1' in Launchpad through
the end of the day tomorrow.
So far, the list to tackle looks like:
Hello all,
First, thanks again to everyone who put in some extra time to make commits for
the m2 phase of Evergreen 2.5. It didn't live up to the drama of m1, but that
is a good thing. We entered Friday needing only 5 more commits, and we
exceeded that goal. When all was said and done, our
Hello everyone,
First, thank you to everyone who has contributed to the m2 commit push. Today
is the last day, and the goal is well in range! In four days, we have gone
from 62 ready m2 pullrequests to 36 still needing review; just 6 more to reach
our target. Keep pushing!
Again, here is
Hello all,
As usual, the summer is cruising by at a rapid pace. Already we find ourselves
at the first of July, the suggested last day for targeting bugs at M2. If you
have something you feel is ready for review, but haven't pushed your branch
yet, now is the time! Also, since Monday
Hello Beth,
In this case, your problem is being caused by the 'x, 01' in your pattern.
This subfield is for a calendar change meaning the volume should increment at
a certain month (or day, or season), but your serial is not a monthly, and has
no month in the caption. If you remove the 'x,
Hello all,
Milestone 1 (aka m1), the first phase of the 2.5 development process, came to a
close on Friday. We entered the commit phase with 63 bug reports needing
review, many of them being part of a bug backlog which built up over time.
With the number so high, the challenge given to the
Hello all,
Today was targeted as the last day for getting commits into m1. According to
my count [1], we have gone from 63 branches ready to merge to... 54 (after
removing Incomplete tickets).
I have to admit, this is a little disappointing. Maybe people just forgot.
Maybe I didn't
Hello everyone,
In my last communication, I indicated that 5/27 would be the suggested cutoff
date for targeting bugs in Launchpad at Milestone 1 (2.5.0-m1). When I wrote
that, I wasn't thinking about the fact that it was a U.S. holiday. So,
everyone gets a one day extension, and today is
Hello everyone,
After a couple weeks of suspense and anguish, you are now at last reading my
first official communication as release manager [RM] for 2.5. In the interest
of general efficiency, and to encourage dialog over unnecessary detail, I will
try to be succinct.
Announcements:
1)
The idea of newly added closed dates pushing back current checkouts due on that
date sounds like a good wishlist request to me, if anyone is so inclined to
create one:
https://bugs.launchpad.net/evergreen
Thanks,
Dan
--
This isn't especially relevant to the conversation, but last I checked,
Evergreen actually post dates fines to the end of the fine period in which
they occur. In other words, daily fines are all dated with a timestamp of
23:59 regardless of what time the fine generator runs. This made the
Hello Eva,
This seems likely to be a bug. If you haven't already, could you report this
at https://bugs.launchpad.net/evergreen ? That will at least reduce the
likelihood of this issue getting lost.
Thanks,
Dan
--
--
*
Daniel Wells, Library Programmer Analyst d...@calvin.edu
Hekman Library at Calvin College
616.526.7133
On 1/4/2013 at 3:52 PM, Dan Scott d...@coffeecode.net wrote:
In the end, I'd really like to not have this
Hello all,
This is a pretty complex subject, and anyone interested in diving in full on
should probably start here:
http://www.loc.gov/marc/ldr06guide.html
In all, there are at least five major factors which all relate to describe the
type of an item. They are:
Leader/06 - Type of record
Hello Sheila,
Lost marking in Evergreen is handled by a flexible (but somewhat complex)
Action Trigger system. The event definition for lost marking in a stock
install can only be easily configured for number of days overdue, not for
individual circ modifiers, so any checkout which is, for
Hello Janet,
We are on 2.2 but still using JSPAC for our primary catalog. Our TPAC is still
a work-in-progress, but if you want a sneak peek:
http://ulysses.calvin.edu/eg/opac/home
Dan
--
*
Daniel Wells,
Calvin College is seeking an Electronic Services Emerging Technologies
Librarian (ESET). This position is responsible for introducing, designing,
developing, and maintaining the technologies used by the library staff and the
community of library users with the goal of providing an exceptional
Hello Kathy,
--
*
Daniel Wells, Library Programmer Analyst d...@calvin.edu
Hekman Library at Calvin College
616.526.7133
On 5/17/2012 at 10:44 AM, Kathy Lussier kluss...@masslnc.org wrote:
1. After setting up
Hello Tim,
You can generally communicate with Active Directory via the LDAP protocol. If
that is the case for your installation, there is a feature in 2.2 which allows
for basic authentication using LDAP user bind. To answer your listed concern,
it is possible to limit this feature to a
Hello,
I am also unfortunately not able to reproduce this problem on 2.2. If anyone
can reproduce this, could you please post both your pattern code and also the
holding code of your starter, along with your exact Evergreen version?
Thanks,
Dan
--
Calvin College is seeking an Electronic Services Emerging Technologies
Librarian (ESET). This position is responsible for introducing, designing,
developing, and maintaining the technologies used by the library staff and the
community of library users with the goal of providing an exceptional
Hello Mary,
Sorry for the delayed reply. What you are saying is correct in 2.0. The
original thinking was that we wanted a unit for every item, as one eventual
goal is to be able to generate shelving location based holdings summaries.
Without units, the serial items have no shelving
Hello Liam,
No need to apologize, this is quite the amazing effort!
The only thing I would add at first glance is that there is also a specific
'Overdue Circulation' source. If you use that one rather than 'Circulation',
it automatically covers the 'due date' and 'checkin time' filters, and
Hello Jesse,
On 1.6 you need to edit '/openils/var/web/xul/server/patron/ue_config.js'.
Near the top you will find a 'defaultState' variable set to 'GA'.
Dan
On 9/9/2011 at 6:54 AM, Jesse Ephraim jephr...@roanoketexas.com wrote:
Does anyone know where to reset the default GA- that appears
the Evergreen feature summary some of us are working on to
LDAP
supported. I've added it as feature SA537 (System Admin 537) in case
anyone wants to review it.
I'd say no, LDAP isn't supported, because Dan Wells' patch is not part
of the core Evergreen code.
--
Anoop Atre
IS Developer
, Dan Wells wrote:
There may be other cases where Patch Available would make sense, but at
least for this case, I think Under Development is our best bet (if such
a
category already exists). The patch which is available is quite old, and
is
really more of a starting point than something which
Hello Gordana,
We are currently using LDAP to authenticate. I may be mistaken, but I believe
the code attached to the following message is still our current version, with
the one exception of an |= which is supposed to be an ||=.
Hello Gordana,
This was a skin level fix, so since you are using a custom skin ('nc'), it must
be applied manually to your skin after upgrading. Since the fix is simply
deleting a single line, it should be pretty simple to take care of. See here
to view the actual change needed:
1 - 100 of 121 matches
Mail list logo
