Enhancement: Support for Custom Fields / Advanced Custom Fields Plugin about wordpress-to-jekyll-exporter HOT 7 CLOSED

@jambox are you still interested in this? Is there a clean way to get a list of the ACF fields for a given post?

from wordpress-to-jekyll-exporter.

@benbalter In theory I'm still interested in this feature, sure, but the last few times I tried to use this plugin in the past 6-8 months or so, the only result is a corrupt zip file, as outlined in this issue. Definitely a bigger roadblock for me than the ACF stuff at this point...

But in terms of the tech, yes, there are ways of isolating the ACF-specific post_meta fields. If the plugin can work on a basic level for me at some point, I can try to team up with you to figure out the best way to return a clean json object or whatever you need to generate the proper output. Keep me in the loop if you're interested!

from wordpress-to-jekyll-exporter.

but the last few times I tried to use this plugin in the past 6-8 months or so, the only result is a corrupt zip file, as outlined in this issue

If you have a chance, I believe 2.1.1 should resolve many of those issues on most environments.

from wordpress-to-jekyll-exporter.

Thanks for the follow up. Just tried installing via git clone and exporting and the same kind of infinite .zip <> .cpgz issue is happening

Also, just saw an issue where I can't de/activate the plugin via WP CLI...any way this is tied to some sort of runtime error?

from wordpress-to-jekyll-exporter.

and exporting and the same kind of infinite .zip <> .cpgz issue is happening

Have you tried deactivating all other plugins? I'm starting to suspect caching or some other mechanism is corrupting the zip.

from wordpress-to-jekyll-exporter.

Just tried deactivating everything and running your plugin and the same thing happened. I did rename, and thereby ostensibly remove, a few some drop-in plugin files related to caching plugins which helped a bit because now I can see a fatal error in my debug trace. Seems related to Spyc (which I saw in another thread) and/or composer/autoload:

[11-Jan-2016 18:42:44 UTC] PHP Fatal error:  Cannot redeclare class Spyc in /Applications/MAMP/htdocs/{REDACTED_PATH}/wp-content/plugins/wordpress-to-jekyll-exporter/vendor/mustangostang/spyc/Spyc.php on line 57
[11-Jan-2016 18:42:44 UTC] PHP Stack trace:
[11-Jan-2016 18:42:44 UTC] PHP   1. {main}() /Users/{REDACTED_USER}/.wp-cli/bin/wp:0
[11-Jan-2016 18:42:44 UTC] PHP   2. include() /Users/{REDACTED_USER}/.wp-cli/bin/wp:4
[11-Jan-2016 18:42:44 UTC] PHP   3. include() phar:///Users/{REDACTED_USER}/.wp-cli/bin/wp/php/boot-phar.php:5
[11-Jan-2016 18:42:44 UTC] PHP   4. WP_CLI\Runner->start() phar:///Users/{REDACTED_USER}/.wp-cli/bin/wp/php/wp-cli.php:21
[11-Jan-2016 18:42:44 UTC] PHP   5. WP_CLI\Runner->load_wordpress() phar:///Users/{REDACTED_USER}/.wp-cli/bin/wp/php/WP_CLI/Runner.php:697
[11-Jan-2016 18:42:44 UTC] PHP   6. require() phar:///Users/{REDACTED_USER}/.wp-cli/bin/wp/php/WP_CLI/Runner.php:736
[11-Jan-2016 18:42:44 UTC] PHP   7. include_once() phar:///Users/{REDACTED_USER}/.wp-cli/bin/wp/php/wp-settings-cli.php:289
[11-Jan-2016 18:42:44 UTC] PHP   8. require_once() /Applications/MAMP/htdocs/{REDACTED_PATH}/wp-content/plugins/wordpress-to-jekyll-exporter/jekyll-exporter.php:31
[11-Jan-2016 18:42:44 UTC] PHP   9. ComposerAutoloaderInitf3a896456a2c29b2d298527963f263df::getLoader() /Applications/MAMP/htdocs/{REDACTED_PATH}/wp-content/plugins/wordpress-to-jekyll-exporter/vendor/autoload.php:7

Unfortunately this is all the time I have today to help debug. Also, it might be good to move this thread to issue #70 as its less pertinent to the ACF situation. Thanks!

from wordpress-to-jekyll-exporter.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from wordpress-to-jekyll-exporter.