Jump to content



Recommended Posts

1 hour ago, Karinne Cyphers said:

we do want to keep using the Matrix Repeaters as it really improves the content editing experience for our content team.

I know lots of us enjoy using them and I think it would be a worthwhile addition to Migrator. I bet it would be much quicker to extend Migrator than to look for other options 🙂

Maybe at some point in the future I'll find some time to look at adding it. It supports all the other ProFields, so it makes sense to include it as well.

Link to comment
Share on other sites

16 hours ago, adrian said:

I know lots of us enjoy using them and I think it would be a worthwhile addition to Migrator. I bet it would be much quicker to extend Migrator than to look for other options 🙂

Maybe at some point in the future I'll find some time to look at adding it. It supports all the other ProFields, so it makes sense to include it as well.

Yes, agreed.  Thanks for the update.

Link to comment
Share on other sites

  • 2 years later...


I am trying to import to processwire a wordpress site with multi language. I have installed Processmigrator and MigratorWordpress(also in processwire multi laguage support is installed and fields have been change to support multi language). I have exported content(posts) from wordpress and successfully migrated to processwire. Currently both language posts are showing up as different pages.

Can someone point me to right direction is there a way to migrate these posts into one or when i start importing from wordpress what should i do to have them imported in multilanguage?


Thanks in advance,

Link to comment
Share on other sites

Hi @fisnik - I am glad to hear the import when reasonable well. I also just used it a few weeks ago - it's strange to me that it doesn't seem to see much usage.

Sorry about the ML issues. I have never seen the xml export of a ML wordpress site so I don't know the format, but it sounds like they are separate entries. I am sure this is doable but it will either require some modifications to MigratorWordpress to combine ML posts by ID before generating the JSON for the pages to be imported.

Alternatively, you could probably write an API script to match the posts that are separate pages and pull the content to the default language version page, save that, and then delete the other language version. It depends on whether you can match the two pages - the old WP post ID would be ideal but MigratorWordpress doesn't import that is so you'd also need to handle that I think.

Should definitely be doable, but I am sorry I don't have time to help at the moment, but happy to answer questions if you get stuck along the way.

Link to comment
Share on other sites

@adrian Thanks a lot for info. I will try to do something and if it works i will share the info. Regarding usage usually myself when there is not too much content i copy it directly, i think this is the case for others too. But in cases like this one that i have now, we need modules like this i have to move 1000+ posts.

I have to say that this module is life saver and very easy/simple to use, it does the job perfectly.


Link to comment
Share on other sites

  • 2 weeks later...

Hi @adrian i hope you are doing well. I have managed to migrate multi language posts with a help from a friend.
What i just found out is that this module is not importing "featured image" from wordpress, it is importing only images that are embed on body. Is this right or did i miss something? Is there an easy way to fix this since it is very important?

FYI: wordpress exporter by default it does not extrcat that image in .xml file, i did use this plugin to do that.

Link to comment
Share on other sites

Hi @fisnik - I am sorry I don't have time to look into this, but if you dig into the MigratorWordpress code that parses the xml you should be able to grab the feature image (if that plugin is adding it to the xml). 

Looking at your other post on the CMSCritic thread, it looks like you are also considering the approach used there - maybe that's a better option for you? 

Link to comment
Share on other sites

  • 6 months later...

@adrian this module is really useful! But I can‘t get the zip export/import working. Importing via the other options works great.
Iam able to export a zip file. But when I try to import and upload that file into another PW install it says:

Fatal error: Uncaught PDOException: You cannot serialize or unserialize PDO instances in [no active file]:0 Stack trace: #0 [internal function]: PDO->__sleep() #1 {main} thrown in [no active file] on line 0

I tried this on my local machine (Laravel Valet on an old Apple iMac, latest Chrome Browser) with the latest PW version (3.0.184).  
Also when I try to unzip the achive manually, I get a file called files.zip.cpgz, not sure if this is expected. Any clue what's wrong here?

EDIT: It seems to work fine with files inside the templates folder. I had templates under templates/blocks/ and it was not working. So I guess my question would be, if it is possible to allow templates from subfolders as well? Iam currently working an a pagebuilder module and looking into Migrator to update and import the pagebuilder template files. These files live under templates/blocks/ (my pagebuilder creates pages from these template files).

Link to comment
Share on other sites

@jploch - I just tested a full zip export and import and it worked without any issues with the zip. I did just commit some PHP8 fixes, along with properly excluding RepeaterMatrix fields (I never added support for those), so grab the latest commit.

That "zip.cpgz" is weird though - I wonder if there is an issue with Valet and the PHP zip library it includes?

