adrian

Module
Migrator

289 posts in this topic

@manlio - sorry for the rough first experience with Migrator - any chance you could PM me the zip package you are trying to import?

@Septhiroth - good catch, and yes, PR's are always very welcome - thanks :)

1 person likes this

Share this post


Link to post
Share on other sites

Adrian you don't have to be sorry! Instead thanks for you effort that I know is great and thanks for support. I send you a message with the zip file.

Ciao

Share this post


Link to post
Share on other sites

Just wanted to post a little warning here.

@SteveB PM'd me with an issue he was have with a relatively complex migration. I initially tested on PW 2.5.3 and everything worked flawlessly in several tests, which is great!

But then testing on the latest PW dev there were some significant issues with certain pages not ending up where they were supposed to be, so I need to look into this in more detail, but just wanted to remind you guys on dev to be careful until I figure this out. Not sure what version of PW this started happening with.

1 person likes this

Share this post


Link to post
Share on other sites

An update on the status of Migrator with respect to current dev version of PW (soon to be stable 2.7) would be much appreciated!

Reading this thread I get the sense that, understandably, there are plenty of edge case problems but do we know what's working reliably on recent PW installations? I'm piecing together a staging-to-live strategy for a site where most of the content will be imported from non-PW data sources (including images).

One way is to first delete those pages which get imported from the external data, then use the reliable method of copying over the whole database, the site folders (templates and modules) and any necessary config, .htaccess, index.php tweaks. This keeps users, roles, user/role mapping and template access settings intact.

I feel as though a "cleaner" way would be to explicitly export/import users, roles, user/role mapping and all template settings. Then I could start with a clean PW install. How much of that might Migrate be able to do these days?

Thanks,

Steve

Share this post


Link to post
Share on other sites

Hi Steve,

I am sorry, I haven't had time to work on Migrator for a while now. It is definitely not abandoned - I just need to find a good chunk of time to revisit a few things regarding Page fields and sort out remaining bugs. I will try to take a look at this sometime soonish.

Regarding the last part of your question - Migrator currently creates new users/roles if the creator/modifier of the imported content was created by a user that doesn't exist on the new site. The problem of course is migrating the user's password - is this a requirement in your scenario? All the template settings etc are all handled completely by Migrator.

I also have some aspirations to take Migrator a step further and allow it to connect directly to another site and sync changes, but if this happens it will be some time away and will likely be a commercial version of Migrator.

I am not sure if that really helps you at the moment. I am away for the next few days and busy for the week or so after that, but might see if I can get a new version out before the end of the month - but no promises :)

4 people like this

Share this post


Link to post
Share on other sites

Thanks Adrian. I'm just trying to figure out what it might be relied upon to do in it's current, work-in-progress, state. For this project I can probably just build users from scratch each time. The password issue can be dealt with.

Share this post


Link to post
Share on other sites

Hi Adrian

this module looking very good! But i have some strange problems. So export on page tree from one site (whole tree; pw 3.0.15) wich works very well. And I want to import it on PW 3.0.18 System. wich seems to work also well. Templates and fields are created. I also get the info "Created all required templates and fields and imported/edited 140 pages" but if I view on the page tree nothing is there. I dont see any errors. So maybe its because of the 3.0.x version. Do you have tested it with the 3.0.x version?

What else could I try?

Share this post


Link to post
Share on other sites

@jensweigel - please try this commit: https://github.com/adrianbj/ProcessMigrator/tree/3e2121b8fdb68e9d9dc0c6aca8aae75e923a2669

