Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter cowfish

    (@cowfish)

    Finally resolved this myself – ta muchly to the Sitegrounds for supplying the plugin, fixing the automatic transfer got me back to understanding my site better, and what terrible things I’ve done to it over the past decade ??

    Fixes I’ve done over the past few months while occasionally tinkering with it (I have no urgent need to move, and relying on a clean WP build to fix many of my issues that I have now fixed was one reason…):
    * Fixed permissions – 644 for files, 755 for directories. Everything now owned by appropriate users.
    * Checked what was in my database and cleaned up a load of tables that were left behind by badly behaved plugins. This was the final problem, as I had a huge database table that the autoupdated kept trying and failing to save. It would dump out up to about 650mb, pause, delete it and then try again. I binned the table (and a bunch of other dead things) and the migrator worked perfectly.

    Ta muchly folks. Thanks for resolving it when it wasn’t resolved, though…

    Thread Starter cowfish

    (@cowfish)

    No resolution yet – they seem to check these threads every month or so ??

    I deleted everything to start again, and now it doesn’t make the tars…

    Thread Starter cowfish

    (@cowfish)

    Thanks for looking into this for me.

    The permissions on the upload folder seem to be fine –?it’s tarred everything up ready to transfer, but not created a manifest:

    billy:[…]/wp-content/uploads/1575502167-[a load of chars]$ ls
    plugins sql themes

    billy:[…]/uploads/1575502167-[a load of chars]$ du
    143016 ./plugins
    23160 ./themes
    724916 ./sql
    891096 .

    I can also download the files themselves using a direct link without any problem.

    Do you have a sample manifest file? I can make one manually if there’s something stopping it from being created.

    Thread Starter cowfish

    (@cowfish)

    Further testing:

    Broadcasting solely to Facebook, rather than both FB and twitter, seems to fix the problem. I’ll keep prodding when I publish future posts (unfortunately I don’t have a testbed blog setup at the moment to be able to give more useful bug reports).

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