Support » Theme: Hestia » Customizer variables left in the URL

  • Topher

    (@topher1kenobe)


    When I use the customizer, and then close it, the URL keeps this kind of string in it:

    ?customize_autosaved=on&customize_changeset_uuid=94594707-b603-44f3-827a-9ee7be533681

    Then when I go to use the customizer again, it says

    “Something went wrong.

    This changeset cannot be further modified.

    Customize New Changes”

    How can I avoid that? I’m using Local by Flywheel

Viewing 5 replies - 1 through 5 (of 5 total)
  • Hi Topher,

    Would you mind posting the link to your site in question? So that we can offer you with a detailed response.

    Thank you!

    Topher

    (@topher1kenobe)

    Sorry, it’s my local machine.

    Hey @topher1kenobe,

    This doesn’t seem to be a theme specific issue. This is how WordPress acts when you leave the customizer without saving the changes.

    It’s pretty weird from an UX perspective, if you ask me. You just have to be careful to clear the changeset parameter before going back into the customizer.

    All the best,
    Andrei.

    Hello @topher1kenobe,

    Try deactivating all of your plugins to explore whether any could be responsible. If it doesn’t resolve your issue then switch to the Twenty Seventeen theme to check whether it’s an issue with the theme or something else.

    Also, make sure you are using PHP version greater than 5.6.

    Let me know if you succeed – I’m happy to help.

    Richard

    (@richardcoffee)

    @baicusandrei, it may be a theme related issue, since in my case changing to a wordpress theme made it go away. This without deactivating any plugins.

    Thanks for the advice @poonam9, but I’m afraid it didn’t really help that much.
    The url was correct after changing themes to twenty-seventeen, but this does nothing toward fixing the theme I wish to use.

    What I would like to know is how to track this down, in the code, so that I can stop it from happening. Now when I say code, I mean the wordpress core code, not the theme code. I do not expect you to find the issue, just point me toward a place to start, and I’ll take it from there. When I figure what core is doing with it, then I will be better able to figure out how the theme is interacting with core to cause the problem.

    Oh, I can confirm that the php version is not a factor in this issue.

    Will post here if I can find a solution, or at least a reasonable compromise.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Customizer variables left in the URL’ is closed to new replies.