Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • qfq qfq
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 14
    • Merge requests 14
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • typo3typo3
  • qfqqfq
  • Merge requests
  • !417

S13679 Multiple changes in php and js to get tablesorter-view-saver work in...

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Enis Nuredini requested to merge F13679_subrecord_tablesorter_view_saver into develop Mar 18, 2022
  • Overview 0
  • Commits 3
  • Pipelines 2
  • Changes 6

S13679 Multiple changes in php and js to get tablesorter-view-saver work in subrecord. Implemented new parameter for subrecord to give own attributes. Selecting views or columns doesn't impact browser history and record lock anymore. Only saving a new view or deleting an existing view still impacts browser history (but not record lock), It's impossible to prevent it because we need the page reload to get new existing views after deleting or saving a new one.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: F13679_subrecord_tablesorter_view_saver