Archive Extractor

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

    (@yaniiliev)

    8 years, 4 months ago

    @antonyjosephsmith

    There is https://traktor.servmask.com that lets you see what files are inside the archive.

    The extractor is part of the plugin – when you import a backup, the files are extracted from the archive.

    We don’t have any plans to allow editing files inside the archive for now – we think it will create more trouble than good for quite a large number of our users.

    Do you have a specific use case to share with us?

    Thread Starter antonyjosephsmith

    (@antonyjosephsmith)

    8 years, 4 months ago

    Yeah I’ve got a 19GB archive of a site that seems to have been installed on an older version of WordPress, I could do with extracting and viewing the untouched sql database so I can check some parameters and the wp version to make sure I can match the WP Version as currently a straight import into 4.9.2 failed on my first two attempt and shifting a 19GB archive round isn’t fun. Plus it’s of dubious origin and may be infected with malware so I would have ideally liked to perform a scan of all the files before running it – which I can’t while it’s archived.

    I find it bizarre you ask for use cases yet make a tool, Traktor, which to all intents and purposes is pretty much useless, it shows me a file structure and that’s it, I really cannot see any use case for it at all. What do you guys consider are use cases for it?

    If you’ve no intention of adding this functionality or at least creating even an unsupported tool on github so only the savvy can use it, then I’m just going to use an alternative.

    Plugin Author Yani

    (@yaniiliev)

    8 years, 4 months ago

    Yes, knowing the WordPress version is important. We are making a few changes in the plugin that will try to address better the compatibility between different WordPress versions.

    What error message do you get when you import on the latest version of WordPress? You can turn on debugging with https://codex.ww.wp.xz.cn/Debugging_in_WordPress

    To find the WordPress version, you can use the head command on the archive. Here is an example:

    head -c9000 migration-20180101-223541-606.wpress
package.json1811476311743.{"SiteURL":"http:\/\/migration","HomeURL":"http:\/\/migration","Plugin":{"Version":"6.62"},"WordPress":{"Version":"4.0.12","Content":"\/var\/www\/wp-content"}}

    What this will tell you is that the backup is from http://migration. It was exported with All-in-One WP Migration version 6.62 from WordPress version 4.0.12.

    There is a Go library on GitHub that one can use to work with a WPRESS archive: https://github.com/yani-/wpress

    • This reply was modified 8 years, 4 months ago by Yani. Reason: fixing a typo
    Thread Starter antonyjosephsmith

    (@antonyjosephsmith)

    8 years, 4 months ago

    I’ve tried running the Go library without success, I’ve also tried this fork https://github.com/fifthsegment/Wpress-Extractor however I get a fatal error every time and only a partially extracted archive.

    Yeah I’m familiar with wp debugging but what would be really helpful is if I could just extract the damn archive. Plus none of your suggestions offer a solution to scan for any malware.

    Anyway, you clearly don’t want to do it for reasons which are really quite unclear so I’m just going to look at alternatives.

    Antony

    Plugin Author Yani

    (@yaniiliev)

    8 years, 4 months ago

    Thank you for your feedback.

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

The topic ‘Archive Extractor’ is closed to new replies.