Don't know any guide, sorry. I'm just a dev who had to figure out all of that because of the same reasons.
There's no file removing needed. What I would do is once you get a copy installed (such as 1.6) do a string search for curl and/or file_get_contents. That'll quickly bring up any outside calls which you can then investigate. The advertising ones are protected so you just have to edit the core file it's in and do a return.
Also, there's a fork of 1.6 called thirtybees : https://thirtybees.com/
Highly recommend you go with that over Prestashop. Not only are there performance problems with actual Prestashop, there's also security issues which are fixed in 30bees.
This should on /r/webmaster or something.
Anyway, you should have access to your CPANEL (or any other kind of hosting administration). From there, you should have something like a File Manager, where you could zip your entire files and download it.
While there are other ways (SSH, i think, but needs config), you could also upload or make a php script with shell-exec or exec where you zip your site to a location and download it. Afterwards, use the same functions to delete it.
That is, assuming that you have proper permissions to edit the hosting files, but no FTP access.
Just to add: thirtybees can be migrated to from 1.7 now, thanks to them joining up with Cart2Cart (not an advertisement, it's just a good service) - https://thirtybees.com/migrate/prestashop-1-7-thirty-bees/
You can actually select any number of different CMS and choose the things you want transferred to your CMS of choice and they'll do it for you.
Side note: Personally I'm using WooCommerce for a few projects as well, and it's just as scalable for large numbers of products. Personal preference at the end of the day. thirtybees would definitely be my goto choice if the option was PrestaShop or thirtybees though.
Frustrated with Prestashop and unhappy with the direction they are going with 1.7? Come check out Thirty Bees, a fork of Prestashop 1.6. Development is moving at a very rapid pace and IMO in the right directions.
Buenas gente, he tenido el mismo problema y he podido encontrar solución. El problema se encuentra que una vez logeados en el modulo de Mailchimp en Prestashop este no recoge la Api y se queda en blanco, lo que tenemos que hacer es indicarsela de forma manual.
Lo primero es a través del modulo intentar logearse, nos devolverá a la pantalla de prestashop como si nada hubiese pasado. Pero realmente ha creado una clave API en Mailchimp. Tenemos que localizarla y tenerla a mano. La podemos encontrar en la pagina de Mailchimp.com iriamos a nuestro usuario > Profile > Extras > API Key, le damos a "create a KEY" y aqui la tendremos. (Como observación debajo del todo tiene que aparecer que prestashop esta autorizada, sino esta deberéis de ir al modulo en nuestra tienda e intentar el logeo.)
El siguiente paso requiere modificar un archivo TPL que estara en la siguiente ruta ..>Modules> mailchimppro>views>template>admin>wizard> step-1.tpl abrimos este archivo y aproximadamente en la fila 21 tenéis esto:
<input type="hidden" class="form-control" name="api-key" id="api-key"
lo sustituimos por:
<input type="display" class="form-control" name="api-key" id="api-key"
Lo que conseguimos con esto es habilitar el campo donde tenemos que introducir la KEY
Espero que haya sido util