This article explains why we decided to build a BackWPup restore stand-alone app besides to an integration into BackWPup. We discussed this in our team and finally settled with this decision because of vary reasons.
-
Se cubre el peor de los casos
Imagine the worst-case: Your WordPress site does not show anything. We call that “White-Screen of Death”. If your not able to log in to see the backend, you’re not able to use a restore feature within BackWPup. Using a stand-alone app can help in this situation.
-
Es más fácil desarrollar una función nueva de este tipo
Esta es nuestra primera vez que intentamos crear una función de restauración y estamos tan emocionados como vosotros. Sin embargo, desarrollar una función tan nueva no siempre es fácil. Utilizar una aplicación independiente al principio nos ayuda a familiarizarnos con el tema y a detectar los posibles problemas.
-
Separar la lógica de la vista
Ok, let me explain that. We build this stand-alone app in such a way, that we can reuse parts of it later in BackWPup Pro. So that means, the code, which is responsible for restoring a backup is not only build for this app but also for the plugin later. So we won’t have to rebuild everything in the near future when integrating it into BackWPup. We decouple the part, which handles the restoration from the part, which shows the GUI (Graphical User Interface) in browsers.