I also have a PR from @jlahijani (https://github.com/adrianbj/ProcessMigrator/pull/5) which may also take care of the problem. I will try to make some time today to review his changes and the last working commit noted above and get a new version out.

Share this post


Link to post
Share on other sites

Seems like Migrator has problems with templates that include InputfieldPageTable fields. When importing pages that include this fieldtype, Migrator also creates the pages that are stored inside this fieldtype.

Share this post


Link to post
Share on other sites
4 hours ago, charger said:

Seems like Migrator has problems with templates that include InputfieldPageTable fields. When importing pages that include this fieldtype, Migrator also creates the pages that are stored inside this fieldtype.

HI @charger - isn't that the desired behavior? If it didn't create the pages that belong to the Page Table then you wouldn't be migrating all the content. Maybe I am misunderstanding though?

Share this post


Link to post
Share on other sites

You’re of course right. The problem is that the pages that reside in these InputfieldPageTable fields will be moved out of their previous (nested) structure and are applied (flat) to the parent one selects during import.

Share this post


Link to post
Share on other sites

I'm trying to use this module to get pages to an external translation agency, that uses a translation memory. The multilanguage modules are in use and working fine. [Added English manually to the Dutch (default) site, trying to add French and German automatically.]

What worked fine:

  • Export of all pages as a json file
  • Import of that json file in their translation software
  • Inspection of their translated json file in Atom - looks fine

Then I tried to import their file, and that failed.

  • Append: nothing changed — expected behaviour
  • Overwrite/Replace: shows me this error
Error: Uncaught Error: Call to a member function setLanguageValue() on null in /Applications/MAMP/htdocs/site/modules/ProcessMigrator/ProcessMigrator.module:1441
Stack trace:
#0 /Applications/MAMP/htdocs/site/modules/ProcessMigrator/ProcessMigrator.module(161): ProcessMigrator->processImportForm2(Object(ProcessWire\InputfieldForm))
#1 /Applications/MAMP/htdocs/wire/core/Wire.php(374): ProcessMigrator->___executeImport()
#2 /Applications/MAMP/htdocs/wire/core/WireHooks.php(698): ProcessWire\Wire->_callMethod('___executeImpor...', Array)
#3 /Applications/MAMP/htdocs/wire/core/Wire.php(402): ProcessWire\WireHooks->runHooks(Object(ProcessMigrator), 'executeImport', Array)
#4 /Applications/MAMP/htdocs/wire/core/ProcessController.php(244): ProcessWire\Wire->__call('executeImport', Array)
#5 /Applications/MAMP/htdocs/wire/core/Wire.php(374): ProcessWire\ProcessController->___execute()
#6 /Applications/MAMP/htdocs/wire/core/WireHooks.php(698): ProcessWire\Wire->_ (line 1441 of /Applications/MAMP/htdocs/site/modules/ProcessMigrator/ProcessMigrator.module) 

 

Share this post


Link to post
Share on other sites

I did some further testing.

When I choose Replace instead of Overwrite, all texts with multi-language input are deleted, including default language.

I even tested with exporting to a zip, and then importing that same zip. Same errors. So, it's not related to what the translator could have done with the files.

Share this post


Link to post
Share on other sites
3 hours ago, mds said:

Inspection of their translated json file in Atom - looks fine

Just because it looks like valid json doesn't mean it's in the correct format for Migrator.

But could you please make sure you are using this version of Migrator: https://github.com/adrianbj/ProcessMigrator/tree/3e2121b8fdb68e9d9dc0c6aca8aae75e923a2669

It is two commits behind, but it looks like some bugs were introduced since that commit.

As an update on this project. I still do want to get back to it, but I am now going to wait until Ryan completes all the new core page migration tools so I can use those new core methods. Will wait and see exactly what functionality he builds and extend from there if needed.

2 people like this

Share this post


Link to post
Share on other sites

Thanks, Adrian. Very grateful. 
That version doesn't spit out the error I mentioned.

I get another error now: the Home-page gets added as a new page on import, but that's something I can manually adjust.

Looking forward to updates on exporting/importing/migrating.
Loving Processwire so far, and it's only early days!

Share this post


Link to post
Share on other sites

Will this module be updated for PW 3.x?

I have problems like: "Call to a member function setLanguageValue() on a non-object"

Line 1441 of ProcessMigrator.module.

Is there a similar working tool for copying local pages (trees) to remote?

Thank you.

Share this post


Link to post
Share on other sites

Hi @theo - this looks related to (https://github.com/adrianbj/ProcessMigrator/issues/4).

What commit are you using? Please try this one (two back from current) - https://github.com/adrianbj/ProcessMigrator/tree/3e2121b8fdb68e9d9dc0c6aca8aae75e923a2669

I will likely recreate this module in the future after Ryan fully implements the new core methods for exporting/importing pages

http://processwire.com/blog/posts/roadmap-2017/

Quote

Tools for exporting and importing of pages. We've got some nice built-in tools for importing and exporting of templates and fields, but not yet for pages. Over the coming year, I'm hoping to add page import/export as well. I'd like to be able to copy/paste a page or group of pages from one server to another.

 

I just don't have the time to put more effort into the current iteration of this, especially given that future versions should make use of the new core features.

2 people like this

Share this post


Link to post
Share on other sites
11 minutes ago, adrian said:

 

Hi @Adrian

Yes, 0.6.9 seems to work better than 0.7.0

Thank you!

1 person likes this

Share this post


Link to post
Share on other sites

Hello all. 

After playing with PW for some time now and having a heavy WP website, I decided to look this morning about a way to migrate WP to PW (how ironically it sounds ;) ). And here I am - trying out the MigratorWordpress.

Downloaded the XML file (18Mb containing around 700 posts and over 5000 comments). Uploaded the file and started the import. At the end, everything went smooth and I was suggested to check the imported pages. I was not surprised to find out that the import only did find some pages but not the posts itself (no offense to the authors for sure). This issue was not new to me as I was trying to import WP to ModX long time ago and ran into it as well. So what helped me at that time was a simple WP plugin caled Post Type Switcher that allowed me to move all the WP posts from custom post type to the default WP posts. After that I was able to import posts and comments almost flawlessly (I say almost, as I still had to go around the posts and clear the short-tag leftovers etc. - which is not an issue). 

As of now, I am testing the same approach to see if that would work again and will report back. My biggest concern is to have the posts properly imported and attached to their comments. I do not mind loosing keywords etc. as I am planning on redoing every post manually but moving comments that way would be an overkill ;)

