I have a WP blog with posts form 2010 to 2016. Posts from 2012 to 2016 are exported fine, while 2010-2011 are 0 bytes .md files.

I added this plugin and it shows up in the plugin list in my admin console:

When I click Activate, the following error is reported:

Parse error: syntax error, unexpected T_STRING in /homepages/3/d374491256/htdocs/blog/wp-content/plugins/wordpress-to-hugo-exporter/hugo-export.php on line 202

A few additional notes:

• on Wordpress version 4.4
• I'm using a hosting provider, so I'm not sure what version of php is installed (I only have sftp access)

If you happen to have recommended troubleshooting steps, let me know. And thank you!

does this need to be updated for newer versions of hugo?

Installed the plugin on a site with Wordpress 4.6.1.

Uploaded the 14ae448 in Wordpress. Activated and exported. After awhile Chome did start the download of the site.

When trying to extract the ZIP with unzip on Linux the following error message is shown:

Archive:  ~/Downloads/hugo-export.zip
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.

Hi, am really confused about what to do after generates the .zip file, it was generated successfully. I have this directory structure:

• 22.2

  index.md

• appointment-booking

• contact-form

• frontpage

• post

• wp-content

• config.yaml

What should I do then? I ran hugo but it says that content folder not found, so I changed the name of wp-content to content.
Also I ran hugo server, started to listen in :1313 port but nothing is showed there.

I am not clear on what to do after generate the .zip file essentially

Hi I just installed this plugin, then click export to hugo, nothing happend for a while it was just loading then finally throw me to request timeout.

The blog have about 200 post, any clue?

thanks

When I run the exporter it creates a huge-export.zip file. When I click on that (latest version of mac os) it creates a hugo-export.zip.cpgz file which if I click on creates another hugo-export.zip file... in a never ending fashion. Looked into using ditto but it says it can't identify the format.

Are there any exprot logs produced somewhere maybe I can review to see if there was an issue with the export?

in the official yaml format of front matter, the tag format is :

tags: ["x", "y"]

but in our export file , the tag is :

tags:

• x
• y

so ,i think this need to be improved

In order to keep the same URL pattern, I suggest to turn the 'permalink' data from the frontmatter to "url', so that the same links will be generated.

With multiple posts on the same date the order gets mixed up.

Changing
return date('Y-m-d', $unixTime);
to
return date('c', $unixTime);
in
function _getPostDate [...]

fixed the issue for me.

Not sure about the other implications, so not creating a pull request.

Hello,

I am hosting my blog on Dreamhost and now, am planning to migrate to hugo. When I tried to export using "wordpress-to-hugo-exporter" plugin then I got the error below.

Fatal error: Maximum execution time of 30 seconds exceeded in /home/mysite/wp-admin/includes/class-wp-filesystem-direct.php on line 231

I downloaded the "wordpress-to-hugo-exporter" master as zip file and uploaded it from wordpress admin dashboard. I am not sure how to edit "php.ini" since I am on a shared host.

Any idea how to fix it? Thanks in advance.

If a link to youtube exist in post (just the plain url) it will not be exported.

I've got a site with 150-200 blog posts to export, hosted on WPEngine, everything up to date version wise.

When I attempt to use the exporter (through the UI as I can't do CLI on this host) I get the following problem:

[Tue Jul 11 19:28:55.301761 2017] [:error] [pid 5633] [client XXXXXX:23529] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 207056397 bytes) in /nas/content/live/itsalocke/wp-includes/functions.php on line 346, referer: https://itsalocke.com/wp-admin/tools.php
--
[Tue Jul 11 19:28:55.315880 2017] [:error] [pid 5633] [client XXXXX:23529] PHP Fatal error: Unknown: Cannot use output buffering in output buffering display handlers in Unknown on line 0, referer: https://itsalocke.com/wp-admin/tools.php

Is there a way I can tweak the export to keep it within 512MB memory?

PS I tried using the Jekyll exporter but that errors in it's own way.

Warning: Invalid argument supplied for foreach() in /nas/content/staging/itsalocke/wp-includes/class-wp-list-util.php on line 153

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 /nas/content/staging/itsalocke/wp-content/plugins/jekyll-exporter/vendor/symfony/process/Process.php

