Jump to content
adrian

Migrator

Recommended Posts

It's definitely getting closer to being ready diogo.

To be honest I hadn't really thought about automatically capturing changes - I kinda thought that was already in the works here:

https://processwire.com/talk/topic/2117-continuous-integration-of-field-and-template-changes/

PTM is structured so that everything that is exported is based on the content of a parent page - all the child pages, templates, fields, page field content pages, etc. So it is designed to migrate new blocks of content. It can certainly update changes to these blocks to a live server too though.

I guess it might be possible to make what you are saying work by using "Home" as the parent page of the export, so changes to the entire site are migrated. The automatic recording of changes so that the JSON file only contains changes is obviously the tricky part :) I'll read through mindplay.dk's experience in detail and see what suggestions I can garner. Off the top of my head I am thinking that maybe a simple approach might work - use the module's config data field to store and add to an array of pages, fields, and templates that change, captured whenever they are saved. That way I am not trying to record exactly what all the changes are, but rather just that something changed and therefore we should add that page/field/template to the list of things that needs to be exported.

I'll think about it some more!

  • Like 4

Share this post


Link to post
Share on other sites

Do you added the hookable stuff we talked about already? :) 

So I could publish my module too :)

Share this post


Link to post
Share on other sites

Hey Nico,

Sorry, I haven't done that yet - I actually thought you had some more stuff to do on your module around image importing and RTE embedding.

I am super busy at the moment, but I'll see if I can get the hookable part sorted out for you in the next few days. Diogo's ideas actually got me a little sidetracked because I really want to add that functionality now too :)

I'll PM you more thoughts to avoid spamming people here.

  • Like 1

Share this post


Link to post
Share on other sites

Sorry for deviating you from your track, but it's great to hear that :)

Share this post


Link to post
Share on other sites

As someone new to Processwire, I just wanted to say what a godsend this module will be. I've just started a new site using PW and Foundation, and was wondering how I could get the blog profile integrated as part of it, without setting up all the data structures and copying code manually, and here you've done it already!

I'll still have to do all the css and a lot of php changes, but this should take care of all the field/template/page setup that I need. I can see lots of other uses for this, as a way to copy/paste bits and pieces from other sites as well.

Should I just use the blog file you've included in this thread, or would it be better to setup a dummy site with the standard blog profile, and use this module to migrate?

Great job!

Share this post


Link to post
Share on other sites

Hi Russell,

Glad you'll find it useful. It's still a bit of a work in progress, but I hope to dedicate some more time to it shortly to get the final pieces in place.

If I were you I would use the blog file included in this thread because it is already modified to work as a child page, rather than needing to be the home page. Then play with the css as needed, ideally taking the blog specific bits from the imported css files and putting them into your main css files and changing the paths in the template files to those main css files. No matter what you do you'll need to make some css changes to match your site.

Good luck and please let us know how you go.

Share this post


Link to post
Share on other sites

OK, I seem to be having a little trouble importing. I've followed the step by step you posted with the blog profile, but it keeps coming back saying

"Missing required parent page. This must be selected if you want to import the pages in addition to field and template creation."

I've tried twice, and I have selected my "Home" page, which is my top level page, 3 times. Even when I just select "fields and templates" it's still giving me the same message.

Just on the question of data or templates, I do want a clean slate, but will just templates give me everything I need to start fresh?

Here's a screenshot of my last attempt

pzAOBKs.png

Share this post


Link to post
Share on other sites

Russell,

Really sorry about that - I made some significant changes to the form processing in the last version and it looks it was having some issues with session variables which is why it wasn't remembering the parent you selected. I have implemented a quick fix and tested the blog install at my end and it seems to be working fine here. I will revisit things properly before the next version, but please test the latest version from github and let me know how it goes.

Thanks.

Share this post


Link to post
Share on other sites

Thanks. Been out today. Will try tomorrow. Can I follow up on the "templates only" option? Would it be better to copy with data, and delete the data, or templates only, and then create the pages myself, using a dummy site to look at a populated version to get an idea of how it all works?

Share this post


Link to post
Share on other sites

You should use the full migration option because you want the parent blog page, the categories and tags parents etc to be created. The blog.zip only comes with 5 posts, 2 categories, and 6 tags, so a full migration and then deletion of that content would be very quick. 

Share this post


Link to post
Share on other sites

Ok just gave it a run. So far it seems like it loaded OK. The first thing that worried me was, I saw it overwrote admin.php, which kind of freaked me out. A couple other top level files it says were loaded too, but are they the ones that have gone into the markup sub-dir?

I also put it under my "articles" pages, but then it put a "blog" sub-page under that. I guess I should have done it at my home page, and then renames blog to articles? Not sure if I need to delete what was imported, and try again at the proper level, or whether it's easier to try and move the blog stuff up a level. That's the PW newbie in me talking, I'm sure a bit of reading will sort that out :)

Share this post


Link to post
Share on other sites

Yeah, no need to freak out, the admin.php that got copies across goes into the markup subdir, so it's all good :)

Ideally it should have been installed into your Home as the parent, which would have created "blog" as a child of home. I would definitely suggest trying by moving blog to have home as its parent, deleting articles and then renaming blog to articles. I think this should work just fine.

Let us know how you go.

I probably need some detailed examples with this module that show just how the structure is copied and installed. That will come (maybe a video even) once I find some time to finalized things.

Great to have you testing things though.

Share this post


Link to post
Share on other sites

Adrian, this is definitely a module a lot of people have been waiting for! Thanks for this!

Adrian, this module sounds more and more useful everytime. Next thing, you will be creating a "recording" mode that collects all changes that happen in PW during a certain period and makes it possible to export them as json to make late changes on published sites really easy! (did that sound like a suggestion?)

+1 for this one. Especially when you’re collaborating with another developer on a project it is hard to keep track with each other’s changes to templates, fields, etc. without passing on countless db dumps with every commit. It would be great to have a module–even if I think it should be a separate and specialized one–documenting such changes in importable text/json/haml files. Similar to migrations used with Rails.

  • Like 1

Share this post


Link to post
Share on other sites

Well I don't have the recording mode done yet, but thanks to Nico we now have the ability to migrate content from a Wordpress site into PW.

Firstly, this module has been renamed - now it is simply: "Migrator" https://github.com/adrianbj/ProcessMigrator so please uninstall your old one and install this new version.

The module now supports 3rd party plugin modules for migrating content from other sources. The first one is: MigratorWordpress: https://github.com/NicoKnoll/MigratorWordpress

Here's what it looks like in action. Not much action in that screenshot I know, but you can see how MigratorWordpress adds in a new data source option (a WordPress xml export file). There are instructions on exporting in the MigratorWordpress readme.

post-985-0-31285300-1400076231_thumb.png

For those of you who still have access to a WordPress site, simply run WP's built in exporter, then import the resulting xml file into Migrator. At the moment the Wordpress site needs to still be live because any embedded images are installed to PW from their full existing URL.

Also if you have ideas for other plugins, please feel free to start coding :) If there is interest I'll write a guide defining what is required for the module to be recognized by Migrator and also about the JSON schema that is required.

So please test out and let us know how things go.

  • Like 10

Share this post


Link to post
Share on other sites

I have added a new option called "Changes since" in the export dialog.

This is very basic at the moment and put together quickly, but it allows you to specify a date/time which will limit the exported json to only content that has changed since then.

It's certainly not the most efficient approach in that it will export the entire page, even if just the content of one field has changed. I don't expect this should be much of an issue, but it might seem wasteful if you have a page with a lot of images or files, but you only changed one small text field, because it will copy all those images/files again.

Unlike most fields, image/file fields have created/modified fields in the DB tables, so I should be able to improve this fairly easy - something for the next version :)

  • Like 1

Share this post


Link to post
Share on other sites

Adrian pointed me to his great module today because I have to migrate a WP blog to PW. I managed to import Ryan's blog profile and with Nico's extension the posts from the WP install.

Unfortunately neither comments nor categories and tags made it from WP to PW - only the posts. Upon export I chose posts->all, categories->all, status->published. I checked the XML file and all data is there as it should but wasn't completely imported to PW.

Any ideas? 

Many thanks!

Share this post


Link to post
Share on other sites

Have you checked if the categories aren't imported or only not assigned?


FYI: Comments aren't working right now but they are WIP

Share this post


Link to post
Share on other sites

totoff,

Thanks for the feedback. I have just taken a look at the test wordpress xml file Nico and I were testing with and compared it to one I exported from a different WP blog and there are differences related to tags and categories.

The test xml we were working with definitely imported both tags and categories correctly and assigned them to posts with an ASM select field perfectly, so I am sure we can get this sorted out. I will probably continue the discussion with Nico via PM, but hopefully we'll get back to you in the next couple of days with a solution.

As far as I know you are the first person to test the WP import functionality so apologies for it not going fully as expected.

Share this post


Link to post
Share on other sites

Hi adrian and nico,

