-
Notifications
You must be signed in to change notification settings - Fork 0
revisions create reports success but doesn't create revision when content unchanged #37
Copy link
Copy link
Open
Description
Description
The elementor-cli revisions create command reports success even when WordPress doesn't actually create a revision.
Steps to Reproduce
- Push a page to WordPress:
elementor-cli push 2902 --site staging - Immediately run:
elementor-cli revisions create 2902 --site staging --message "My backup" - Command outputs:
- Creating backup... ✔ Created backup for page 2902 Site: staging Note: My backup - List revisions:
elementor-cli revisions list 2902 --site staging - No new revision was created - the revision list is unchanged
Expected Behavior
Either:
- The command should actually force WordPress to create a revision, OR
- The command should detect that no revision was created and show a warning/error message
Actual Behavior
The command shows a success message (✔ Created backup) but no revision is created because WordPress skips creating duplicate revisions when content hasn't changed.
Workaround
Make a small change to the page content and push it - this triggers WordPress to create a real revision.
Environment
- elementor-cli (latest)
- WordPress in Docker/Podman staging environment
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels