#39227 closed defect (bug) (fixed)
Changeset parameter not generated
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | 4.7.3 | Priority: | normal |
| Severity: | normal | Version: | 4.7 |
| Component: | Customize | Keywords: | commit has-patch fixed-major |
| Focuses: | Cc: |
Description
I tried this new feature with Twenty Seventeen, went to Customizer, changed Color schema in left column and there is no changeset URL parameter to copy and share?
I waited a little bit, but nothing happened until I clicked somewhere into preview area. Then, changeset parameter was finally generated. I do not think it is expected behaviour?
Attachments (3)
Change History (21)
#1
@
9 years ago
- Keywords needs-patch added
- Milestone changed from Awaiting Review to 4.7.1
- Owner set to westonruter
- Status changed from new to accepted
#2
@
9 years ago
Yes, you are right, I did not try to click URL bar when I did not see that there is no changeset_uuid :-) When i click URL, parameter appears (with a small delay).
#3
@
9 years ago
- Keywords has-patch needs-testing added; needs-patch removed
I was able to duplicate the issue on latest nightly release and 4.7 . I attached a patch, let me know if that works for ya!
This ticket was mentioned in Slack in #core by jeffpaul. View the logs.
9 years ago
#5
follow-up:
↓ 6
@
9 years ago
- Keywords needs-testing removed
@asalce Nice work! I tested 39227.diff and it fixes the issue.
Here is a screencast showing the issue, before and after the patch for the record:
before: https://cl.ly/1M2j1b2A3J1N - the uuid is not added initially
after: https://cl.ly/3p2W1d0H470b - the uuid is added immediately
@westonruter I notice when I hit refresh I get the "Changes you made may not be saved." warning modal... is that still true? with the changesets, when i hit refresh my changes aren't lost, right?
#6
in reply to:
↑ 5
@
9 years ago
Replying to adamsilverstein:
I notice when I hit refresh I get the "Changes you made may not be saved." warning modal... is that still true? with the changesets, when i hit refresh my changes aren't lost, right?
It's not strictly true but it it may be true in practice because there is no UI or regaining access to the auto-draft changeset. The in the UI being developed in the Customize Snapshots plugin, upon saving an actual explicit Draft of the changes the AYS dialog in that case will not surface.
#7
@
9 years ago
- Keywords needs-patch added; has-patch removed
I also updated the Customizer Browser History plugin to implement a related fix: https://github.com/xwp/wp-customizer-browser-history/pull/16
#12
@
9 years ago
- Resolution fixed deleted
- Status changed from closed to reopened
It is closed for 4.7.1 milestone, but there is no commit for 4.7 branch?
#13
@
9 years ago
- Milestone changed from 4.7.1 to 4.7.2
Right, looks like @westonruter missed to actually re-open the ticket in comment:10.
Moving to 4.7.2 since 4.7.1 is already in the pipe.
The changes get persisted into a changeset currently at the
AUTOSAVE_INTERVALor whenever youblurthecustomize.phpwindow (orbeforeunloadit). This is why you see thechangeset_uuidappear in the URL the moment that you click into the preview, because this is ablurevent on thecustomize.phpwindow. This is probably an unintentional side effect of the fix done in #39081. This needs to be fixed.However, when starting customization with starter content initially supplied, I'm not seeing the URL update as expected. I am seeing this behavior once
fresh_siteis0. Specifically, once you click into the URL bar you should see thechangeset_uuidparam supplied, as in changeset_uuid-param-added-upon-window-blur.mov.Nevertheless, we really shouldn't be waiting for the
customize_changesetpost to be created before updating the URL with thechangeset_uuidparam. The moment that thesavedstate becomesfalsewe should at that moment make sure that thechangeset_uuidparam is added to the URL.