-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Table columns from history and assets tab conflicts #7834
Comments
Seems like this option
overrides per-table "data-" attributes. I have investigaed codebase and found that each table has personal attribute "data-cookie-id-table". So i think that we can remove line "cookieIdTable: '{{ Route::currentRouteName() }}',". |
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
This issue has been automatically closed because it has not had recent activity. If you believe this is still an issue, please confirm that this issue is still happening in the most recent version of Snipe-IT and reply to this thread to re-open it. |
Please confirm you have done the following before posting your bug report:
Describe the bug
After changing column set on assets tab of any hardware we have no columns on history page.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I want to have separate column set for each table on each page and it should be in memory (cookie or something else)
Server (please complete the following information):
Desktop (please complete the following information):
Error Messages
This problem was explained here #6038
And probably here #4784
The text was updated successfully, but these errors were encountered: