https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38436 --- Comment #86 from Michaela Sieber <michaela.sieber@kit.edu> --- (In reply to Jonathan Druart from comment #84)
(In reply to Michaela Sieber from comment #78)
Before you push this, please test this scenario :
search for "Programming the Perl DBI" (= koha/catalogue/detail.pl?biblionumber=13 )
Check that the item has no itemcallnumber, that's why the column 'Call number' is not displayed
Check that the itemcallnumber in the admin table settings is NOT hidden by default (checkbox is not active)
Go back to biblionumber=13 and edit the item. Add an itemcallnumber in the editor (Field o - Full call number)
save the item.
Go again to the "Normal" detail view.
Now I have the problem, that I still don't see the column Call number.
Yes, this is a tricky one. I thought I could fix this behaviour here but failed. It's reported separately on bug 38433 (reopened now).
Yes it is tricky. I read all your thoughts in this bug , thats why I tested it with the mentioned workflow And to add new data to an item record is not a "special" use case, this is daily business in a library
If we are saving the state (column visibility), it is saved automatically when a visibility changes, manually or with this behaviour we have on this table (hide the column if empty). To distinguish them we need to store separately the state desired by the user, and the "automatic state" generated by this "hide if empty" behaviour.
Exactly, that is the only solution.
It should not be very hard, but this is too late for 24.11.00
Unfortunately.
If this is too confusing, maybe a solution for 24.11.00 could be to disable "save state" by default for this table, with a note in the setting.
Yes, it definitly should be disabled because the feature makes no sense as it works not as an end-user would expect it. -- You are receiving this mail because: You are watching all bug changes.