• Windows 10
• Wordpress 4.7

In 7-zip, the path shows up as hugo-export.zip//hugo-export/.... There is an extra no-name directory as the root directory.

Output of php hugo-export-cli.php > export.zip give the following error when trying to unzip export.zip

Archive:  export2.zip
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.
unzip:  cannot find zipfile directory in one of export2.zip or
        export2.zip.zip, and cannot find export2.zip.ZIP, period.

using PHP 5.4.20 on wordpress 4.0

I tried with jekyll exporter and that worked without issues.

Works fine for front matter but I'm getting nothing for the content area. Any ideas?

I executed Exporter from Tools and value of my src tag (in img) ended up corrupt (base64...), see gohugoio/hugo#1170.
Post content and other img tags (e.g. dst-src) did not get corrupt.

Hi,

I've just installed the 1.8 release to my Wordpress 4.9.6 site. Once the plugin is installed, the 'Export to Hugo' entry shows up in the Tools menu. However, clicking on the menu item just leads to a white screen.

I've checked the settings for php 7.0, and it looks like the zip module is loaded.

Any tips on how to debug this?

The html codes such as <p> and <br/> generated probably by wordpress should be removed from the text inside <code> tag.

For example: I have this in my wordpress blog.

<code>
int count = 1;
Console.WriteLine(count);
</code>

That code has been converted as below.

`

int count = 1;
Console.WriteLine(count);

Is it an known issue? How do I fix it?

When I try to activate the plugin I get the error, "Plugin could not be activated because it triggered a fatal error.", details of the error:
Parse error: syntax error, unexpected T_STRING in <root>/wp-content/plugins/wordpress-to-hugo-exporter-master/hugo-export.php on line 202

Hi, and thank you for this tool!

I'm trying to migrate my blog away from Wordpress. I've successfully exported the ZIP file, however, the resulting site doesn't seem to be close to buildable.

Out of the box, running hugo in the unzipped hugo-export directory, results in:

ERROR 2018/03/02 05:36:15 No 'baseURL' set in configuration or as a flag. Features like page menus will not work without one.
Total in 6 ms
Error: Error building site: No source directory found, expecting to find it at /home/vladimir/work/blog/hugo-export/content

Fixing the immediate errors (changing url to baseURL in config.yaml, and creating the content directory) causes hugo to execute successfully, but it still does not generate any HTML files - only some XML files containing blank ATOM feeds. None of the exported blog posts seem to have been picked up.

Are there any additional steps that one must do after the export?

I noticed that when following the instructions for creating a new site on https://gohugo.io/getting-started/quick-start/ , the resulting directory structure is quite different from that generated by this exporter. For example, the exported ZIP file has about, index, posts, topics and wp-content directories, whereas the new Hugo site template has archetypes, content, data, layouts, static, and themes directories, and none of those are present in the other. The configuration file is also .toml instead of .yaml - it's as if the two are for different tools entirely.

Perhaps something changed in a breaking way in hugo itself?

Edit: Well, I figured it out - the missing step was to move all the files, except the configuration, to an existing Hugo site skeleton's content directory. I'll leave this open as it seems there are some actionable points mentioned above, but feel free to close at your discretion. Thanks!

Hello,
I uploaded this plugin to wp, but cant activate it on the dashboard.
i got thls error:

Parse error: syntax error, unexpected T_STRING in /home/u89339/orangefrog.ru/www/wp-content/plugins/wordpress-to-hugo-exporter/hugo-export.php on line 221

thank for any ideas,
Alexandr Gakhov

While exporting a large WordPress blog, I get the following error:
PHP Fatal error: Allowed memory size of 4294967296 bytes exhausted (tried to allocate 1512064064 bytes) in /var/www/blogs/blog_com/blog/wp-content/plugins/wordpress-to-hugo-exporter-1.5.0/includes/markdownify/Converter.php on line 793

I've bumped the memory up to 4G by adding a line to hugo-export-cli.php:
ini_set('memory_limit', '4096M');
but still it fails before completion. Is this a direct result of the size of the blog? Is there another way to export without continually increasing the memory of the process?

For a blog hosted on blah.wordpress.org - so no copy on the local filesystem - how can this utility be used to import to hugo?

Exception thrown when run from command line

$ php hugo-export.php > hugo-export.zip
PHP Fatal error:  Uncaught Error: Call to undefined function add_action() in .../plugins/wordpress-to-hugo-exporter/hugo-export.php:62

$ wp core version --extra
WordPress version: 4.7.5
Database revision: 38590
TinyMCE version:   4.506 (4506-20170408)
Package language:  en_US

$ php -v
PHP 7.1.5 (cli) (built: May  9 2017 16:55:02) ( NTS )
Copyright (c) 1997-2017 The PHP Group
Zend Engine v3.1.0, Copyright (c) 1998-2017 Zend Technologies

Hi,

Can you please describe how we can run this on an exported xml file from wordpress.com? There is no way to install the plugin to wordpress.com so I'm curious how to achieve it. Thanks

I'm past #18 and hit my next snag - I hope others find this helpful too. At the end of a download, I'm left with a file called hugo-export.zip.download that's tiny. When I try to unzip it, it turns into a .cpgz, which I then unzip into another .zip. This goes on forever.

-rw-r--r--@   1 myusername  mygroup   3.0K Dec 21 10:35 hugo-export.zip
-rw-r--r--    1 myusername  mygroup   1.6K Dec 21 10:35 hugo-export.zip.cpgz

Hi Cyrill,

Do you think that we could add an export of local files (ie. `wp-content' ) so that images and other files can go to the static folder ?

Hi there,

Great job on this plugin, it works very well for most cases, and I have used it successfully in previous builds.

However, I am hoping you may be able to shed some light on the way the exported .md files for posts are processed.
I have a normal WordPress permalink structure of /year/month/day and as per usual, the markdown frontmatter includes that, as desired.

The individual .md files are prefixed with the following format: Y-m-d- (as noted in the attached screenshot PHP date() function)

My question is whether I can the export format so that posts are placed in subdirectories like so:

So ultimately, upon creation of the the .md files for posts, they are placed in a nested folder format of year/month/day/file-name.md.
I have tried doing so by editing the plugin, editing date format to YY"/"mm"/"dd and running an export locally, but it baulks at exporting the posts.

I am trying to pull these .md files in using GatsbyJS, and while I can rename & place the individual files into the subfolder structure, I have over 300 entries which I'd prefer to avoid editing by hand!

I thought my new format is along the right track, but I shall see whether you have an advisable play in this situation before moving on.

Thank you!

I'm looked through the Hugo documentation and cannot find the underscore convention. Why are posts exported to "_posts" and not "posts"?

I'm trying to export a WP site with the Portfolio Press theme: https://wptheming.com/portfolio-press/. Most of my content is saved as the custom post type "portfolio".

The export process does not output any portfolio posts. How do I include this custom post type?

When using the CLI php hugo-export-cli.php I'm get this error:

PHP Fatal error:  Uncaught Error: Call to a member function find() on boolean in 
/ ... /content/themes/cm/functions/dom-manipulaion.php:41

WP is installed as a submodule, my dir structure:

├── content
│   ├── plugins
│   ├── themes
│   └──uploads -> ../shared/content/uploads
└── wp
    ├── wp-admin
    ├── wp-content
    └── wp-includes

I had to update the two include path in hugo-export-cli.php because WordPress is in ./wp. Could this have something to do with it?

I'm running PHP 7.0.19 and WordPress 4.7.5.

same problems as the originating jekyll-exporter. Are you going to work on this or was this just a one-time shot?

Hi!