Share this post


Link to post
Share on other sites

Ok. All custo post types were converted back to standard wordpress posts and then the XML was exported using the Tools->Export feature. Then installed the both required modules - ProcessMigrator and MigratorWordpress and tried to import the posts into a newly created page called Import. Unfortunately it did not work with PW 2.8.5 and blows an error:

Error: Call to a member function get() on a non-object (line 1450 of C:\OpenServer\domains\recipemagician.pw\site\modules\ProcessMigrator\ProcessMigrator.module) 

This error message was shown because: you are logged in as a Superuser. Error has been logged.

I tried with the latest 3.0.55 and it did not work either. Is there any specific version to try with that would seemed to work?

Share this post


Link to post
Share on other sites

Thanks Adrian. Testing it now. Would you recommend using 3.X or 2.X?

Share this post


Link to post
Share on other sites
2 minutes ago, MilenKo said:

Thanks Adrian. Testing it now. Would you recommend using 3.X or 2.X?

Migrator and MigratorWordpress were written for 2.x so that might be safer, but I have used Migrator itself with 3.x without any issues, but I haven't used MigratorWordpress with 3.x yet.

FYI - as I mention above:

On 1/11/2017 at 7:07 AM, adrian said:

As an update on this project. I still do want to get back to it, but I am now going to wait until Ryan completes all the new core page migration tools so I can use those new core methods. Will wait and see exactly what functionality he builds and extend from there if needed.

 

Share this post


Link to post
Share on other sites

