Created attachment 41414 [details] Uploaded incorrect file. Going to Administration | Additional Parameters | Configure columns | Circulation and checking Is Hidden By Default for Price hides the Fine column in the checkout display, not Price. Clicking on Show/hide columns for the checkout display does not show Price as an option, and Fine is unchecked.
Created attachment 41415 [details] Change columnns Circulation
Created attachment 41416 [details] Checkout display after change applied
Created attachment 41417 [details] Checkout display before change applied
John, try and restart memcached. It should fix your issue.
Hi Jonathan John Yorio submitted this one on our behalf - we found it when fist upgraded to 3.20.02.000. Might have been fixed along the way since then. I can confirm it still happens in our live system. I hope this will clarify the symptoms: It is a mismatch between the show/hide column names in Administration and those that appear in circulation. Koha admin - Columns settings - Circulation Set Charge and Price to Hidden by default Expected result: For checkout display not to show Charge or Price. This is what ACTUALLY happened: Checkout still shows Price. Fine disappears! Drop-drown to show/hide that is in the checkout screen - does not list hide Price at all. Seems the programmers mixed up the Price and Fine fields. In the Admin module - hiding Price actually hides Fine, and Fine is not listed in the Columns Settings table at all. In the checkout screen drop-down - the fields seem to be correctly named, and hide Price is simply not an option.
Created attachment 49871 [details] Admin show/hide settings
Created attachment 49872 [details] Show/hide setting in Checkout Compare with my other attachment & Note the different columns listed, and the result in the checkout display.
Oh - I should say that we would like to hide "Price" - the one column that we are not able to turn off! Thanks, Agnes
Indeed, bug confirmed on 3.20. See bug 14841 for a fix, I will ask the 3.20 release maintainer to backport it *** This bug has been marked as a duplicate of bug 14841 ***