[Koha] JSPrint & ff57

Are you saying that doing something like the following: * Type *about:config*, in the address bar of Firefox. Click “I’ll be careful, I promise!” on the warning message. * Type, *print.alway**s* in Filter. * Look for *print.always_print_silent*. * Double-click the value to change it to

[Koha] JSPrint 57

Hello Koha Community, how we'll solve printing from Koha in new FF? Mozilla close debate about silent printing https://bugzilla.mozilla.org/show_bug.cgi?id=1385827 Its time to move to other browser? Which solution for printing do you prefer now? Thank you Mike

Re: [Koha] Software error: ~~Duplicate entry '320' for key 'PRIMARY' at~~~

Yes the "about page" lists all duplicate IDs for all data affected. On Nov 16, 2017 19:47, "Scott Owen" wrote: > Select * from old_reserves where reserve_id = (320) > > seems to find the specific one..any way to find all the records in > question (like on the "about page"

Re: [Koha] Software error: ~~Duplicate entry '320' for key 'PRIMARY' at~~~

Select * from old_reserves where reserve_id = (320) seems to find the specific one..any way to find all the records in question (like on the "about page" ) ? -S On Thu, Nov 16, 2017 at 3:25 PM, Pedro Amorim wrote: > Hey, you might have already checked this but

Re: [Koha] Software error: ~~Duplicate entry '320' for key 'PRIMARY' at~~~

Hey, you might have already checked this but just to be sure: The problem you were having with circulation also applies to holds, borrowers, records and items I think. If this problem is related, you might want to check ID 320 on old_reserves table and if its there, the same solution from before

[Koha] Software error: ~~Duplicate entry '320' for key 'PRIMARY' at~~~

Another erroris this one also related to the bug 18003 ? seems very similar. From one of my staff... I put a book that is checked out on hold. When it is returned, the system tells me who is waiting. I confirm the hold When I check the book

Re: [Koha] DBMS auto increment fix

"This situation comes up quite often in the list." -- so sorry, Google got me going in the correct direction, but was missing that last little "how to" . I guess I should pay more attention to the list. Thank you again, -S On Thu, Nov 16, 2017 at 2:12 PM, Pedro Amorim

Re: [Koha] DBMS auto increment fix

You're welcome! I hope this helps others in the future. This situation comes up quite often in the list. Have a good one, Pedro Amorim On Nov 16, 2017 18:04, "Scott Owen" wrote: > You Sir, > > ARE AWESOME ! > > thank you so much. > > -S > > > On Thu, Nov 16, 2017 at

Re: [Koha] DBMS auto increment fix

You Sir, ARE AWESOME ! thank you so much. -S On Thu, Nov 16, 2017 at 1:05 PM, Pedro Amorim wrote: > 1) Copy the ID's from About Koha -> System Information > > 2) *Select * from old_issues where issue_id IN () * Confirm > the listed rows are the ones you want to

Re: [Koha] DBMS auto increment fix

1) Copy the ID's from About Koha -> System Information 2) *Select * from old_issues where issue_id IN () * Confirm the listed rows are the ones you want to delete; 3) *Delete from old_issues where issue_id IN ();* 4) Check in items and be happy. This should work. Have a good one, Pedro

Re: [Koha] DBMS auto increment fix

thank you so much for the fast response. Is there a report / SQL query to find the duplicate ids that exist on both issues and old_issues tables ? On Thu, Nov 16, 2017 at 12:54 PM, Pedro Amorim wrote: > Scott, > > The documented fix only prevents the problem from

Re: [Koha] DBMS auto increment fix

Scott, The documented fix only prevents the problem from happening in the future for new IDs, it will not fix the IDs already compromised. This is the conversation I had with Marcel a couple weeks ago regarding this issue:

[Koha] DBMS auto increment fix

Hi all, I have the following errors when my staff try and check in items: "The item has not been checked in due to a configuration issue in your system. You must ask an administrator to take a look at the about page and search for the "data problems" section" I have followed the solution as