How to handle screenshots when pushing changes?

  • Resolved Neven Jevti?

    (@nevenjevtic)


    3 months ago

    Oftentimes with our clients, we make changes on staging and push to production automatically using a sync tool (host, import/export). This is due to override the database, where tests seem to be saved.

    Is there a way to keep the tests for after the push is made and compare bost versions?
    Perhaps saving them to cloud or having exportable config.

Viewing 1 replies (of 1 total)
  • Plugin Support steffenbew

    (@steffenbew)

    Hey, the VRTs Tests and Alerts are saved in separate tables.

    That’s why it should be possible to keep the tests on production, by doing the following:

    1. Sync the VRTs options to staging (SELECT * FROM wp_options WHERE option_name LIKE ‘vrts_%’).
    2. Exclude the VRTs tables from syncing to production: vrts_alerts, vrts_tests.

    That way, you would prevent Tests getting overwritten on production, ensure that VRTs options are retained, and get comparisons of before and after push states.

    Syncing the options back to staging only has to be done whenever plugin settings (notification email, click element, license key) are changed.

    Does your migration tool support excluding tables?

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.