Jump to content
adrian

Migrator

Recommended Posts

I think Nico is working on a few more tweaks to this as we speak.

Firstly, MigratorWordpress is not designed to give you a fully functioning blog in that it doesn't create a template to render your posts. You could use the template from Ryan's blog profile though and depending on names of fields it will work, although I haven't compared these to be certain.

I just tested Nico's new version with a recently exported XML from the current version of WP and it works perfectly. All the tags and categories were created, the page fields created, and they were assigned to each post correctly. The only current issue I had was some issues with html and body tags making it into the body field of the post (which affect the viewing in edit mode), which I think Nico is working on now.

One thing to be aware of is the "Parent Page" setting when importing. If you are testing and trashed a previous import, this will load up that original page from the trash by default. I might need to consider doing a check to make sure this can't happen.

Also, out of curiosity, are you selecting your Home page as the parent, or a child of this? My successful test this morning was to a child page - eg: Home > Blog

Share this post


Link to post
Share on other sites

Hi Adrian,

thanks for your reply.

Firstly, MigratorWordpress is not designed to give you a fully functioning blog in that it doesn't create a template to render your posts.

I assumed so but was unsure. Thanks for clarifying.

This is what I tried out in the meantime:

  • clean, untouched PW install
  • import the blog profile from the zip you posted earlier in this thread. Choose home as parent -> perfect working blog, script added /blog/ and the appropriate children to the page tree
  • import WP-XML, parent = /blog/, import everything, append, import dates = true, edit content = false -> all posts, categories, tags are there but categories are not assigned to posts and all post dates are today. Page tree as before.

For me this is perfectly good - more than I ever expected. I'll give this a go now with the site I'm working on (keep my fingers crossed ...) and adjust the template styling to my needs.

Thanks again!

Share this post


Link to post
Share on other sites

Thanks for the report.

Not sure why the categories are not being assigned to your posts. I am getting mixed success with this - on a clean install it always works, so I am wondering if it's an issue with the fields already existing. Have you played with the Import Type options? I wonder if maybe using "Replace" might work?

As for the dates being today - is that the modified date or the created date? The created date works for me, but I still need to fix the modified date - unfortunately when PW saves the page, the modified date is instantly changed. Quiet mode saving works for the created date, but not the modified date. I might need to do this using SQL.

Thanks for helping us to debug this.

Share this post


Link to post
Share on other sites

Ok, I just tested the "Replace" option and it doesn't solve the tags/categories issue, but if you manually remove those two fields from the post template and then delete them, the next import works perfectly with tags and templates assigned to posts as they should be. I will try to figure out why and see what I can do to avoid the need to do this.

Share this post


Link to post
Share on other sites

Thats what i meant in my pm, Adrian. The fields have got a "hard coded" parent after creating. And when importing a second time without removing the fields it keeps the parent because fields aren't overwritten (are they?)

But at the end you only should have to use it one time so that won't be the problem but not really satisfying for me :/

Share this post


Link to post
Share on other sites

Nico - yeah, I get what you meant now - I thought you were referring to the Parent Page setting during import.

I was actually just looking at the category and tag field input tabs and seeing the parent set to:

/trash/1297_blog-test-3/ Categories 

Which as you say, is exactly why they aren't working when you run an import, then trash the entire blog page tree and import again.

I should be able to to add a check in though to replace the parent if it has a status that flags it as being in the trash. I think that should work fine.

Share this post


Link to post
Share on other sites

I have just committed a couple of updates that take care of an image filename issue when using the Wordpress import, and more importantly it now completely honors the modified user and modified date values from the original source, whether from Wordpress or another PW installation.

  • Like 2

Share this post


Link to post
Share on other sites

Hi,

I'll continue testing tonight. Will be occupied with other tasks during the day unfortunately. Sent via mobile.

Share this post


Link to post
Share on other sites

Thanks @totoff,

We have both made a few enhancements in the last couple of hours, so be sure to grab the latest versions of both modules. There are still a few things to iron out, but it's starting to look really good - hopefully in the next couple of days we can get the final tweaks sorted.

Back to real work now :)

Share this post


Link to post
Share on other sites

Minor, but important fix just committed to prevent domdocument from adding docytype, html, and body tags to RTE fields.

Share this post


Link to post
Share on other sites

Hi Adrian, Nico,

sorry that it took a while to get back. Unfortunately I can't report that this is working completely fine for me. Here is what I did:

1st attempt

  • Parent = Home
  • Everything = true
  • Append = true
  • Import Dates = true
  • File = blogprofile.zip
  • Edit content = false
  • Result = perfect

Trying to import WP-Data

  • Everything = true
  • Parent = Blog
  • Append = true
  • Import Dates = true
  • Edit content = false
  • Warning: Unknown Selector operator: '=%' -- was your selector value properly escaped?
  • Result = Import successful, no tags/categories assigned, post dates as of today. Page tree as before

