[Resolved] how-to / best practise / cheat sheet for updating GeneratePress

Home Forums Support [Resolved] how-to / best practise / cheat sheet for updating GeneratePress

Home Forums Support how-to / best practise / cheat sheet for updating GeneratePress

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #1115925
    th

    Dear Support,
    I am running WordPress 5.2.5 / GP Premium 1.9.1 / GeneratePress 2.2.2
    I want to update to latest version 2.4.1
    As this will be my 1st update of my production website I wonder if there is a
    how-to / best practise / cheat sheet
    how-to do. This one here https://docs.generatepress.com/article/updating-generatepress/
    does not help to much.
    I would like to know which items to check, which data to save (apart from a WP installation file and DB backup), which settings to document. I am running GeneratePress pretty simple, only used the Customizer. I am neither aware of any own coding nor of modifying theme which would rquire a child theme creation. But I am not sure what Customizer did or did not. That’s why i want to gain some security by follwoing a kind of ‘how-to’ to minimize any risk.
    Thanks for your help in advance.
    Kind regards,
    Thilo

    #1116216
    Leo
    Staff
    Customer Support

    Hi there,

    There really isn’t anything you need to worry about during updating.

    GP Premium 1.9.1 has been released for awhile now so it’s really stable.

    All your customizer options will be saved during updating. If you haven’t modified any of the theme’s core file then you won’t notice any changes to your site after the update is done.

    We pay a lot of attention to backward compatibility.

    Let me know if this helps ๐Ÿ™‚

    #1117274
    th

    Dear Leo,
    thanks for helping – update worked fine!
    Kind regards,
    Thilo

    #1117275
    th

    status changed to “resolved”

    #1118028
    Leo
    Staff
    Customer Support

    No problem ๐Ÿ™‚

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.