many thanks for your quick and kind replies. Glad that my feedback could be helpful. Unfortunately the XML file is customer data, otherwise I would give it to you for testing purposes.

@nico no, it didn't import the categories neither the tags. I first imported the blog profile successful giving me tags and categories and than the WP-XML. But it left the categories and tags pages untouched.

Share this post


Link to post
Share on other sites

Could you try import it in a clean instalation? Without ryan's blog profile? Normally it should create everything by itself.

Share this post


Link to post
Share on other sites

Well I updated it to the new WXRparser and now it should work. Even if you are using Ryan's Blog profile. Maybe even better with it than without it :)

Share this post


Link to post
Share on other sites

Nico,

not sure if we shouldn't open a new thread for that. Maybe moderation can do this in case this is the wrong place to discuss the WP importer.

However, I did try first on a clean install - with the same result: Only posts, nothing else. Therefore I thought it might have to have the blog profile first in order to install the functionality required.

Do I understand you right, that it - if everything works - the module may not only import the data from WP but will also "install" all required code to run a blog?

Thanks!

Share this post


Link to post
Share on other sites

Nico,

did try on a clean install just a few minutes ago. Got an error. See screenshot.

Got posts, categories and tags imported. Testing.

post-625-0-85777700-1400599061_thumb.png

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 bernhard
      --- Please use RockFinder3 ---
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory (pending approval) If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
    • By Craig
      I've been using Fathom Analytics for a while now and on a growing number of sites, so thought it was about time there was a PW module for it.
      WayFathomAnalytics
      WayFathomAnalytics is a group of modules which will allow you to view your Fathom Analytics dashboard in the PW admin panel and (optionally) automatically add and configure the tracking code on front-end pages.
      Links
      GitHub Readme & documentation Download Zip Modules directory Module settings screenshot What is Fathom Analytics?
      Fathom Analytics is a simple, privacy-focused website analytics tool for bloggers and businesses.

      Stop scrolling through pages of reports and collecting gobs of personal data about your visitors, both of which you probably don't need. Fathom is a simple and private website analytics platform that lets you focus on what's important: your business.
      Privacy focused Fast-loading dashboards, all data is on a single screen Easy to get what you need, no training required Unlimited email reports Private or public dashboard sharing Cookie notices not required (it doesn't use cookies or collect personal data) Displays: top content, top referrers, top goals and more
    • By daniels
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      You can find the Module in the Modules directory and on Github
      It can subscribe, update, unsubscribe & delete a user in a list in Mailchimp with MailChimp API 3.0. It does not provide any forms or validation, so you can feel free to use your own. To protect your users, it does not save any user data in logs or sends them to an admin.
      This module fits your needs if you...
      ...use Mailchimp as your newsletter / email-automation tool ...want to let users subscribe to your newsletter on your website ...want to use your own form, validation and messages (with or without the wire forms) ...don't want any personal user data saved in any way in your ProcessWire environment (cf. EU data regulation terms) ...like to subscribe, update, unsubscribe or delete users to/from different lists ...like the Mailchimp UI for creating / sending / reviewing email campaigns *I have only tested it with PHP 7.x so far, so use on owners risk
      EDIT:
      Since 0.0.4, instructions and changelog can be found in the README only. You can find it here  🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github, thanks!
    • By MoritzLost
      Sorry for the convoluted title. I have a problem with Process modules that define a custom page using the page key through getModuleInfo (as demonstrated in this excellent tutorial by @bernhard). Those pages are created automatically when the module is installed. The problem is that the title of the page only gets set in the current language. That's not a problem if the current language (language of the superuser who is installing the module) is the default language; if it isn't, the Process page is missing a title in the default language. This has the very awkward effect that a user using the backend in the default language (or any other language) will see an empty entry in the setup menu:

      This screenshot comes from my Cache Control module which includes a Process page. Now I realize the description sounds obscure, but for us it's a common setup: We a multiple bilingual sites where the default language is German and the second language is English. While the clients use the CMS in German, as a developer I prefer the English interface, so whenever I install a Process module I get this problem.
      As a module author, is there a way to handle this situation? I guess it would be possible to use post-installation hooks or create the pages manually, but I very much prefer the declarative approach. The page title is already translatable (through the __ function), but of course at the time of installation there is no translation, and as far as I'm aware it's not possible to ship translations with a module so they are used automatically. Could this situation be handled better in the core? I would prefer if the module installation process would always set the title of the Process page in the default language, instead of the language of the current user.
×
×
  • Create New...