2nd Attempt

  • Remove fields tags and categories from template post
  • deleted the fields
  • Parent = Blog
  • Import everything = true
  • Replace = true
  • Import Dates = true
  • Import-file = WP File
  • Edit content = false
  • Warning: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'c2-a719-1108' for key ‚name_parent_id'
  • Result = Blog posts are present but can’t be edited in the admin. Warning : Unknown Selector operator: '' -- was your selector value properly escaped?

3rd Attempt

  • Rollback installation to clean state from 1st attempt
  • Repeat import blogprofile.zip from attempt 1
  • Result = perfect

Import WP-Data

  • Everything = true
  • Parent = Blog
  • Replace = true
  • Import Dates = true
  • Edit content = false
  • Warning: Unknown Selector operator: '=%' -- was your selector value properly escaped?
  • Result = Import successful, no tags/categories assigned, post dates as of today (like with 1st attempt)

Before testing I installed the last versions of your modules.

  • Like 1

Share this post


Link to post
Share on other sites

Thank you for the thorough testing and detailed reporting - really appreciate it.

I had never tried the combo of importing that blog.zip I posted and then importing some WP posts, so I just gave it a go and found it worked flawlessly, except for assigning tags and categories to the posts - there must be a conflict with those fields already being created from the import of Ryan's blog.zip

This sounds mostly like your first attempt, except that for me, I didn't get the selector operator warning and the post dates were imported correctly. 

Can I ask what you mean by: "Page tree as before"?

I am going to see what I can do about the tag/category assignment to posts problem when using Ryan's blog profile and on subsequent install attempts. Once I get that sorted, it would be great if you can test again and make sure debug mode is on to see if we can get some more info on that selector error.

I am not sure why the post dates aren't importing for you, but I'll take a look at that too.

Stay tuned :)

  • Like 1

Share this post


Link to post
Share on other sites

Ok, I think we are sorted :)

I made some changes to the module so get the latest version - there were some session variable issues regarding the Import Type not being used as selected.

This is exactly what I did and I got Ryan's blog profile installed and a test install of 40 WP blog posts, with tags and categories assigned and users and dates imported.

Started with a clean PW install.

Import the blog.zip with the following settings

  1. Parent Page: Home
  2. Components to Import: Everything
  3. Import Type: Append
  4. Import User Details: Checked
  5. Import Created/Modified Dates: Checked
  6. Data Source: blog.zip

Import wordpress xml file with the following settings

  1. Parent Page: Blog (this parent page was created by the blog.zip import)
  2. Components to Import: Everything
  3. Import Type: Replace
  4. Import User Details: Checked
  5. Import Created/Modified Dates: Checked
  6. Data Source: wordpress.xml

Now that kongondo has released his Blog module (https://processwire.com/talk/topic/6465-module-blog/) I think it would be awesome if Nico's MigratorWorpress was made compatible with the page, template, and field names that kongondo is using, because this will be a much better approach than using the blog.zip import I put together. Perhaps a way to configure the names of these in the module config settings!

Anyway totoff, please let me know if it works for you now. I have run this a few times now and it seems perfect!

  • Like 4

Share this post


Link to post
Share on other sites

Now that kongondo has released his Blog module (https://processwire.com/talk/topic/6465-module-blog/) I think it would be awesome if Nico's MigratorWorpress was made compatible with the page, template, and field names that kongondo is using

Maybe it would make sense if PW would have some metadata inputs for all kinds of data (like it has "tags") so we could have some conventions to make it easier this kind of interactions between modules. Like this we could mark the blog parent page on Ryan's blog profile an Kongondo's blog module with the same meta-name, and the blog pages template also with the same meta-name and the same goes for main fields on blog pages (you get the idea). Like this any importing script could easily target all profiles that would comply to conventions. Hope I explained clearly...

  • Like 4

Share this post


Link to post
Share on other sites

I agree diogo!

Just a small issue for anyone who goes to test the WP import. If you are using TinyMCE on the body field, images won't display in the editor. There is a tiny bug in MigratorWordpress that breaks the valid_elements setting. If you want to test before Nico fixes this, after the import, just replace the valid_elements for the body field with the default settings:

@[id|class],a[href|target|name],strong/b,em/i,br,img[src|id|class|width|height|alt],ul,ol,li,p[class],h2,h3,h4,blockquote,-p,-table[border=0|cellspacing|cellpadding|width|frame|rules|height|align|summary|bgcolor|background|bordercolor],-tr[rowspan|width|height|align|valign|bgcolor|background|bordercolor],tbody,thead,tfoot,#td[colspan|rowspan|width|height|align|valign|bgcolor|background|bordercolor|scope],#th[colspan|rowspan|width|height|align|valign|scope],code,pre

Share this post


Link to post
Share on other sites

Hi adrian,

let me say how much I appreciate the huge effort you put into this. Awesome work!

Unfortunately I dont't have good news regarding my specific case. I get the same results as before with my client's XML-file (I did export it once again to be sure). I again have this misterious warning and categories/tags are not assigned.

However, I suspect something could be wrong with the XML export. If you would like to, please PM me your XML-file an I'll be glad to test it here with my installation in question.

EDIT: Sorry, I forgot the debug mode before importing. Apologies.

  • Like 1

Share this post


Link to post
Share on other sites

You're not making me happy :)

I'll PM you the XML I have been testing with. I don't suppose you'd be able to send me your one as well?

What version of Wordpress are you running - this could be relevant?

I don't think it should matter, but also what version of PW are you running - I have been testing the latest dev.

Share this post


Link to post
Share on other sites

Hi adrian,

PW is 2.4.0

I'll PM you the file. It's published content anyway. Nothing top secret.

WP is 3.8.1 - updates come faster than I can keep up with  :P  

Share this post


Link to post
Share on other sites

Just an update for those following intently :)

Turns out there was a character encoding issue in totoff's WP xml export. WP was url encoding special characters which is why he was getting the selector error. 

Remove that and it all works because that selector error was responsible for the categories/tags assignment problem and the post date stuff as well.

  • Like 4

Share this post


Link to post
Share on other sites

Now that it seems to be that simple to convert from WP to PW, I'm a bit sad that I don't have any WP site. :'(:P

  • Like 2

Share this post


Link to post
Share on other sites

Yeah, I am sure you are distraught :)

