https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42910
--- Comment #15 from Jonathan Druart <[email protected]> --- (In reply to Anneli Österman from comment #12) > I tested again and I think there is still something strange happening here. > > Test 1: I took off all "Is hidden by default" checksmarks from table > configuration, logged out (so that cache is emptied), logged in and made a > search. Then opened one of the records. Checked everything visible from > Columns dropdown menu and used an arrow to move to the next record. Then I > opened the Columns dropdown menu and only some of the columns were still > checked. See attachment b42910-1.png. > Test 2: This time I hid all columns from table configuration. Logged out and > in, made a search and checked all columns visible from the Columns dropdown > menu. Then moved to the next record. Again, only some of the columns were > visible. See attachment b42910-2.png. There is only one difference to the > first test: Call number also stays visible. > > Same seems to happen when holdings table is seperated into two tabs with > SeparateHoldings and SeparateHoldingsBranch systempreferences Yes, this is how it's expecting to work on this table (if I understand correctly what you reported). This is related to the warning in the admin: "Please note that if a field is not used on the first page of items in the holdings table, it will be automatically hidden from display and can be made visible on demand. You can still use the column configuration to permanently hide columns from the holdings table." If a column has no value (ie. is empty for all rows) then it's hidden automatically. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
