Support » Plugin: All-in-One WP Migration » Like many other, suddenly unable to restore a backup

  • Resolved messanoir


    Like many others on here, I found myself in the position to need to restore from a backup, and finding that I would either have to pay, or download an extension from an outside, un-trusted source. I have chosen to post this here, rather than as a review, to because I would prefer to get some answers before cementing my opinion of the developer and the plugin. I sometimes have the tendency to be a little wordy, so I apologize if this is a bit long winded me trying to get all my thoughts out and straight.

    We all get and use backup software, for the same reason I imagine…in case something bad happens. We don’t get them with the intention of backing up and restoring every day, or week, or month. We get them in the hopes we never need them, but keep them just in case we do. That’s where this plugin up till now was amazing, easy to do backups, automatic server-side file saved, and we knew if needed to, restoring was just as easy.
    Now while I know you probably had a very good business reason for making the changes you have (at least I hope so, and at the moment will give the benefit of the doubt in assuming so) there should have been an announcement to all current users of the impending change, rather than only finding out after it was too late. that aside, here is what I do not understand, and from what I have been able to find, has not been clearly explained…

    Why is the import extension to compensate for this placed outside the repo? I know you have mentioned that the plugin develper(programmer, designer, i’m not sure, sorry, we’ll just go with whoever is in charge of it) didn’t want it on the repo…which you have to admit, not only sounds odd, but can come across as very suspicious to the average person. The whole reason people submit to the repository is that WordPress can check it, say it’s clean and good, and put it out in front of hundreds of thousands of people. Now if this was a paid extension, then yes, I could understand, as they are not allowed on the repository, but this plugin extension, as you have stated on various occasions, is free.
    Ok, so maybe the code is proprietary for whatever reason, hence not eligible to be on the repo…but you have mentioned in other answers that it’s open source….so again..why an outside source? Submitting a free plugin to the repo can only improve ones reputation and brand as long as the plugin is good (which the original was, it was amazing, as thousands of people and good reviews should show you). People know that if it is on the repo, they can at least trust that it wont directly harm their setup, or compromise their installation in some way. I have nothing against developers changing or adding to plugins things that are a paid service, you have to make money to keep working, and it’s just good business. But this isn’ have subtracted features, crippling the product, and then asking people to “trust you” over the WordPress repo, that your extension is safe. Really only two things can be derived from this…one, you are banking on people being leary of the extension, thus they buy the full version (most people in the situation we find ourselves in having relied on the earlier version and thus, have no other backups available, so having to stick with the product in some form), or two…whoever was in charge of making the decision to do things this way, has very little sense of good business decisions, and sadly everyone else involved just went along with it instead of saying “whoah..this is going to bad for us, and make us look really bad and shady”…which it what an action like this so clearly would, and unfortunately does.

    I would have probably ignored all this, except that of course I encountered the same issue as others. Had my site crash, needed to restore and whoops…can’t. I prefer not to download plugins from un-trusted sources, so I wasn’t going to get the extension, and certainly was not going to pay, after reading not just the issues others were having, but the way some of them were being responded to in either vaguely hidden patronizing ways, or condescendingly or arrogantly. I decided to do what I knew I could, which is go and download a previous version from the repo…something that as developer you should know is always accessable and available..the repo always keeps previous versions just in case people are running older versions of wordpress. I bring this up as in a few of the reviews and support tickets I read, the individual answering the questions kept saying that the older version was not available when asked about it. Only then to warn about using older versions when someone posted a link or informed others where it could be found. I get that there would be some bugs, and some fixes missing…but these were ones that people were already either aware of or had worked around or found a way to deal with before this update came out, so to be honest, the warning of missing bug fixes is kind of irrelevant.

    Again, so sorry for being wordy, as you can tell I had a lot to get out, but basically it boils down to asking you to give clear concise answers to the questions everyone is asking…why was this change made? Why is the only free option to counter it placed outside the trusted source of plugins?

    Thanks for your time, and letting me rant a bit..

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Yani Iliev



    Why is the import extension to compensate for this placed outside the repo?

    – There are plugin guidelines that every plugin author has to abide by in order to host a plugin on plugin repository. The uploader code does not comply with the guidelines of the repo so we had to move it outside of the repo and host it on our own website as a separate extension. Here are the plugin guidelines if you would like to learn more about them.

    I prefer not to download plugins from un-trusted sources, so I wasn’t going to get the extension, and certainly was not going to pay, after reading not just the issues others were having, but the way some of them were being responded to in either vaguely hidden patronizing ways, or condescendingly or arrogantly.

    – I and the team answer every question with the idea to resolve the issue on the topic posted. If this comes out patronizing, condescending, or arrogant, I am sorry for it – it was not the goal nor the intention of the reply. Regarding the security of plugins outside repo – I am not sure if we are allowed to discuss plugins outside – you should make yourself familiar with your rights and responsibilities on the Internet – privacy policy, acceptable use policy, terms of use, and so on. Once you have read this information, you will know what a software does, what information if any it collects from you, does it share your information with anyone, and so on. All our websites and products include this required information.

    the warning of missing bug fixes is kind of irrelevant.

    – As a vendor of this plugin, it is my responsibility to warn you that older versions of the plugin have bugs and I cannot guarantee successful transfer/restore of your website, or provide support when you use an outdated version of the plugin.



    I appreciate your concise response, though if I may, I would like to rephrase my question, taking into account your answer provided. So the plug-in doesn’t meet WordPresses guidelines for being listed on the repo…why is that? What guidelines does it fail to meet? It doesn’t help with the trust value when information about the plug-in isn’t shared.

    That’s what I mean when I say it’s hard to trust, as WordPress’s guidelines are in place to not only promote open source, and a overall free and fair market for all, but a place of safety, if I may use that term. People using the repo know that the plugins and most of the time the distributors, have been vetted for the repo, and be used safely without harm or danger.

    As for discussing the plug-in on this site, well, you feel comfortable with linking to, mentioning and yes, promoting when able, the plug-in, so you open yourself to discussing it. If you would prefer not to, that’s perfectly fine, but then dont advertise and link to it either. Perhaps not the best solution for you, I know, but then you chose to move the plug-in off site to begin with.

    I noticed as well that you avoided the section regarding notifing users of such a drastic change in what had become for many, a much required and depended on plug-in. If you choose not to, that’s fine, though I am still.curious as to what the reasoning behind that actuin was. You had to know the effect that would have, people running the update, as we are all essentially trained by the software to do, only to find it essentially non functional and telling us us if we want to use it, go outside our trusted comfort zone or pay. Would have really been so hard to simply put out a minor update that did nothing but tell people of the upcoming change? I mean I’ve written code that produce a simple message box notification in less than an hour, and you guys are pros at this, could it be that hard?

    Thank you for giving me the opportunity to respond.



    I think the issues raised here are quite valid. After using the plugin for years, without warning I’m suddenly told “Import from file is available via a free extension. Download it here”. I was alarmed enough to come here to find out what’s going on.
    Naturally it raises suspicions, especially since it’s not mentioned in the main info about the plugin.
    Why has the change taken place? I have no objections to this as such – if this is the way we have to get the plugin and it’s legitimate then fine, but I do think that you ought to warn users (old and new) of the new policy.
    The outcome is that after trusting the plugin for so long I’m wary of future developments. An explanation isn’t an unreasonable request.
    This is a shame because it is such a good plugin.

    Plugin Author Yani Iliev


    The plugin can do much better in explaining the upcoming changes to its users. We used the changelog until now because that’s what we thought our users were using to see the changes between releases. I now understand that not everyone knows what a changelog is, where to find it and how to use it.
    We make a change – we see what users say about it – we learn and improve.
    The changelog can be seen here:

    Going forward – importing from a file will be using whatever the server supports – it ranges from 2MB up to 256MB. Larger uploads will be possible by adjusting server settings and changing max upload file size. I did not want our users to have to deal with this and set a file restriction of 512MB (twice the size of what is available on most hosting providers and plans) – it turned out that this restriction is not allowed on plugin repository and I had to remove it.

    Restoring a backup will be done by first downloading it, then importing it from a file.

    Plugin Author Yani Iliev


Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Like many other, suddenly unable to restore a backup’ is closed to new replies.