benbalter / wordpress-to-jekyll-exporter Goto Github PK

hey

just so you know, plugin is giving me an error the moment I try to activate it. I'm with WP 4.0.1 on godaddy (not sure what php they have)

this is what I have

Plugin could not be activated because it triggered a fatal error.

Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING or '(' in /home/content/i/a/m/iamadroid/html/tom/wp-content/plugins/jekyll-exporter/jekyll-exporter.php on line 27

When exporting my Wordpress blog, <iframe> tags disappeared (even though the <div>s and <p>s around them were generated.

This affected mostly Youtube, SlideShare and likewise embeded posts. Since I only had a few, I fixed them manually by copying from the old posts, but it might be desired to copy those tags.

Btw, this plugin is awesome - it was able to cope with > 14 years of bad HTML from my blog, and I deeply appreciate the effort put into it.

Once the plugin is installed, I'm unable to activate it. My wordpress installation (4.0.1) communicates a fatal error:

Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING or '(' in /home/ttybhpmk/public_html/wp-content/plugins/jekyll-exporter/jekyll-exporter.php on line 27

I am trying to use your plugin to export my current site to Jekyll. I first installed via the Wordpress install in my admin (via the plugins site). I encountered the following issue, deactivated and deleted the plugin and then did a manual download, upload and install. I am getting the same issue either way. Any ideas? I am sure it has to do with some quirk with my hosting at ipage.

Output error====
File not found
Firefox can't find the file at http://johnyux.com/wp-admin/export.php?type=jekyll.

I've a bunch of <iframe> tags with youtube and vimeo videos. They are all lost in exported .md files. How can I work around that?

I've tried again since the update and am getting the following:

Fatal error: Call to undefined function Alchemy\Zippy\mb_strtolower() in /home/…/public_html/blog/wp-content/plugins/wordpress-to-jekyll-exporter-master/vendor/alchemy/zippy/src/Alchemy/Zippy/Zippy.php on line 189

I'm on Wordpress 4.1.1

Just tried to activate this for the first time on a WP 3.8 install.

Parse error: syntax error, unexpected T_STRING in /blog/wp-content/plugins/wordpress-to-jekyll-exporter-master/jekyll-export.php on line 164

Not sure if you all are still developing this, but figured I would give you a heads up.

Also, version number in docs does not match version description in header (1.4 vs 1.3)

Using WordPress 3.4.1 with freshly downloaded and installed copy of this plugin gets a few dozen instances of the second line below

Warning: buffer was not flushed, this is a bug. please report! in /users/home/blazar/web/public/wp-content/plugins/benbalter-wordpress-to-jekyll-exporter-a522b2b/includes/markdownify/markdownify.php on line 330

Warning: call_user_func(Markdownify::flushStacked_ul) [function.call-user-func]: First argument is expected to be a valid callback in /users/home/blazar/web/public/wp-content/plugins/benbalter-wordpress-to-jekyll-exporter-a522b2b/includes/markdownify/markdownify.php on line 392

Then a similar number of this error:

Warning: copy(/var/tmp//wp-jekyll-573e378d0d3b63438d0f4822e0a7b0c3/wp-content/uploads/2010/07/joe-cole-1st-training-lfc-150x150.jpg) [function.copy]: failed to open stream: Permission denied in /users/home/blazar/web/public/wp-content/plugins/benbalter-wordpress-to-jekyll-exporter-a522b2b/jekyll-export.php on line 392

Finally the remaining errors:

Warning: mkdir() [function.mkdir]: Permission denied in /users/home/blazar/web/public/wp-content/plugins/benbalter-wordpress-to-jekyll-exporter-a522b2b/jekyll-export.php on line 397

Warning: Cannot modify header information - headers already sent by (output started at /users/home/blazar/web/public/wp-content/plugins/benbalter-wordpress-to-jekyll-exporter-a522b2b/includes/markdownify/markdownify.php:392) in /users/home/blazar/web/public/wp-content/plugins/benbalter-wordpress-to-jekyll-exporter-a522b2b/jekyll-export.php on line 315

Warning: filesize() [function.filesize]: stat failed for /var/tmp//wp-jekyll.zip in /users/home/blazar/web/public/wp-content/plugins/benbalter-wordpress-to-jekyll-exporter-a522b2b/jekyll-export.php on line 317

Warning: Cannot modify header information - headers already sent by (output started at /users/home/blazar/web/public/wp-content/plugins/benbalter-wordpress-to-jekyll-exporter-a522b2b/includes/markdownify/markdownify.php:392) in /users/home/blazar/web/public/wp-content/plugins/benbalter-wordpress-to-jekyll-exporter-a522b2b/jekyll-export.php on line 317

Warning: readfile(/var/tmp//wp-jekyll.zip) [function.readfile]: failed to open stream: No such file or directory in /users/home/blazar/web/public/wp-content/plugins/benbalter-wordpress-to-jekyll-exporter-a522b2b/jekyll-export.php on line 320

Warning: unlink(/var/tmp//wp-jekyll.zip) [function.unlink]: No such file or directory in /users/home/blazar/web/public/wp-content/plugins/benbalter-wordpress-to-jekyll-exporter-a522b2b/jekyll-export.php on line 331

Hi, I am trying to export all my post, pages and uploads to jekyll but with no luck. The wp-content directory is empty.

I've tried with both wp-cli and php jekyll-export-cli.php > jekyll-export.zip. As I have a custom wordpress structure, I thought that wp-cli will solve the problem, but it didn't.

The first error that I've encounter with wp-cli was that it can not find jekyll-export as a command. So I downloaded the plugin to ~/.wp-cli as explained here https://github.com/wp-cli/wp-cli/wiki/Community-Packages

After that, the plugin was able to run, but with errors like:

PHP Fatal error: Cannot redeclare cli\render() 

After commenting all the function redeclared, I keep getting things like:

Cannot redeclare class Spyc in

I do not know what more I can do to be able to download the contents of wp-content.

Is worth mentioning that I have a custom wordpress structure, like this:

.
├── content
├── index.php
├── robots.txt
├── wordpress
└── wp-config.php

So I modified the file jekyll-export-cli to

include "../../../wordpress/wp-load.php";
include "../../../wordpress/wp-admin/includes/file.php";

Hope you can help me. Regards

When opening a file converted by wordpress-to-jekyll-exporter in Coda, I get "The file has mixed line endings. Do you want to convert all line endings to LF, the most common line ending in the file?"

Via @marteaurouge over in benbalter/feedback#11:

Thanks for your work on the plugin!

Do you think it is possible to add the ability to choose a month range (like the regular xml exporter) ?

Using the plugin is tricky with huge wordpress sites (tried in cli mode, but it didn't work).

I already left a comment on a403c1e and I think it should be reverted.

When I tried exporting a site with a mere 250+ posts, the script timed out. When I used an earlier revision that didn't use that site, it finished almost instantly.

I think it's better to leave the content as HTML, if there are parser errors (as I've done in scribu@d6f1d71), than to make the script rely on a third-party service that's inherently slow to access and might go away at any time.

Not sure if this is any priority but I had wp_debug on for local dev and that breaks the output.

Cool plugin, thanks Ben :)

Parse error: syntax error, unexpected T_STRING in ...wp-content/plugins/wordpress-to-jekyll-exporter-master/jekyll-export.php on line 164

line 164: $converter = new Markdownify\ConverterExtra;

Nothing appears to happen for wordpress 2.8.4...

When I start the plugin, it raised this~

Unless I misunderstand something, custom post types (set up via a custom post type plugin) don't get included in an export, no matter what I try. Is this missing, or am I missing it? Custom post types are very common.

Would be nice to include these in some form in the export.

I have installed this as a plugin to export to Jekyll and I am getting the following error:

Fatal error: Uncaught exception 'Symfony\Component\Process\Exception\RuntimeException' with message 'The Process class relies on proc_open, which is not available on your PHP installation.' in /home/neus/public_html/wp-content/plugins/jekyll-exporter/vendor/symfony/process/Symfony/Component/Process/Process.php:148 Stack trace: #0 /home/neus/public_html/wp-content/plugins/jekyll-exporter/vendor/symfony/process/Symfony/Component/Process/ProcessBuilder.php(279): Symfony\Component\Process\Process->__construct(''/usr/bin/unzip...', NULL, Array, NULL, NULL, Array) #1 /home/neus/public_html/wp-content/plugins/jekyll-exporter/vendor/alchemy/zippy/src/Alchemy/Zippy/Adapter/VersionProbe/ZipVersionProbe.php(72): Symfony\Component\Process\ProcessBuilder->getProcess() #2 /home/neus/public_html/wp-content/plugins/jekyll-exporter/vendor/alchemy/zippy/src/Alchemy/Zippy/Adapter/AbstractAdapter.php(142): Alchemy\Zippy\Adapter\VersionProbe\ZipVersionProbe->getStatus() #3 /home/neus/public_html/wp-content/plugins/jekyll-exporter/vendor/alche in /home/neus/public_html/wp-content/plugins/jekyll-exporter/vendor/symfony/process/Symfony/Component/Process/Process.php on line 148

The installation docs recommend PHP >5.3 - is this still the case?

Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING or '(' in D:\HostingSpaces***********\wwwroot\wp-content\plugins\wordpress-to-jekyll-exporter-master\jekyll-exporter.php on line 32
PHP Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING or '(' in D:\HostingSpaces***********\wwwroot\wp-content\plugins\wordpress-to-jekyll-exporter-master\jekyll-exporter.php on line 32

One of my Wordpress blogs is 100% pages and 0% posts. Most pages have parent pages and many of these subpages have the same name. For example:

http://teaching.danaernst.com/mat220s15/syllabus/
http://teaching.danaernst.com/mat220s15/syllabus/

However, only one page named syllabus was exported.

fails with this message:

Plugin could not be activated because it triggered a fatal error.

Currently the CLI script allows anyone publicly to run the export and potentially overload the server. The CLI script should check for php_sapi_name() before continuing.

I can not export anything, it gives me a server error and nothing happens.. Any ideas?

--HTTP Error 500 (Internal Server Error): An unexpected condition was encountered while the server was attempting to fulfil the request.

I am migrating http://www.seitad.com to http://danieltakeshi.github.io/ and used this tool to help out in the process. I seem to have gotten all my old posts converted to markdown. However, when I pushed the updates to my github page, I found that clicking on the links to each blog post just led me back to the homepage.

I later realized it was a problem with permlinks. With my wordpress.org site, the blog posts were of the form:

http://www.seitad.com/?p=2391

with the "2391" being replaced by various numbers to indicate different blog posts. This tool preserved the "?p=2391" part and put this in the header of the markdown files. I later figured out that by deleting that line for a single post, I could get the permalinks working as intended because it defaults to the /year/month/day format.

I'm just wondering if this is an intended issue because otherwise I will need to delete all the permalink lines in my posts. This is not a big deal, of course, but I'm also wondering if: (a) there is another way to get permalinks working, perhaps by modifying the "permalink" variable in the _config.yml, and (b) if this will affect future comment migration via Discus (though I understand this is not a Discus-related thing). Thanks.

Hi, I am on Wordpress version 3.5. This is the error I got.

Warning: mkdir() [function.mkdir]: Permission denied in /home/content/.../wpcontent/plugins/wordpress-to-jekyll-exporter-master/jekyll-export.php on line 401

Hey there. I'm a WP dev and I'm trying to expand my toolkit and also think about site performance...this led me to trying your plugin/CLI and thinking about integrating it into some sort of build script or deploy sequence or something. Anyway...a big part of what I focus on is the admin section of WP and, to that end, I use the ACF plugin and custom post types on most of my sites. Out of the box, this plugin doesn't support ACF...it outputs all the custom fields as converted meta in YAML (I think...I dug around your code a bit) and I can't begin to think how to capture the output.

Are you familiar with ACF and/or handling custom fields within templates? I see that you're ignoring certain meta fields which makes me think that somewhere around those lines in the code, it could detect whether the meta is an Advanced Custom Field (based on the post_type column) and save them for output later or something.

It'd be really great to hear your thoughts of how a site using custom fields and custom templates could output as markdown or at least static HTML files. Thanks in advance!

T_STRING, expecting T_CONSTANT_ENCAPSED_STRING - Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING - on line 32 jekyll-exporter.php

I tried this plugin yesterday, after some wrestling around with it (mostly with my Wordpress/PHP stack) I got it to work. However it fails to convert html to markdown. The html is extremely sloppy with a lot of inline styling and legacy stuff from different plugins (youtube plugins, and code highlighting.)

I noticed the export plugin likes to place all the links at the bottom and then reference them using the markdown bracket syntax:

[Some link][1] and some text 
....rest of the blog post....
[1]: http://example.org

I can appreciate it trying t consolidate links, but this totally breaks using {{ post.excerpt }} since the links aren't available in the except. I'm going to look into this, but I thought I'd post an issue here first.

I think the solution needs to be an option to inline the links instead of separating them.

wordpress-to-jekyll-exporter seems to export long permalinks using YAML's multi-line text syntax in the exported .md:

permalink: >
  /some/long/permalink/path/goes/here/yo/dawg/i/heard/you/liked/long/permalinks

I fixed this by manually changing the permalink to be on a single line:

permalink: /some/long/permalink/path/goes/here/yo/dawg/i/heard/you/liked/long/permalinks

Be nice if wp-to-jekyll-exporter dealt with this for me :)

I've deleted all plugins and before trying and and only see a blank page.
host: wpengine
plugin version: 2.01

Hi Ben,

are <div class="wp_syntax"> blocks (http://wp-syntax.com/) supposed to be exported correctly as well (I use quite a lot of GeShi on my http://blog.mro.name/) or would you recommend a post-processing step to get this ready for pygments.rb (http://clarkdave.net/2013/03/syntax-highlighting-in-nanoc/)?

Cheers,
Marcus

Getting such warnings:

 $ jekyll build
Configuration file: /home/krieger/jekyll/jekyll-export/_config.yml
            Source: /home/krieger/jekyll/jekyll-export
       Destination: /home/krieger/jekyll/jekyll-export/_site
      Generating... 
     Build Warning: Layout 'post' requested in _posts/2013-06-24-initial-post.md does not exist.
     Build Warning: Layout 'post' requested in _posts/2013-06-25-whdd-2-0rc2.md does not exist.
     Build Warning: Layout 'post' requested in _posts/2013-06-26-humor-whdd-implemented-in-bash.md does not exist.
     Build Warning: Layout 'post' requested in _posts/2013-06-28-sticky-post.md does not exist.
     Build Warning: Layout 'post' requested in _posts/2013-06-29-whdd-2-0.md does not exist.
     Build Warning: Layout 'post' requested in _posts/2013-07-01-whdd-2-0-1.md does not exist.
     Build Warning: Layout 'post' requested in _posts/2013-07-03-new-demo-whdd-read-test-explained.md does not exist.
     Build Warning: Layout 'post' requested in _posts/2013-08-21-whdd-2-1.md does not exist.
     Build Warning: Layout 'post' requested in _posts/2013-08-29-new-demo-copying-with-skipfail-strategy.md does not exist.
     Build Warning: Layout 'post' requested in _posts/2013-08-29-new-demo-copying-with-skipfail_noreverse-strategy.md does not exist.
     Build Warning: Layout 'post' requested in _posts/2014-08-03-whdd-2-2.md does not exist.
     Build Warning: Layout 'page' requested in get-it/index.md does not exist.
     Build Warning: Layout 'page' requested in press/index.md does not exist.
     Build Warning: Layout 'page' requested in report-issue/index.md does not exist.
     Build Warning: Layout 'page' requested in contact/index.md does not exist.
     Build Warning: Layout 'page' requested in demo/index.md does not exist.
                    done.
 Auto-regeneration: disabled. Use --watch to enable.

Used git revision 0c60021

I cannot export from Wordpress using the CLI tools:

[root@shrine thefallenphoenixnet]# php wp-content/plugins/jekyll-exporter/jekyll-export-cli.php > jekyll-export.zip
PHP Warning:  include(../../../wp-load.php): failed to open stream: No such file or directory in /var/www/thefallenphoenixnet/wp-content/plugins/jekyll-exporter/jekyll-export-cli.php on line 13
PHP Warning:  include(): Failed opening '../../../wp-load.php' for inclusion (include_path='.:/usr/share/pear:/usr/share/php') in /var/www/thefallenphoenixnet/wp-content/plugins/jekyll-exporter/jekyll-export-cli.php on line 13
PHP Warning:  include(../../../wp-admin/includes/file.php): failed to open stream: No such file or directory in /var/www/thefallenphoenixnet/wp-content/plugins/jekyll-exporter/jekyll-export-cli.php on line 14
PHP Warning:  include(): Failed opening '../../../wp-admin/includes/file.php' for inclusion (include_path='.:/usr/share/pear:/usr/share/php') in /var/www/thefallenphoenixnet/wp-content/plugins/jekyll-exporter/jekyll-export-cli.php on line 14
PHP Fatal error:  Call to undefined function add_action() in /var/www/thefallenphoenixnet/wp-content/plugins/jekyll-exporter/jekyll-exporter.php on line 51

or

[root@shrine thefallenphoenixnet]# wp jekyll-export > export.zip
PHP Fatal error:  Cannot redeclare cli\render() (previously declared in phar:///usr/local/bin/wp/vendor/wp-cli/php-cli-tools/lib/cli/cli.php:26) in /var/www/thefallenphoenixnet/wp-content/plugins/jekyll-exporter/vendor/wp-cli/php-cli-tools/lib/cli/cli.php on line 28
Fatal error: Cannot redeclare cli\render() (previously declared in phar:///usr/local/bin/wp/vendor/wp-cli/php-cli-tools/lib/cli/cli.php:26) in /var/www/thefallenphoenixnet/wp-content/plugins/jekyll-exporter/vendor/wp-cli/php-cli-tools/lib/cli/cli.php on line 28

This is on:

• Wordpress 4.1
• PHP 5.4.16

I am unable to get a zip file or an export file when running this plugin, I keep seeing the following errors:

Warning: copy(/tmp/wp-jekyll-169c28ead8defb8b820d81fd14523529/wp/wp-content/uploads/path/to/media.ext) [function.copy]: failed to open stream: No such file or directory in /home/USER/http/path/to/www/wp/wp-admin/includes/class-wp-filesystem-direct.php on line 217

Warning: copy(/tmp/wp-jekyll-169c28ead8defb8b820d81fd14523529/wp/wp-content/uploads/path/to/media.ext) [function.copy]: failed to open stream: No such file or directory in /home/USER/http/path/to/www/wp/wp-admin/includes/class-wp-filesystem-direct.php on line 217

Warning: copy(/tmp/wp-jekyll-169c28ead8defb8b820d81fd14523529/wp/wp-content/uploads/path/to/media.ext) [function.copy]: failed to open stream: No such file or directory in /home/USER/http/path/to/www/wp/wp-admin/includes/class-wp-filesystem-direct.php on line 217

Warning: copy(/tmp/wp-jekyll-169c28ead8defb8b820d81fd14523529/wp/wp-content/uploads/path/to/media.ext) [function.copy]: failed to open stream: No such file or directory in /home/USER/http/path/to/www/wp/wp-admin/includes/class-wp-filesystem-direct.php on line 217

--- REPEATS AND REPEATS AND REPEATS ---

PK����‡��EQóð�€��/jekyll-export/_config.ymlMʱ Â0��à½OñOvÑv�“8ˆ(¸ô�ŽxÚÃÜ%¤‰¡o/ââúñÕ��æR’�ÇÖÚ V8��‰FaG (...)
(...)
(... and the rest of the output is just garbage characters)

As far as I know everything should be configured correctly. I've been able to use other plugins and Wordpress features, as well as keep PHP and Wordpress up to date.

Note: My Wordpress site is hosted in a www domain, and then Wordpress runs out of a wp folder on the actual server (as opposed to running Wordpress directly in the root).

Version Information

• PHP 5.4
• Wordpress 3.9.2
• Cloned latest plugin from GitHub directly as of 2014 / 08 / 16

Using Wordpress 3.9.1 (latest as of August 1st 2014), the zip file is created and downloaded successfully, it is 3.8 MB file in size, but cannot be extracted, windows claims its an invalid zip file.

Thanks

Hi there! Thanks for writing this exporter.

Unfortunately, I seem to have run into an issue trying to activate the plugin.

Full error: Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING or '(' in /home/content/r/0/0/r00k123123/html/wp-content/plugins/jekyll-exporter/jekyll-exporter.php on line 27

This is version 2.0.1 of the plugin. Version 4.0.1 of Wordpress (hosted with shame on Godaddy).

Anything else I can do to help diagnose? Thanks!

When trying to export, I get multiple errors about:

markdownify.php on line 392
jekyll-export.php on line 401
jekyll-export.php on line 396

when looking at the export path it starts off as /tmp/wp-jekyll-f321288767a6e8eab17b0229ba0f05b9 with the has being randomly generated. Is there a way to change the /tmp value to another location as my hosted provider does not allow /tmp to be written (it's my home directory ~/tmp). I don't see any tmp variables being set.

Running WP 3.8, and going to Tools -> Export to Jekyll, the export page never loads properly. It always loads to a blank page.

Hi,

I'm getting issue while trying to activate plugin

Plugin could not be activated because it triggered a fatal error.

Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING or '(' in /[...]/wp-content/plugins/jekyll-exporter/jekyll-exporter.php on line 27

Hello,

Thanks for writing and supporting this plugin.

I'm having some difficulty getting past some errors. I'm running Wordpress 4.1, PHP 5.4, and the latest version of the wordpress exporter.

I'm receiving multiples of this type of error:

Warning: copy(/tmp/wp-jekyll-d90dca3e9ec4c36e485e8704959d9be1/wp-content/uploads/2012/09/052912-le-trumilou-2-courtesy-jc1-700x525.jpg): failed to open stream: No such file or directory in /home2/knarf/public_html/wp-admin/includes/class-wp-filesystem-direct.php on line 231

finished with a:

Fatal error: Uncaught exception 'Symfony\Component\Filesystem\Exception\IOException' with message 'Failed to create "/tmp/zippy_54c5176d46489": mkdir(): No space left on device.' in /home2/knarf/public_html/...... (shortened)

Any help would be greatly appreciated. Please let me know if there is any additional information you may need.

I was unable to run the plugin as my server was running 5.2.9, upgraded to 5.4, plugin installed perfectly, however when actually running the "export to jekyll" in tools I get:

"Fatal error: Class 'ZipArchive' not found in …public_html/blog/wp-content/plugins/wordpress-to-jekyll-exporter-master/jekyll-export.php on line 326"

Any ideas?

Markdownify is no longer under active development, and a known issue is that it chokes on malformed HTML resulting in undefined call user function errors breaking the zip/export.

Note: this merges issues which arose in #8 and #10

Is there a way to execute it from command line? If wordpress data is too big, it times out...
two ways to resolve it

1. from command line --> this prefarable because I have 1GB size of data
2. changing the timeout... in php

The script fails to export my Wordpress 3.5.1 install (considering a nice export for a future Jekyll site) : Debian Wheezy is up-to-date, with PHP 5.4.16 from DotDeb and MariaDB 5.5.31 from MariaDB repositories.

php jekyll-export-cli.php > jekyll-export.zip
PHP Fatal error:  Call to undefined function WP_Filesystem() in /var/www/wordpress/wp-content/plugins/wordpress-to-jekyll-exporter/jekyll-export.php on line 237

I don't know where to search for a fix.

When I try to activate the plugin, I get the following error message:

"Plugin could not be activated because it triggered a fatal error.

Parse error: syntax error, unexpected T_STRING in /home/djstrouse/webapps/old_wordpress/wp-content/plugins/wordpress-to-jekyll-exporter-master/jekyll-export.php on line 164"

Line 164 of said file is:

"$converter = new Markdownify\ConverterExtra;"

Any ideas on what I'm doing wrong or how to fix this?

When I click Tools > Export to Jekyll I get the following error message:

Fatal error: Uncaught exception 'Alchemy\Zippy\Exception\RuntimeException' with message 'Unable to create the inflator' in /nfs/c06/h08/mnt/153562/domains/piersonthe.net/html/wp-content/plugins/jekyll-exporter/vendor/alchemy/zippy/src/Alchemy/Zippy/Adapter/AbstractBinaryAdapter.php:162 Stack trace: #0 /nfs/c06/h08/mnt/153562/domains/piersonthe.net/html/wp-content/plugins/jekyll-exporter/vendor/alchemy/zippy/src/Alchemy/Zippy/Adapter/AdapterContainer.php(80): Alchemy\Zippy\Adapter\AbstractBinaryAdapter::newInstance(Object(Symfony\Component\Process\ExecutableFinder), Object(Alchemy\Zippy\Resource\ResourceManager), NULL, NULL) #1 /nfs/c06/h08/mnt/153562/domains/piersonthe.net/html/wp-content/plugins/jekyll-exporter/vendor/pimple/pimple/lib/Pimple.php(126): Alchemy\Zippy\Adapter\{closure}(Object(Alchemy\Zippy\Adapter\AdapterContainer)) #2 /nfs/c06/h08/mnt/153562/domains/piersonthe.net/html/wp-content/plugins/jekyll-exporter/vendor/pimple/pimple/lib/Pimple.php(83): {closure}(Object(Alchemy\Zippy\Adapter\AdapterContainer)) #3 / in /nfs/c06/h08/mnt/153562/domains/piersonthe.net/html/wp-content/plugins/jekyll-exporter/vendor/alchemy/zippy/src/Alchemy/Zippy/Zippy.php on line 63

Things are improving... I get this in Safari and Chrome on 10.8.2 Mt Lion after updating to 1.1:

Warning: call_user_func(Markdownify_Extra::flushStacked_ul) [function.call-user-func]: First argument is expected to be a valid callback in /home/jrummel/public_html/wp-content/plugins/wordpress-to-jekyll-exporter/includes/markdownify/markdownify.php on line 392

PKÖtAB/ïug~/jekyll-export/config.yml-Œ± Ã0{MñH½ )SÞÀ°i„�(¤­ÁIù�‡ëV2Þ­]9¥1Füto\­‹P‰»J uÊxÞ?Ö b¢p�ïÆWc­K^¦'¹Ï½šÎ·Ûm1¶cîËßœÿÜ]]RŒMù±õãeçÂ]ÆC?Ü—¿^ÎcûXþ~9CW„/>§ñ¾ü9¡tñïÜCÙ7åxåévsüâÆò—rìûOe}ÚÇýK™]ѹ§þŸsêÏcq ÃÑuíã§ûoã¶Ó¸íüDTtíþ0Vý—¾iܖï×�û¢>ÿeÇÃ\mÛúù’ Ta!tqŽKˆ÷wÏ?Æñt�PÕŽ»î ©?Ÿ�Ç»1ìû¡ ççAó<‹Ñío?ýx:uáåÅéËÇC?öûÁ�OÅ6òü¯HŠ»»»ò'÷T’¢x·�—mý°Ù»®ÃÓ–W‚7U�7¥ïÜùü°iºÖ�¶·ëåišÌ9Œ›qn×»_Ž—cu½/»2òj67 ÏCv¾?¢ëcvûÇðCçDP¢4!zóá}{ÜÏ�¼Ú”WûyØL“Ç‹í¼×Éc¹)σ_dÜpd»óèÆÖï¾Ñ¤Ò´hY^Iêkƒ½³çÝŸ§ý¦tÝøôá=r×¥£¸öéŸÿã2 ƒbÐ-ZVÐPU"‚�Ø›c œhbTÄ „D‹–uJÖS,ƒÈb šÐ4ˆ�‚-+ŒÔµÌQ �ƒÁ,Ñ)(ƒz¶†›–¥•Ò†ëP šÅ)Ms Æ 9Z´,ÕF71lJÃ@²0'b€†HÁæØ0iYï© �W" ËâÑ@Ó0@7L�1Z´¬�Á›Š6ˆ!dž©1e‰yƒ�Zƒºm˜W-K¨i„“CC¤ÉàQ�±4ø-6\µ¬4„aZÓÍHk�š§98o -Z¶ñFÐ_° h DdÁ N³µEÑ¢eÆžyVa´žÁ_16(pÉÑ¢e™�A%šˆAe‰ 1~§94‹TìklˆZÖ„Fx'…�:…Îb ±^OÃÀÁրѢe«Éhˆa†!�S(™ˆê’´hÙc´—5°Ð&Yœ‚ȸ#%aÀàšbvŠIË﹜l˜tÞÞ(¥i¥�æ ‚Ï!rÒ².&�é(oØo}Ü°ùfÐí£ø—qóå¹FWºa¢á׌fî†E‹ÑÓº¿ÿZäK\ô5é™­sÒ²‚3Šõ„­½–

This garbage section is cropped. I believe it's supposed to be the .zip file, however, it's spitting it out on display vs. saving to the server and/or making a zip to download.