craftcms / craftcms/cms

Delayed availability of "Update Entry" button

Open
#4,343 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
3.6k
Forks
705
Avg merge
1d 5h
Merged PRs (30d)
134

Description

Description

It takes anywhere from 5 to 10 seconds for the "Update Entry" button to be enabled after making a change to an entry.

Steps to reproduce
  1. Open an existing entry
  2. Make a small change like punctuation in the description
  3. Wait for "Update Entry" button to become enabled
Additional info
  • Craft version: Craft Pro 3.2.0-alpha.7
  • PHP version: 7.3.2
  • Database driver & version: MySQL 5.6.34
  • Plugins & versions:
    "craftcms/cms": "3.2.x-dev#66ddb7eed8dc5a84f0695a7c9e3d0c1c2f9808bd",
    "vlucas/phpdotenv": "^2.4.0",
    "craftcms/redactor": "2.3.3.2",
    "mmikkel/incognito-field": "1.1.1.1",
    "rias/craft-position-fieldtype": "1.0.14",
    "markhuot/craftql": "1.3.2",
    "verbb/super-table": "2.1.20",
    "marionnewlevant/match-input": "v2.0.1",
    "fruitstudios/linkit": "1.1.11",
    "nfourtythree/entriessubset": "1.2.1",
    "craftcms/aws-s3": "1.2.2",
    "nystudio107/craft-units": "1.0.3",
    "doublesecretagency/craft-cpcss": "2.1.0",
    "doublesecretagency/craft-smartmap": "3.2.2.1",
    "craftcms/store-hours": "2.1.1.1",
    "elivz/craft-single-cat": "1.2.1",
    "fortrabbit/craft-copy": "1.0.0-RC5",
    "aelvan/preparse-field": "v1.0.6",
    "spicyweb/craft-fieldlabels": "1.1.1",
    "rias/craft-password-policy": "1.0.4",
    "craftcms/element-api": "2.5.4",
    "craftcms/feed-me": "4.1.0",
    "verbb/workflow": "1.1.9",
    "robuust/craft-reverserelations": "1.1.5",
    "mmikkel/cp-field-inspect": "1.0.5",
    "doublesecretagency/craft-inventory": "2.0.2",
    "fortrabbit/yii-memcached": "^1.0",
    "putyourlightson/craft-sendgrid": "1.1.0",
    "doublesecretagency/craft-cpjs": "2.1.0",
    "doublesecretagency/craft-cpbodyclasses": "2.1.0",
    "solspace/api-caller": "*"

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report identifies no source files, tests, or entry points. Start by reproducing the delayed enabling behavior on Craft 3.2.0-alpha.7 with the listed environment, then trace the entry-editing interface; done means the “Update Entry” button becomes enabled promptly after a small change.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.