We have had a few queries about suggestions not working correctly in
3.8, that seem to be the result of this:
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7300#c6
can we decide the path to solving this? Making suggestions hidden by
default is distinctly a regression for many
I completely agree that this is confusing, and it took my a while to
figure out that when you reach this screen the filter is not empty. (The
site is picked in acquisition information), actually if you play a
little with the filter, then click clear, you go back to a setting
where you only see
I think I would still prefer a system preference here. But I also like the idea
to remember the last state for each user.
But I think this would be harder to do - while a system preference might be the
easier way to go back to former behaviour?
Katrin
-Original Message-
From:
On Mon, Sep 24, 2012 at 3:45 AM, Fischer, Katrin
katrin.fisc...@bsz-bw.de wrote:
I think I would still prefer a system preference here. But I also like the
idea to remember the last state for each user.
But I think this would be harder to do - while a system preference might be
the easier
+1 for having a preference
Marc
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs :
Op 25-09-12 00:18, Nicole Engard schreef:
+1 ... too many of our libraries are consortia with one central
ordering location and they don't want to limit on branch. This is a
regression and I think we need a preference, but if we can't have that
easily then it must remember the last state and
In my opinion, the current branch filtering can be a behavior common to
all intranet pages.
Maybe a combo-box next to login.
In this case, it would be easy to know what is the current filtering.
It would be initialized with user's branch and its current value could
be saved in cookie to remain
Hi
I have a problem while installing koha on a machine (i install with
debian package)
I have this message ERROR 2002 (HY000): Can't connect to local MySQL
server through socket '/var/run/*mysqld/mysqld.sock' (2)
What i don't understand is
mysql well running
$ service mysql status
Hello all,
In the past we were all putting bug numbers in our updatedatabase
messages like this:
Upgrade to 3.09.00.034 done (Bug 8207: correct typo in authority types)
But more and more I'm seeing this:
Upgrade to 3.09.00.035 done (Adding PrefillItem and
SubfieldsToUseWhenPrefill
Hi,
On Mon, Sep 24, 2012 at 12:15 PM, Nicole Engard neng...@gmail.com wrote:
When documenting new features I often need to refer to the bug report
to get more information but without the bug number I have to do
searches to find the right bug and it can sometimes be easy - but
sometimes not so
Can we start putting our bug references in our updates?
I agree, and would add that there's no reason to hold back in your
database update description. If the bug number and title don't
describe well enough, elaborate.
-- Owen
--
Web Developer
Athens County Public Libraries
Can we start putting our bug references in our updates?
+1
This rule should be written down somewhere in the Wiki.
But where?
Marc
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
At 05:07 PM 9/24/2012 +0200, Fridolyn SOMERS wrote:
In my opinion, the current branch filtering can be a behavior common to
all intranet pages.
Maybe a combo-box next to login.
In this case, it would be easy to know what is the current filtering.
It would be initialized with user's branch and
Hi,
The September 2012 edition of the Koha Community Newsletter has been
posted to
http://koha-community.org/koha-newsletter-volume-3-issue-9-september-2012/.
Cheers,
Daniel Grobani
Koha Community Newsletter Editor
___
Koha-devel mailing list
Paul,
On Mon, Sep 24, 2012 at 6:07 PM, Paul pau...@aandc.org wrote:
We have just discovered a problem with 3.8.4 -- before I can rule out
whether it is 'our' db or setup that is at fault, or a more general issue,
I would appreciate some help.
Basically our authorities are no longer
I've uploaded new Debian packages for the latest 3.6 and 3.8 releases.
Normally this isn't worth an email, but in this case it's necessary to
be aware that Debian won't automatically upgrade it for you when you
ask.
New dependencies have been added, and so it is now necessary to do:
sudo
Samuel Desseaux schreef op ma 24-09-2012 om 17:19 [+0200]:
I have this message ERROR 2002 (HY000): Can't connect to local MySQL
server through socket '/var/run/*mysqld/mysqld.sock' (2)
is that '*' really there? Because it seems like a strange thing to have.
Also, does the file
On Mon, Sep 24, 2012 at 8:11 PM, Jared Camins-Esakov
jcam...@cpbibliography.com wrote:
So ... new biblios and items are being recorded, but the cross referencing
to authorities appears to have died with the upgrade to 3.8.4
Most unfortunately, I can reproduce this in my sandbox and the [now
18 matches
Mail list logo