I wonder if you can convert that to a regular zip (https://www.lifewire.com/cpgz-file-2620362) and try importing that?

Link to comment
Share on other sites

16 hours ago, adrian said:

I just tested a full zip export and import and it worked without any issues with the zip

Thx for looking into this! Not sure if you saw my last edit. The zip export/import works for me with files that are directly in the templates directory, however Iam working on a pagebuilder based on page table that creates pages based on templates in the subfolder "templates/blocks" (See my EDIT above for more information). Would it be possible to support subfolders as well? I was trying to include those files with the "Helper Files" option, but the zip seems to fail if the module can not find the tempate files in the templates root folder. 

Link to comment
Share on other sites

  • 2 weeks later...

After some more tests with PageTable, I found out that migrator is not exporting/importing pages under admin. In my use case I have PageTable configured to save all item/pages in a container page under admin. For example admin–>pt-items. However with this setup migrator only exports the main page where the PageTable lives without the items. 

Placing the PageTable items under admin is a common thing, if you do not want editors to mess with them and keep your page tree clean. I think people also use this approach with PageTableExtended. So it would be nice if migrator would export PageTable items that live under admin or a diffrent parent than the containing page. Since PageTable has a field that saves the IDs of the item pages, that could be used to identify the items.

I understand if this is out of scope for migrator. If so I might look into building my own solution.

Link to comment
Share on other sites

38 minutes ago, adrian said:

@jploch - it's definitely not out of scope for Migrator and it would be great to support it. There are a few places in the code where I have id!=2, has_parent!=2 - it's possible that removing those might take care of things. Can I leave it to you to test?

Thanks Adrian! I try to remove those checks and do some testing. Will report back soon. 

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 MarkE
      This fieldtype and inputfield bundle was built for storing measurement values within a field, rendering them in a variety of formats and converting them to other units or otherwise modifying them via the API.
      The API consists of a number of predefined functions, some of which include...
      render() for rendering the measurement object, valueAs() for converting the value to another unit value, convertTo() for converting the whole measurement object to different units, and add() and subtract() for creating a new measurement object from the sum or difference between two other objects. In the admin the inputfield includes a checkbox (which can be optionally disabled) for converting values on page save. For an example if a value was typed in as centimeters, the unit was changed to metres, and the page saved with this checkbox selected, said value would be automatically converted so that e.g. 170 cm becomes 1.7 m.
      A simple length field using Fieldtype Measurement and Inputfield Measurement.
      Combination units (e.g. feet and inches) are also supported.
      Please note that this module is 'proof of concept' at the moment - there are limited units available and quite a lot of code tidying to do. More units will be added shortly.
      See the GitHub at https://github.com/MetaTunes/FieldtypeMeasurement for full details and updates.
    • By tcnet
      File Manager for ProcessWire is a module to manager files and folders from the CMS backend. It supports creating, deleting, renaming, packing, unpacking, uploading, downloading and editing of files and folders. The integrated code editor ACE supports highlighting of all common programming languages.

      This module is probably the most powerful module. You might destroy your processwire installation if you don't exactly know what you doing. Be careful and use it at your own risk!
      ACE code editor
      This module uses ACE code editor available from: https://github.com/ajaxorg/ace

      This module uses the JavaScript dragscroll available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability to drag the table horizontally with the mouse pointer.
      PHP File Manager
      This module uses a modified version of PHP File Manager available from: https://github.com/alexantr/filemanager
    • By tcnet
      This module implements the website live chat service from tawk.to. Actually the module doesn't have to do much. It just need to inserted a few lines of JavaScript just before the closing body tag </body> on each side. However, the module offers additional options to display the widget only on certain pages.
      Create an account
      Visit https://www.tawk.to and create an account. It's free! At some point you will reach a page where you can copy the required JavaScript-code.

      Open the module settings and paste the JavaScript-code into the field as shown below. Click "Submit" and that's all.

      Open the module settings
      The settings for this module are located int the menu Modules=>Configure=>LiveChatTawkTo.

    • By tcnet
      Session Viewer is a module for ProcessWire to list session files and display session data. This module is helpful to display the session data of a specific session or to kick out a logged in user by simply delete his session file. After installation the module is available in the Setup menu.

      The following conditions must be met for the module to work properly:
      Session files
      Session data must be stored in session files, which is the default way in ProcessWire. Sessions stored in the database are not supported by this module. The path to the directory where the session files are stored must be declared in the ProcessWire configuration which is by default: site/assets/sessions.
      Serialize handler
      In order to transform session data easier back to a PHP array, the session data is stored serialized. PHP offers a way to declare a custom serialize handler. This module supports only the default serialize handlers: php, php_binary and php_serialize. WDDX was dropped in PHP 7.4.0 and is therefore not supported by this module as well as any other custom serialize handler. Which serialize handler is actually used you can find out in the module configuration which is available under Modules=>Configure=>SessionViewer.

      Session data
      The session data can be displayed in two different ways. PHP's default output for arrays print_r() or by default for this module nice_r() offered on github: https://github.com/uuf6429/nice_r. There is a setting in the module configuration if someone prefers print_r(). Apart from the better handling and overview of the folded session data the output of nice_r() looks indeed nicer.

      ProcessWire module directory
    • By Robin S
      Repeater Easy Sort
      Adds a compact "easy-sort" mode to Repeater and Repeater Matrix, making those fields easier to sort when there are a large number of items.
      The module also enhances Repeater Matrix by allowing a colour to be set for each matrix type. This colour is used in the item headers and in the "add new" links, to help visually distinguish different matrix types in the inputfield.
      A Repeater field

      A Repeater Matrix field with custom header colours

      Easy-sort mode
      Each Repeater/Matrix item gets an double-arrow icon in the item header. Click this icon to enter easy-sort mode.
      While in easy-sort mode:
      The items will reduce in width so that more items can be shown on the screen at once. The minimum width is configurable in the field settings. Any items that were in an open state are collapsed, but when you exit easy-sort mode the previously open items will be reopened. You can drag an item left/right/up/down to sort it within the items. The item that you clicked the icon for is shown with a black background. This makes it easier to find the item you want to move in easy-sort mode. You can click an item header to open the item. An "Exit easy-sort mode" button appears at the bottom of the inputfield. Configuration
      In the field settings for Repeater and Repeater Matrix fields you can define a minimum width in pixels for items in easy-sort mode. While in easy-sort mode the items will be sized to neatly fill the available width on any screen size but will never be narrower than the width you set here.
      In the field settings for Repeater Matrix you can define a custom header colour for each matrix type using an HTML "color" type input. The default colour for this type of input is black, so when black is selected in the input it means that no custom colour will be applied to the header.
      The easy-sort mode is only possible on Repeater/Matrix fields that do not use the "item depth" option.
  • Create New...