Adrian, that is understandable considering the amount of work and changes that needs to be applied. Will try now with 2x version and see how it goes. In regards to the shorcodes, this was one of the things that initially pushed me to search for another CMS. I used a few themes before starting to deal with the next one on my own and with every theme change there were more and more shortcodes used. After the latest theme some were dropped out so it got ugly. That is why all I care is to have the comments and posts imported properly. The rest I will setup up/change/clean myself as a part of the process and learning curve ;)

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 Robin S
      I have had this module sitting in a 95% complete state for a while now and have finally made the push to get it out there. Thanks to @teppo for his Hanna Code Helper module which I referred to and borrowed from during development.
      http://modules.processwire.com/modules/hanna-code-dialog/
      https://github.com/Toutouwai/HannaCodeDialog
      HannaCodeDialog
      A module for ProcessWire CMS/CMF. Provides a number of enhancements for working with Hanna Code tags in CKEditor. The main enhancement is that Hanna tags in a CKEditor field may be double-clicked to edit their attributes using core ProcessWire inputfields in a modal dialog.
      Requires the Hanna Code module.
      Installation
      Install the HannaCodeDialog module using any of the normal methods.
      For any CKEditor field where you want the "Insert Hanna tag" dropdown menu to appear in the CKEditor toolbar, visit the field settings and add "HannaDropdown" to the "CKEditor Toolbar" settings field.
      Module configuration
      Visit the module configuration screen to set any of the following:
      Exclude prefix: Hanna tags named with this prefix will not appear in the CKEditor toolbar dropdown menu for Hanna tag insertion. Exclude Hanna tags: Hanna tags selected here will not appear in the CKEditor toolbar dropdown menu for Hanna tag insertion. Background colour of tag widgets: you can customise the background colour used for Hanna tags in CKEditor if you like. Dialog width: in pixels Dialog height: in pixels Features
      Insert tag from toolbar dropdown menu
      Place the cursor in the CKEditor window where you want to insert your Hanna tag, then select the tag from the "Insert Hanna tag" dropdown.

      Advanced: if you want to control which tags appear in the dropdown on particular pages or templates you can hook HannaCodeDialog::getDropdownTags. See the forum support thread for examples .
      Edit tag attributes in modal dialog
      Insert a tag using the dropdown or double-click an existing tag in the CKEditor window to edit the tag attributes in a modal dialog.

      Tags are widgets
      Hanna tags that have been inserted in a CKEditor window are "widgets" - they have a background colour for easy identification, are protected from accidental editing, and can be moved within the text by drag-and-drop.

      Options for tag attributes may be defined
      You can define options for a tag attribute so that editors must choose an option rather than type text. This is useful for when only certain strings are valid for an attribute and also has the benefit of avoiding typos.
      Add a new attribute for the Hanna tag, named the same as the existing attribute you want to add options for, followed by "__options". The options themselves are defined as a string, using a pipe character as a delimiter between options. Example for an existing attribute named "vegetables":
      vegetables__options=Spinach|Pumpkin|Celery|Tomato|Brussels Sprout|Potato You can define a default for an attribute as normal. Use a pipe delimiter if defining multiple options as the default, for example:
      vegetables=Tomato|Potato Dynamic options
      Besides defining static options as above, you can use one Hanna tag to dynamically generate options for another. For instance, you could create a Hanna tag that generates options based on images that have been uploaded to the page, or the titles of children of the page.
      Your Hanna tag that generates the options should echo a string of options delimited by pipe characters (i.e. the same format as a static options string).
      You will probably want to name the Hanna tag that generates the options so that it starts with an underscore (or whatever prefix you have configured as the "exclude" prefix in the module config), to avoid it appearing as an insertable tag in the HannaCodeDialog dropdown menu.
      Example for an existing attribute named "image":
      image__options=[[_images_on_page]] And the code for the _images_on_page tag:
      <?php $image_names = array(); $image_fields = $page->fields->find('type=FieldtypeImage')->explode('name'); foreach($image_fields as $image_field) { $image_names = array_unique( array_merge($image_names, $page->$image_field->explode('name') ) ); } echo implode('|', $image_names); Advanced: define or manipulate options in a hook
      You can hook HannaCodeDialog::prepareOptions to define or manipulate options for a Hanna tag attribute. Your Hanna tag must include a someattribute__options attribute in order for the hook to fire. The prepareOptions method receives the following arguments that can be used in your hook:
      options_string Any existing string of options you have set for the attribute attribute_name The name of the attribute the options are for tag_name The name of the Hanna tag page The page being edited If you hook after HannaCodeDialog::prepareOptions then your hook should set $event->return to an array of option values, or an associative array in the form of $value => $label.
      Choice of inputfield for attribute
      You can choose the inputfield that is used for an attribute in the dialog.
      For text attributes the supported inputfields are text (this is the default inputfield for text attributes so it isn't necessary to specify it if you want it) and textarea. Note: any manual line breaks inside a textarea are removed because these will break the CKEditor tag widget.
      Inputfields that support the selection of a single option are select (this is the default inputfield for attributes with options so it isn't necessary to specify it if you want it) and radios.
      Inputfields that support the selection of multiple options are selectmultiple, asmselect and checkboxes.
      You can also specify a checkbox inputfield - this is not for attributes with defined options but will limit an attribute to an integer value of 1 or 0.
      The names of the inputfield types are case-insensitive.
      Example for an existing attribute named "vegetables":
      vegetables__type=asmselect Descriptions and notes for inputfields
      You can add a description or notes to an attribute and these will be displayed in the dialog.
      Example for an existing attribute named "vegetables":
      vegetables__description=Please select vegetables for your soup. vegetables__notes=Pumpkin and celery is a delicious combination. Notes
      When creating or editing a Hanna tag you can view a basic cheatsheet outlining the HannaCodeDialog features relating to attributes below the "Attributes" config inputfield.
      Troubleshooting
      HannaCodeDialog includes and automatically loads the third-party CKEditor plugins Line Utilities and Widget. If you have added these plugins to your CKEditor field already for some purpose and experience problems with HannaCodeDialog try deactivating those plugins from the CKEditor field settings.
    • By joshuag
      Introducing our newest [commercial] module:
      Recurme
      Processwire Recurring Dates Field & Custom Calendar Module.
      http://www.99lime.com/modules/recurme/
      One Field to Recur them ALL…
      A Recurring Dates InputField for your Processwire templates. The InputField you’ve been waiting for.
      Complex RRule date repeating in a simple and fast user interface.
      Use the super simple, & powerful API to output them into your templates.
      example:
      <? // easy to get recurring events $events = $recurme->find(); // events for this day $events = $recurme->day(); // events for this week $events = $recurme->week(); // events for this month $events = $recurme->month(); ?> <? // Loop through your events foreach($events as $event){ echo $event->title; echo $event->start_date; echo $event->rrule; echo $event->original->url; ... } ?> Unlimited Custom Calendars.
      Imagine you could create any calendar you wanted on your website. Use recurring events with the Recurme field, or use your own Processwire pages and date fields to render calendars… it’s up to you. Fully customizable. Make as many calendars as you like. Get events from anywhere. Recurme does all the hard date work for you.
      Unlimited Custom Admin Calendars too.
      Hope you like it  ,
       Joshua & Eduardo from 99Lime.
       




    • By valan
      At our site we use both email and phone authorizations at frontend. To make life easier, I've developed HelperPhone pack that handles phone numbers. This pack includes following modules for ProcessWire CMS/CMF:
      FieldtypePhoneNumber: module that stores phone numbers InputfieldPhoneNumber: module that renders inputfield for phone numbers HelperPhone: module that loads PhoneNumber and PhoneNumberConst classes, and 'libphonenumber' namespace All these modules require included PW WireData-derived class PhoneNumber and PhoneNumberConst.
      PhoneNumber class is a thin wrapper over giggsey/libphonenumber-for-php, itself is port of Google's libphonenumber. PhoneNumberConst class stores constants, used by PhoneNumber class Usage: PhoneNumber class
      $phone = '8 (916) 318-07-29 ext 1234'; // input string could be in any phone-recognizable format $phoneNumber = new PhoneNumber($phone, 'RU'); // or wire('modules')->get('HelperPhone')->makePhoneNumber($phone, 'RU'); echo ($phoneNumber->isValidNumber() ? 'Yes':'No'); // Yes echo ($phoneNumber->isValidNumberForRegion($regionCode) ? 'Yes':'No'); // Yes echo $phoneNumber->getNumberTypeTitle(); // Mobile echo $phoneNumber->getCountryCode(); // 7 echo $phoneNumber->getRegionCode(); // RU echo $phoneNumber->getNationalNumber(); // 9163180729 echo $phoneNumber->getExtension(); // 1234 echo $phoneNumber->formatForCallingFrom('US') // 011 7 916 318-07-28 echo $phoneNumber->formatForCallingFrom('GE') // 00 7 916 318-07-28
      For more methods and properties please refer to PhoneNumber and PhoneNumberConst source files. Need more? Check giggsey/libphonenumber-for-php and use it by accessing $phoneNumber->phoneNumber property - it is instance of \libphonenumber\PhoneNumber or null (if empty).
      Usage: field
      Note: on field creation, make sure that you've configured field settings
      Default region: assumed region if input phone number string is not in international format (starts with '+', etc)
      Enabled/disabled phone extentions: if disabled, phone extension will be removed on field save.
      Phone field settings in example below: default region code 'RU', phone extensions are enabled
      echo $page->phone; // +79163180729 // Note1: $page->phone stores instance of PhoneNumber and renders to string in E164 format. // Note2: E164 format does not include extension. echo $page->getFormatted('phone'); // +7 916 318-07-29 ext. 1234 echo $page->getUnformatted('phone'); // +79163180729 echo $page->phone->format(PhoneNumberConst::RFC3966); // tel:+7-916-318-07-29;ext=1234 echo $page->phone->getNationalNumber(); // 9163180729 Usage: PW selectors
      FieldtypePhoneNumber is instance of FieldtypeText. It stores phone numbers and extensions as string in E164 format with #extention (if provided by user and enabled in settings) E.g. in db it looks like this: '+79163180729#1234'. This makes it easy to query fields as any text field.
      echo $pages->find([     'template' => 'my_temlate',     'phone^=' => '+79163180729', ]); // will echo page ids where phone starts with '+79163180729' Finally
      I've decided to put it here first and later to Modules directory (based on your feedbacks).
      GitHub: https://github.com/valieand/HelperPhone
      Enjoy
    • By justb3a
      Little admin helper module: Using this module you can view all template cache settings at once. E.g. cache status, cache time (configurable). Furthermore it adds the functionality to clear the entire template cache or just the template cache for a given template. Note that this may cause a temporary delay for one or more requests while pages are re-cached.

       
      GitHub: https://github.com/justb3a/processwire-templatecacheoverview
    • By Steven Veerbeek
      Hi,
      I am trying to create a module for a webshop in which I can predefine a number of thumbnail sizes for my product images. I was thinking of storing each of these image sizes as a child page with 'width' and 'height' fields under the module page , so I can use a PageTable input field in my module to easily manage them.
      I know how to create a Pagetable field and add it to templates so I can use it in regular pages, but because I am planning on implementing some other functionalities that (I think) can't be achieved with a regular page, I need the PageTable field to work within a module.
      So far I have come up with this piece of code by trial and error:
      $page = $this->page; $field_sizes = $this->modules->get("InputfieldPageTable"); $field_sizes->title = "image_sizes"; $field_sizes->label = "Image sizes"; $field_sizes->set('parent_id', $page->id); $template = wire("templates")->get("image_size"); $field_sizes->set('template_id', $template->id); $field_sizes->set('columns', "title\nimage_width\nimage_height"); $wrapper->add($field_sizes); It works in that it does display an empty PageTable in my module. I can also add pages and they will be added as child pages under my module page, but when I do, the way the PageTable is displayed gets all messed up. Instead of showing the newly created page as a row in the PageTable, all the fields on the module page (including the PageTable field itself) are repeated within the PageTable field.
      I hope my explanation makes sense. I am fairly new to Processwire (and module development in particular) so perhaps I am just trying to use PageTable in a way it was not intended to be. Maybe you guys could give me some directions on how to achieve what I am looking for?
      Thanks!