Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • WordPress WordPress
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • WordPressWordPress
  • Issues
  • #67
Closed
Open
Created Jul 22, 2020 by haystack@haystack🤔Maintainer

Slow down the frequency of WordPress "heartbeat" calls in CiviCRM admin

Heartbeat is important to WordPress for a number of tasks - e.g. checking continued authentication whilst on a page and implementing edit locks on post/page edit screens - but it is less important on CiviCRM admin pages and consumes server resources. Reducing the frequency of calls minimises the impact on servers and can make CiviCRM admin pages more responsive.

PR here: https://github.com/civicrm/civicrm-wordpress/pull/214

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking