Jump to content



Recommended Posts

I posted about this on kongondo's blog module thread, but wanted to note it here too :)

I just tested Nico's new version, tweaked the field and template names to match those used by K's Blog module, imported my WP blog xml and it worked brilliantly.

Great work Nico!

  • Like 1
Link to comment
Share on other sites

Thanks Adrian and Nico for these two powerful tools. I can confirm that I was able to import a WP site and was blown away by the results.

This opens up a lot of professional opportunities to offer much quicker redesigns to those clients who come to me frustrated with their Wordpress sites, complaining that they have not fulfilled their expectations and were unable to grow and adapt to their business needs.

  • Like 7
Link to comment
Share on other sites

This module saved me a ton of time overall. The site I was using as a test case has one custom post type. After a couple of attempts to import the entire Wordpress export file, I figured out that it is easier to make exports of the regular posts and custom posts individually. I then had to go through the custom post type xml file and find/replace two things. First, I had to change these urls 

<guid isPermaLink="false">http://localhost/clients/yoursitehere/v03/?post_type=events&p=183</guid>

to look like this

<guid isPermaLink="false">http://localhost/clients/yoursitehere/v03/?p=183</guid>

Then I had to change the post type from




I wasn't able to figure out how to pull in my custom meta information, but even with having to do that manually, these modules saved me a ton of time. I'm sure that I probably did this inefficiently, but in the end I was able to Forrest Gump my way through it and get the results I needed.

I appreciate the work that has been put into these modules. Thanks guys!

  • Like 3
Link to comment
Share on other sites

Hey, thank you for posting this workaround. Custom post types are currently not supported. (I don't even have test data for custom posts). Comments aren't supported as well at moment. But both will follow in the next time. 

  • Like 1
Link to comment
Share on other sites

Yeah, that's totally understandable. Since they're custom post types, it seems like all the variations would be difficult to plan for. I'm glad you guys came up with a way to get most of the information into ProcessWire. I was dreading all the copying/pasting I was going to have to do.

  • Like 1
Link to comment
Share on other sites

  • 4 weeks later...

hi there!
i just discovered this great module an wanted to test it with a site of mine.
export worked well (140mb zip  :o), but the import failed with the following error:

Can't save page 0: /: It has an empty 'name' field

it seems like there is an issue with the import/export and the use of the »Languages Support - Page Names« module. using this module, the homepage also has a name field for each language, where the field for the default language is empty by default. this seems to bug the import. if i add a name manually, the import succeeds, but i get another (undeleteable) homepage under the original.
a second error occurs, when i try to import user details:

Can't save page 0: /cms/access/roles/: It has an empty 'name' field

i couldn't find the reason for this.
and last but not least the third error:
When i select the "Edit Imported Content" option, i can choose the fields and pages, i want to import. after submitting may selection i get an error, that zip or json are missing.
otherwise, great module!  :wub:

  • Like 1
Link to comment
Share on other sites

tobaco - thanks for the comprehensive report. I have tested the module with standard language support, but never with "Languages Support - Page Names". Sorry, multi language stuff is not something I ever use, so I am a bit ignorant of it I'm afraid. Is it common practice for the field for the default language to be empty by default?

Not sure about the roles issue - creating new users and roles this is a relatively new feature for Migrator - I'll need to see if I can replicate the error you got. Would it be possible to send me the json file from your export so I can see how the role was defined during export?

I'll look into the Edit Imported Content issue - again that is a relatively new feature and I think some more recent changes might have broken that - hopefully should be an easy fix - just a session variable issue.

Link to comment
Share on other sites

Ok, just to follow up. I have fixed the issue with the error when using the "Edit Imported Content" option - stupid oversight on my part when I added a cleanup routine in a recent update. Should be fine now :)

I can't replicate the error around roles so it would be great to have your exported json if possible.

I also tried to look at the language page names issue, but when I tried to leave the default name blank I get an error saying that it can't be blank, but I think I must not be understanding this. Could you please outline the steps to set up a site with multi-language page names with a blank default name so I can test this.

Thanks again for your feedback with this.

  • Like 1
Link to comment
Share on other sites

Hi I am getting the error 'Missing required ZIP or JSON Souce' as well, both with a custom page tree import. and the blog profile zip import.

Edit: Sorry, the blog.zip import works ok.

In my exported files.zip there is not a .json file.

This is the structure of the exported files.zip:














I get the error whether Edit Imported Content is checked or not.

I hope that helps. If you need any more info please let me know.

Edited by NooseLadder
Link to comment
Share on other sites


Thanks for the json file. I will take a look at the language/role issues when I have a little more time - sometime early next week.


Can you please make sure you are running the latest version of Migrator - I think the fix I made yesterday should take care of the issues you are having. Although it is surprising to hear that you don't have a data.json file in your exported files.zip - I have never seen that before. Does it make a difference if you choose a different parent page when exporting?

Edited by adrian
Link to comment
Share on other sites

Can you please try exporting a page tree that does not include Home as the parent? I think maybe there might be an issue with selecting Home as the parent. It works for me, but just trying to narrow it down. 

Also, are you running multilanguage page names?

Link to comment
Share on other sites


I have run some more tests. Exporting from a live server is ok (the JSON file is created) but exporting from localhost (Xampp) it is not created. Maybe its the php server configuration but I am not sure where to look for this particular problem.  :(

I hope we can get this running on localhost as this is where I make all the site changes prior to uploading to live server.

Edit: I've just chechek XAMPP phpinfo and json support is enabled, json version 1.2.1. This is the same on my live server.

Edited by NooseLadder
Link to comment
Share on other sites

Can you please clear your browser session data and then run an export on your xamp server and after the file has downloaded, reload the page and open up:

Debug Mode Tools > Session and look for an entry like this:

jsonFilename | /Users/xxxxxx/site/assets/files/1006/data.json

Keep in mind the 1006 will be different.

Link to comment
Share on other sites

I've just terminated (exit;) the module ( line 316) after data.json and files.zip creation and both files are in the /1022/ folder.

Edit: But after zip download the json file is missing in the zip file.

Edited by NooseLadder
Link to comment
Share on other sites

I've just terminated (exit;) the module ( line 316) after data.json and files.zip creation and both files are in the /1022/ folder.

What do you see in your 1022 folder if you move the exit down to after line 317 and then again after 318?

I am assuming there is something in the create_zip function that isn't working on your local install. Maybe it's the ZIPARCHIVE::OVERWRITE?

Link to comment
Share on other sites


I haven't looked into the language issue fully yet, but had a quick look at the role error you are getting. For some reason your cms user doesn't have a role defined in the json file. From what I can tell, it is not possible to save a user in PW without at least having the guest role assigned, but could you please look at that user and let me know the role setup for it?

Another role issue I noticed has shown up because you are migrating your entire page tree, which includes the default 404 page. The created_user_id for this page is 3 which is not actually a user. I am going to check with Ryan if there is a reason for this. Regardless, I should be able to implement a workaround for this easily.

One nice thing from playing around with your JSON file is that the FieldtypeTextareas field appears to have been imported correctly - I hadn't tested any of the new Profields with Migrator yet, so this is an encouraging start :)

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Robin S
      This module lets you add some custom menu items to the main admin menu, and you can set the dropdown links dynamically in a hook if needed.
      Sidenote: the module config uses some repeatable/sortable rows for the child link settings, similar to the ProFields Table interface. The data gets saved as JSON in a hidden textarea field. Might be interesting to other module developers?
      Custom Admin Menus
      Adds up to three custom menu items with optional dropdowns to the main admin menu.
      The menu items can link to admin pages, front-end pages, or pages on external websites.
      The links can be set to open in a new browser tab, and child links in the dropdown can be given an icon.
      Requires ProcessWire v3.0.178 or newer.
      Example of menu items

      Module config for the menus

      Link list shown when parent menu item is not given a URL

      Setting child menu items dynamically
      If needed you can set the child menu items dynamically using a hook.
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $colours = $event->wire()->pages->findRaw('template=colour', ['title', 'url', 'page_icon']); $children = []; foreach($colours as $colour) { // Each child item should be an array with the following keys $children[] = [ 'icon' => $colour['page_icon'], 'label' => $colour['title'], 'url' => $colour['url'], 'newtab' => false, ]; } $event->return = $children; } }); Create multiple levels of flyout menus
      It's also possible to create multiple levels of flyout submenus using a hook.

      For each level a submenu can be defined in a "children" item. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $children = [ [ 'icon' => 'adjust', 'label' => 'One', 'url' => '/one/', 'newtab' => false, ], [ 'icon' => 'anchor', 'label' => 'Two', 'url' => '/two/', 'newtab' => false, 'children' => [ [ 'icon' => 'child', 'label' => 'Red', 'url' => '/red/', 'newtab' => false, ], [ 'icon' => 'bullhorn', 'label' => 'Green', 'url' => '/green/', 'newtab' => false, 'children' => [ [ 'icon' => 'wifi', 'label' => 'Small', 'url' => '/small/', 'newtab' => true, ], [ 'icon' => 'codepen', 'label' => 'Medium', 'url' => '/medium/', 'newtab' => false, ], [ 'icon' => 'cogs', 'label' => 'Large', 'url' => '/large/', 'newtab' => false, ], ] ], [ 'icon' => 'futbol-o', 'label' => 'Blue', 'url' => '/blue/', 'newtab' => true, ], ] ], [ 'icon' => 'hand-o-left', 'label' => 'Three', 'url' => '/three/', 'newtab' => false, ], ]; $event->return = $children; } }); Showing/hiding menus according to user role
      You can determine which menu items can be seen by a role by checking the user's role in the hook.
      For example, if a user has or lacks a role you could include different child menu items in the hook return value. Or if you want to conditionally hide a custom menu altogether you can set the return value to false. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); $user = $event->wire()->user; // For custom menu number 1... if($menu_number === 1) { // ...if user does not have some particular role... if(!$user->hasRole('foo')) { // ...do not show the menu $event->return = false; } } });  
    • By tcnet
      This module for ProcessWire sends a notification email for each failed login attempt. Similar modules exists already in the module directory of ProcessWire. However, this module is designed to notify, even if specified user doesn't exist.
      The settings for this module are located in the menu Modules=>Configure=>LoginFailNotifier.
      Notification email
      Specifies the email address to which the notification emails should be sent.
        Email subject
      Specifies the subject line for the notification email.
        Post variables
      Specifies the $_POST variables to be included in the notification email. Each variable must be separated by a comma. For example: login_name,login_pass
        Server variables
      Specifies the $_SERVER variables to be included in the notification email. Each variable must be separated by a comma. For example: REMOTE_ADDR,HTTP_USER_AGENT
      Link to ProcessWire module directory:
      Link to github.com:
    • By Fokke
      ProcessWire 3.x markup module for rendering meta tags in HTML document head section. Note that this module is not a full-blown SEO solution, but rather a simple tool for rendering meta tags based on module configuration. Adding custom meta tags is also supported.
      Built-in meta tags
      The following meta tags are supported out-of-the-box:
      Document title consisting of page title and site name Character set Canonical Viewport Description Keywords Hreflang tags Open Graph og:title og:site_name og:type og:url og:description og:image og:image:width og:image:height Twitter meta tags twitter:card twitter:site twitter:creator twitter:title twitter:description twitter:image Facebook meta tags fb:app_id The full documentation with configurable options can be found here: https://github.com/Fokke-/MarkupMetadata
      ProcessWire>=3.0.0 PHP >=7.1 Installation using Composer
      composer require fokke/markup-metadata Manual installation
      Download latest version from https://github.com/Fokke-/MarkupMetadata/archive/master.zip Extract module files to site/modules/MarkupMetadata directory.
    • By m.sieber
      ITRK-Service for ProcessWire
      Module for the automated transfer of imprint, data protection declaration and terms and conditions from IT-Recht Kanzlei to your ProcessWire installation
      What is ITRK Service for ProcessWire?
      ITRK-Service for ProcessWire is a free module for ProcessWire CMS. It provides an interface to the update service of IT-Recht Kanzlei, via which the legal texts of your online presence are automatically updated. In this way, the texts remain legally secure and warning-proof in the long term. Imprint, data protection declaration, revocation and general terms and conditions are currently supported.
      You can find our documentation (in german language) here: https://www.pupit.de/itrk-service-for-processwire/dokumentation/

      Download: https://www.pupit.de/itrk-service-for-processwire/
      Github: https://github.com/pupit-de/pwItrkServiceConnector
    • By LuisM
      Symprowire is a PHP MVC Framework based and built on Symfony using ProcessWire 3.x as DBAL and Service-Provider
      It acts as a Drop-In Replacement Module to handle the Request/Response outside the ProcessWire Admin. Even tough Symfony or any other mature MVC Framework could be intimidating at first, Symprowire tries to abstract Configuration and Symfony Internals away as much as possible to give you a quick start and lift the heavy work for you.
      The main Goal is to give an easy path to follow an MVC Approach during development with ProcessWire and open up the available eco-system.
      You can find the GitHub Repo and more Information here: https://github.com/Luis85/symprowire
      The Symprowire Wiki https://github.com/Luis85/symprowire/wiki How to create a simple Blog with Symprowire https://github.com/Luis85/symprowire/wiki/Symprowire-Blog-Tutorial Last Update
      16.07.2021 // RC 1 v0.6.0 centralized ProcessWire access trough out the Application by wrapping to a Service https://github.com/Luis85/symprowire/releases/tag/v0.6.0-rc-1 Requirements
      PHP ^7.4 Fresh ProcessWire ^3.0.181 with a Blank Profile Composer 2 (v1 should work, not recommended) The usual Symfony Requirements Features
      Twig Dependency Injection Monolog for Symprowire Support for .env YAML Configuration Symfony Console and Console Commands Symfony Webprofiler Full ProcessWire access inside your Controller and Services Webpack Encore support Caveats
      Symfony is no small Framework and will come with a price in terms of Memory Usage and added Overhead. To give you a taste I installed Tracy Debugger alongside to compare ProcessWire profiling with the included Symfony Webprofiler

      So in a fresh install Symprowire would atleast add another 2MB of Memory usage and around 40ms in response time, should be less in production due to the added overhead of the Webprofiler in dev env
  • Create New...