On Fri, Dec 16, 2011 at 10:12 PM, Chris Nighswonger <
cnighswon...@foundations.edu> wrote:
> Hi Paul,
>
> On Fri, Dec 16, 2011 at 7:09 PM, Paul wrote:
>
>> Lines 3006-3008 of biblio.pm called from additem.pl:
>>
>># get title of the record (to store the 10 first letters with the
>> index)
Hi Paul,
On Fri, Dec 16, 2011 at 7:09 PM, Paul wrote:
> Good evening,
>
> First glitch with 3.06 has appeared: adding an 'item' after importing
> biblio via z39.50 is functional (it adds the item !!!) but the admin
> interface gives:
>
> Software error:
> Can't call method "subfield" on an undef
Good evening,
First glitch with 3.06 has appeared: adding an 'item' after importing
biblio via z39.50 is functional (it adds the item !!!) but the admin
interface gives:
Software error:
Can't call method "subfield" on an undefined value at
/usr/share/koha/lib/C4/Biblio.pm line 3008.
Lines
Well, cut and paste strikes again... here it is with the missing portion
On Fri, Dec 16, 2011 at 2:41 PM, Chris Nighswonger <
cnighswon...@foundations.edu> wrote:
> Moving this to the devel list
>
>
> On Fri, Dec 16, 2011 at 1:24 PM, Paul wrote:
>
>> At 12:51 PM 12/16/2011 -0500, Chris
Moving this to the devel list
On Fri, Dec 16, 2011 at 1:24 PM, Paul wrote:
> At 12:51 PM 12/16/2011 -0500, Chris Nighswonger wrote:
>
>> Hi Paul,
>>
> [snip]
>
> I see no reason why the errors you posted in this thread should/would
>> affect the ability to put a server into production.
>>
>
Liz Rea
> I think more likely people are forgetful - would be nice to add this
> to git-bz as a flag so it was "forget proof."
It is already possible with git bz attach -e BUGNUM BRANCHPOINT
which is documented on
http://wiki.koha-community.org/wiki/Git_bz_configuration#Signing_off
but our bugzil
Right you are, I didn't know about that when I sent my message. So - everybody,
obsolete your patches when you attach them using git bz!
It's easy and fun!
Liz Rea
l...@nekls.org
<>
On Dec 16, 2011, at 10:30 AM, Paul Poulain wrote:
> Le 16/12/2011 17:22, Liz Rea a écrit :
>> I think more like
Le 16/12/2011 17:22, Liz Rea a écrit :
> I think more likely people are forgetful - would be nice to add this to
> git-bz as a flag so it was "forget proof."
???
git bg attach -e
=> the -e will show you the commit, with #obsoletes at the end.
Just remove the # and you'll obsolete the old
I think more likely people are forgetful - would be nice to add this to git-bz
as a flag so it was "forget proof."
Liz Rea
l...@nekls.org
<>
On Dec 16, 2011, at 8:18 AM, Magnus Enger wrote:
> On 16 December 2011 14:08, Paul Poulain wrote:
>> (feel free to add this to the wiki if you think it'
On 16 December 2011 14:08, Paul Poulain wrote:
> (feel free to add this to the wiki if you think it's worth it)
Done, and thanks!
http://wiki.koha-community.org/wiki/Bugzilla#To_mark_a_patch_obsolete
Best regards,
Magnus Enger
libriotech.no
___
Koha-de
Hello world,
It seems that some of you have problem marking an attachment obsolete
without attaching another file.
I found how to do that a while ago, so, as I know, I share:
* go to the bug
* on the attachment line, you've 3 links: "file title/description",
"Details" and "Diff". Click on Details
+1 to displaying all standard information on the Details page. If a
library has this info in a record, but DOESN'T want it displayed, then can
either remove the info, or strip the field out with JQuery. Hopefully
'sensitive' information is not being put in MARC records...
I'm with Magnus on this
2011/12/15 Fischer, Katrin :
> +1 from me too.
>
> The XSLT is done so that only information in your records shows up. I don't
> see why people would not want that.
+1
In an ideal world I think we would have some cool graphical tool where
each library could easily configure their own display by d
13 matches
Mail list logo