Now we just need someone with some Drupal skills to write a MigratorDrupal plugin.

Anyone?

Share this post


Link to post
Share on other sites

Update: Migrator Wordpress 1.3

A lot of bug fixes are contained in this new update but the main change is that you can now adjust field and template names is the module's settings. That means that if you already created fields or templates or started with the blog profile or started with kongondos BlogMarkup you can import data right into the needed position :)

In my testing it worked like a charm with adrian's new version. So go - try it yourself :)

  • Like 8

Share this post


Link to post
Share on other sites

Now that it seems to be that simple to convert from WP to PW, I'm a bit sad that I don't have any WP site. :'(:P

:lol:

You could set up one just for fun. WP is a preferred one-click-solution. Go ahead, it's easy.

  • Like 2

Share this post


Link to post
Share on other sites

@totoff: Not that easy. I tried a friend of mine to set up a blog ant thought WP.con might be a good option because free hosting. And after 20 minutes of struggeling in the backend I told her that we should use Tumblr instead. Now she uses Tumblr :)

Share this post


Link to post
Share on other sites

Update: Migrator Wordpress 1.3

Tried it. Worked like a charm.

@totoff: Not that easy.

I was joking.

  • Like 2

Share this post


Link to post
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 d'Hinnisdaël
      Happy new year, everybody 🥬
      I've been sitting on this Dashboard module I made for a client and finally came around to cleaning it up and releasing it to the wider public. This is how it looks.
      ProcessWire Dashboard

      If anyone is interested in trying this out, please go ahead! I'd love to get some feedback on it. If this proves useful and survives some real-world testing, I'll add this to the module directory.
      Download
      You can find the latest release on Github.
      Documentation
      Check out the documentation to get started. This is where you'll find information about included panel types and configuration options.
      Custom Panels
      My goal was to make it really simple to create custom panels. The easiest way to do that is to use the panel type template and have it render a file in your templates folder. This might be enough for 80% of all use cases. For anything more complex (FormBuilder submissions? Comments? Live chat?), you can add new panel types by creating modules that extend the DashboardPanel base class. Check out the documentation on custom panels or take a look at the HelloWorld panel to get started. I'm happy to merge any user-created modules into the main repo if they might be useful to more than a few people.
       Disclaimer
      This is a pre-release version. Please treat it as such — don't install it on production sites. Just making sure 🍇
      Roadmap
      These are the things I'm looking to implement myself at some point. The wishlist is a lot longer, but those are the 80/20 items that I probably won't regret spending time on.
      Improve documentation & add examples ⚙️ Panel types Google Analytics ⚙️ Add new page  🔥 Drafts 🔥 At a glance / Page counter 404s  Layout options Render multiple tabs per panel panel groups with heading and spacing between ✅ panel wrappers as grid item (e.g. stacked notices) ✅ Admin themes support AdminThemeReno and AdminThemeDefault ✅ Shortcuts panel add a table layout with icon, title & summary ✅ Chart panel add default styles for common chart types ✅ load chart data from JS file (currently passed as PHP array) Collection panel support image columns ✅ add buttons: view all & add new ✅
    • By Pip
      Hi everyone!
      I'm trying out the Login/Register module for my site. Noted that the module assigns the newly registered user to login-register role. 
      Once you modify the login-register role's permissions, particularly adding page-edit, the new member role will be set to guest. 
      Thing is I'd like to grant my new users the power to create their own pages. Any advice? 
      Thanks. 
    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-07-03 -- SnipWire 0.8.7 (beta) released! Fixes some small bugs and adds an indicator for TEST mode 2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  

       
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
×
×
  • Create New...