Clean destination before import

  • Resolved rogeriodec

    (@rogeriodec)


    8 years, 2 months ago

    I use this plugin for a sandbox version of my current site. So, every time I want to do a test, I export the entire official website and import it into the sandbox site.
    But I have noticed that this plugin DOES NOT DELETE the existing files in the target site, ie if for example I have a previous copy in the sandbox with 10 plugins I export a new version of the official website, in which I have removed for example 3 of these plugins , when I import, the old plugins continue in the sandbox folders. So, these plugins reappear (although disabled) in the list of plugins in the sandbox.
    The same occurs with images and other files that have been previously deleted on the original site, still appear on the target site.
    I was wondering if there is how to configure this plugin so that it completely CLEAN the target site before importing a new version?

Viewing 5 replies - 1 through 5 (of 5 total)
  • lesleysm

    (@lesleysm)

    8 years, 2 months ago

    @rogeriodec

    In the past the plugin used to delete all content on a website before install. We had many customers that wanted to have certain aspects of the site remain whilst others were replaced. As it has become so much easier to create a clean WordPress install we moved to this model.

    If you need a clean target, please ensure that you have a clean install before migrating.

    Thread Starter rogeriodec

    (@rogeriodec)

    8 years, 2 months ago

    I understand that for a first migration, the current model works. But you have noticed that there are situations like mine, where the migration occurs repeatedly to the same place, where in fact I want a “mirror” of the original site and do not want to keep anything that already existed before in the destination site.
    So, it would be very simple for you to put an additional option before the moment of importing: if the user wants the target files to be kept or deleted. You can leave it as standard as it is today, that is, be kept. But that gives the option of choice to the user. Hence, the responsibility lies with the user.

    Plugin Author Yani

    (@yaniiliev)

    8 years, 2 months ago

    @rogeriodec
    Yes, allowing the user to select what to do is the best way.
    We decided to switch our approach from cleaning to keeping based on the number of requests and how easy it is to install a new WordPress nowadays.

    tdechangy

    (@tdechangy)

    8 years, 1 month ago

    Sad to hear that to! I use this plugin to update my websites after local tests which is certainly an even popular use case. Now it makes the task so cumbersome that it makes me crazy to lose so much time for … nothing.

    Now I tried a quick reset of my website using a plugin it even crached it down. You imagine how happy i am.

    Please consider allowing BOTH PTIONS at import stage !
    As suggested before this shouldn’t be so hard since it’s just a question of deleting files or not, just as it existed previously.

    I hope you’ll give this approach a second chance for the sake of our pace.

    • This reply was modified 8 years, 1 month ago by tdechangy.
    Plugin Author Yani

    (@yaniiliev)

    8 years, 1 month ago

    @tdechangy @rogeriodec

    We’ve created a new website to track user’s feedback: https://feedback.servmask.com
    It will help us prioritize all features of the plugin. Voice your opinion there to make it happen.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Clean destination before import’ is closed to new replies.