The loop at line 370, foreach (glob(trailingslashit($dir) . '*') as $path) { is failing to run if there are empty directories on wp-content/uploads/. I'm sorry, but I don't know how to fix it. I deleted all empty directories and filled the directory of current month with a dummy text file.

Thanks, guys.

I installed this plugin and used it. It downloaded a zip file, but it would not open. When I tried to unzip with 7zip, it told me that hte file was not correctly setup as a zip file. I used the wordpress to jekyll plugin and converted to hugo.

i tested the plug in the Chinese env, the title of article that contain the Chinese will convert not correct

Doesn't seem to work for me.

$  wp hugo-export

PHP Fatal error:  Uncaught Error: Call to a member function export() on null in /var/www/html/markrichman.com/wp-content/plugins/wordpress-to-hugo-exporter/hugo-export.php:530
Stack trace:
#0 [internal function]: Hugo_Export_Command->__invoke(Array, Array)
#1 phar:///usr/local/bin/wp/php/WP_CLI/Dispatcher/CommandFactory.php(67): call_user_func(Array, Array, Array)
#2 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}(Array, Array)
#3 phar:///usr/local/bin/wp/php/WP_CLI/Dispatcher/Subcommand.php(351): call_user_func(Object(Closure), Array, Array)
#4 phar:///usr/local/bin/wp/php/WP_CLI/Runner.php(327): WP_CLI\Dispatcher\Subcommand->invoke(Array, Array, Array)
#5 phar:///usr/local/bin/wp/php/WP_CLI/Runner.php(334): WP_CLI\Runner->run_command(Array, Array)
#6 phar:///usr/local/bin/wp/php/WP_CLI/Runner.php(757): WP_CLI\Runner->_run_command()
#7 phar:///usr/local/bin/wp/php/wp-cli.php(21): WP_CLI\Runner->start()
#8 phar:///usr/local/bin/wp/php/boot-phar.php(5): include('phar:///usr/loc...')
#9 /usr/lo in /var/www/html/markrichman.com/wp-content/plugins/wordpress-to-hugo-exporter/hugo-export.php on line 530
Fatal error: Uncaught Error: Call to a member function export() on null in /var/www/html/markrichman.com/wp-content/plugins/wordpress-to-hugo-exporter/hugo-export.php:530
Stack trace:
#0 [internal function]: Hugo_Export_Command->__invoke(Array, Array)
#1 phar:///usr/local/bin/wp/php/WP_CLI/Dispatcher/CommandFactory.php(67): call_user_func(Array, Array, Array)
#2 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}(Array, Array)
#3 phar:///usr/local/bin/wp/php/WP_CLI/Dispatcher/Subcommand.php(351): call_user_func(Object(Closure), Array, Array)
#4 phar:///usr/local/bin/wp/php/WP_CLI/Runner.php(327): WP_CLI\Dispatcher\Subcommand->invoke(Array, Array, Array)
#5 phar:///usr/local/bin/wp/php/WP_CLI/Runner.php(334): WP_CLI\Runner->run_command(Array, Array)
#6 phar:///usr/local/bin/wp/php/WP_CLI/Runner.php(757): WP_CLI\Runner->_run_command()
#7 phar:///usr/local/bin/wp/php/wp-cli.php(21): WP_CLI\Runner->start()
#8 phar:///usr/local/bin/wp/php/boot-phar.php(5): include('phar:///usr/loc...')
#9 /usr/lo in /var/www/html/markrichman.com/wp-content/plugins/wordpress-to-hugo-exporter/hugo-export.php on line 530

I also tried this:

$ php hugo-export-cli.php
PHP Fatal error:  Cannot redeclare get_file_description() (previously declared in /var/www/html/markrichman.com/wp-admin/includes/file.php:71) in /var/www/html/markrichman.com/wp-admin/includes/file.php on line 86

Cannot redeclare Markdownify\Converter::handleTag_iframe() in /home/oblac203/public_html/wp-content/plugins/wordpress-to-hugo-exporter-1.8.0/includes/markdownify/Converter.php on line 925

this is a great tool!
i think it maybe has the below functions :

1. add the increment export function
2. add the config setting that can list the export history and the date.
3. user can choose total export or increment export.
   if user choose increment export ,the tool will export the content from the last export day.

thansks for the work!

Got this error when trying to run wp hugo-export

PHP Fatal error:  Uncaught Error: Call to a member function export() on null in /var/www/site/wp-content/plugins/wordpress-to-hugo-exporter-master/hugo-export.php:583

Here's my setup:

PHP binary:     /usr/bin/php7.0
PHP version:    7.0.22-0ubuntu0.16.04.1
php.ini used:   /etc/php/7.0/cli/php.ini
WP-CLI root dir:        phar://wp-cli.phar
WP-CLI vendor dir:      phar://wp-cli.phar/vendor
WP_CLI phar path:       /var/www/site
WP-CLI packages dir:
WP-CLI global config:
WP-CLI project config:
WP-CLI version: 1.4.1

For some reason or another, I didn't have an uploads folder. I don't recall if I deleted it for non-use or if WordPress only creates it when it is used the first time. Either way, the exporter bailed. I created an empty folder and the export appears to have run properly now.

Thanks for creating this. It is great.

I can't edit the php.ini file where my website is hosted and I get this error when the plugin is activated with Wordpress:

Parse error: syntax error, unexpected T_STRING in /web/htdocs/home/wordpress/wp-content/plugins/wordpress-to-hugo/hugo-export.php on line 202

Are the two things related? Is there a way to fix this other that edit php.ini file?

Thank you.

Hi,

Here's what I did.

1. Downloaded the repository as a .zip file.
2. Uploaded it as a .zip file in my WPEngine.com hosted Wordpress blog - WP Version 4.4.1.
3. Successfully installed and activated the plugin.
4. Clicked Export to Hugo from the Tools menu.
5. The export started and it created a 54 mb .zip file in my local windows download folder.
6. I tried to unzip the .zip file and am getting an error that the file is corrupt.
7. I tried double-clicking .zip file and when I did that, there's nothing inside.

So the file is getting created, because I can open it in a text editor and see binary characters, and it is about 54 Mb, i.e. not an empty file.

I don't know the PHP and other versions. I think Wpengine.com uses the latest of everything.

I played with exporter the other night and noticed it did not play well with high utf characters.

I had issues with non printable chars (e.g. 
), double quotes ("), single quotes (' and ').. in my titles, causing invalid .md files generation, breaking hugo, looking bad (all titles on site contained codes, not characters) etc.

Eg, one blog post had title with – in it (–). Front matter looked like this:

title: 'Top Gear 03×13 – BBC camera and editing crew are gods'
author: Daemon
type: post
date: 2009-07-06T08:35:56+00:00
url: /2009/07/06/top-gear-03x13-bbc-camera-and-editing-crew-are-gods/
views:
  - 129
categories:
  - developers journal

This one was causing hugo to break with yaml: invalid trailing UTF-8 octet

Started building sites ...
ERROR 2017/11/10 00:00:59 failed to parse page metadata for "posts/2009-07-06-top-gear-03x13-bbc-camera-and-editing-crew-are-gods.md": yaml: invalid trailing UTF-8 octet
Error: Error building site: Errors reading pages: Error: failed to parse page metadata for "posts/2009-07-06-top-gear-03x13-bbc-camera-and-editing-crew-are-gods.md": yaml: invalid trailing UTF-8 octet for 2009-07-06-top-gear-03x13-bbc-camera-and-editing-crew-are-gods.md

Other high ut8 chars just looked like codes in titles in generated code.

I created PR #49

Thanks for great work!
Best!

TC

Any iframes in a post or page are being stripped out when exported. Other HTML is left in, so shouldn't iframes be left in as well? This could possibly be a Wordpress or Markdownify issue as well.

I had some problems with nested upload dirs:
uploads/YYYY/MM/$filename

wp_filesystem->mkdir doesn't recurse (like mkdir -p) so I changed the plugin like this:

diff --git a/hugo-export.php b/hugo-export.php
index 5bde326..5651fd6 100644
--- a/hugo-export.php
+++ b/hugo-export.php
@@ -474,7 +474,9 @@ class Hugo_Export

         // Make destination directory
         if (!is_dir($dest)) {
-            $wp_filesystem->mkdir($dest);
+            if (! wp_mkdir_p($dest)){
+                $wp_filesystem->mkdir($dest) or wp_die("Could not created $dest");
+            }
         }

         // Loop through the folder

To get it working

This issue was closed, but in fact the solution is to include the line

global $je;

in the file hugo-export.php just before the line $je = new Hugo_Export();. For some reason php (or at least version 5.6) seems to have trouble with global variables.