https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42433 David Nind <david@davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |david@davidnind.com --- Comment #2 from David Nind <david@davidnind.com> --- I can confirm the behavour you described. Instead of going into the developer tools, I logged out and then logged back in - the changes made in the table administration were then shown (that is, the column you asked to be hidden by default is now hidden). (In reply to Caroline Cyr La Rose from comment #1)
I feel like this is a lot of steps to remove a column and not really manageable by all library staff. Is this the normal behaviour of the save state thing? (I admit I don't understand the purpose of the save state option... :/ )
I'm always confused by these options - I don't really know what they mean, and feel like they are written in developer speak: - Save configuration state on page change - Save search state on page change I'd be happy to attempt a rewrite, if someone could explain what they are supposed to do. So for "Save configuration state on page change" selected: - make changes to the table columns (using the "Columns" dropdown list when you are on the page with the table) - go somewhere else then go back to the table ==> the column changes you made are remembered - if you log out then log back in: ==> the changes you made aren't remembered (things are set back to the default in the table settings) With it not selected, if you go away and then go back to the table later on in the same session, any column changes aren't remembered. I don't have any idea what the "Save search state on page change" means (it is also not an option available for all tables). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.