Jump to content
adrian

Migrator

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

Share this post


Link to post
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

Share this post


Link to post
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

<wp:post_type>events</wp:post_type>

to

<wp:post_type>post</wp:post_type>

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

Share this post


Link to post
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

Share this post


Link to post
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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
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.

Share this post


Link to post
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

Share this post


Link to post
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:

pages

      >site-management

                            >projects

                                        >page1

                                                 image1.jpg

                                                 image1.0x100.jpg

                                        >page2

                                                  image2.jpg

                                                  image2.0x100.jpg

                                        >page3

                                                  image3.jpg

                                                  image3.0x100.jpg

                                        etc

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

Share this post


Link to post
Share on other sites

@tobaco,

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.

@NooseLadder 

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

Share this post


Link to post
Share on other sites

Hi I downloaded the module today at approx 15:30 GMT. The version from the modules window in admin says Migrator 0.1.1. Is that the latest?

Share this post


Link to post
Share on other sites

Yep, that is the latest. Does exporting a different parent make any difference to having a data.json file in your zip?

Share this post


Link to post
Share on other sites

Hi. I have created a test page under Home and exported using Home as the parent. Unfortunately the JSON file is not in the zip file.  :(

Share this post


Link to post
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?

Share this post


Link to post
Share on other sites

Hi,

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

Share this post


Link to post
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.

Share this post


Link to post
Share on other sites

I got this line in debug tools: 


C:/xampp/htdocs/mysite/site/assets/files/1022/data.json

The folder /1022/ is empty.

Edit: And the zip file does not contain the data.json file.

Edited by NooseLadder

Share this post


Link to post
Share on other sites

Have you checked your file permissions? Maybe /assets/files/ is not writable..


For testing on your local XAMP Server just give assets and its subfolders 777 permission (never do this on live server if possible!)

Share this post


Link to post
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

Share this post


Link to post
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?

Share this post


Link to post
Share on other sites

@tobaco,

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 :)

Share this post


Link to post
Share on other sites

@adrian

thanks for your help!

do you mean with cms user an user named "cms"? there is no user with this name. all other users have at least one role assigned.

"cms" is the path to the backend (changed it from "processwire" to "cms")

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 picarica
      so i am trying to put CustomHooksForVariations.module, a custom module, i am placing it into site/modules direcotry yet my modules page in admin panel gives me errors
      so this is the screen show when i refresh modules, i dont know why the shole hook is written on top of the page :||

      and this next image is when i try to install it, i saw that it is not defiuned modules.php but it shouldnt need to be ?, any ways i dont want to edit site's core just to make one moulde work there has to be a way

    • By David Karich
      ProcessWire InputfieldRepeaterMatrixDuplicate
      Thanks to the great ProModule "RepeaterMatrix" I have the possibility to create complex repeater items. With it I have created a quite powerful page builder. Many different content modules, with many more possible design options. The RepeaterMatrix module supports the cloning of items, but only within the same page. Now I often have the case that very design-intensive pages and items are created. If you want to use a content module on a different page (e.g. in the same design), you have to rebuild each item manually every time.
      This module extends the commercial ProModule "RepeaterMatrix" by the function to duplicate repeater items from one page to another page. The condition is that the target field is the same matrix field from which the item is duplicated. This module is currently understood as proof of concept. There are a few limitations that need to be considered. The intention of the module is that this functionality is integrated into the core of RepeaterMatrix and does not require an extra module.
      Check out the screencast
      What the module can do
      Duplicate multible repeater items from one page to another No matter how complex the item is Full support for file and image fields Multilingual support Support of Min and Max settings Live synchronization of clipboard between multiple browser tabs. Copy an item and simply switch the browser tab to the target page and you will immediately see the past button Support of multiple RepeaterMatrix fields on one page Configurable which roles and fields are excluded Configurable dialogs for copy and paste Duplicated items are automatically pasted to the end of the target field and set to hidden status so that changes are not directly published Automatic clipboard update when other items are picked Automatically removes old clipboard data if it is not pasted within 6 hours Delete clipboard itself by clicking the selected item again Benefit: unbelievably fast workflow and content replication What the module can't do
      Before an item can be duplicated in its current version, the source page must be saved. This means that if you make changes to an item and copy this, the old saved state will be duplicated Dynamic loading is currently not possible. Means no AJAX. When pasting, the target page is saved completely No support for nested repeater items. Currently only first level items can be duplicated. Means a repeater field in a repeater field cannot be duplicated. Workaround: simply duplicate the parent item Dynamic reloading and adding of repeater items cannot be registered. Several interfaces and events from the core are missing. The initialization occurs only once after the page load event Changelog
      2.0.0
      Feature: Copy multiple items at once! The fundament for copying multiple items was created by @Autofahrn - THX! Feature: Optionally you can disable the copy and/or paste dialog Bug fix: A fix suggestion when additional and normal repeater fields are present was contributed by @joshua - THX! 1.0.4
      Bug fix: Various bug fixes and improvements in live synchronization Bug fix: Items are no longer inserted when the normal save button is clicked. Only when the past button is explicitly clicked Feature: Support of multiple repeater fields in one page Feature: Support of repeater Min/Max settings Feature: Configurable roles and fields Enhancement: Improved clipboard management Enhancement: Documentation improvement Enhancement: Corrected few typos #1 1.0.3
      Feature: Live synchronization Enhancement: Load the module only in the backend Enhancement: Documentation improvement 1.0.2
      Bug fix: Various bug fixes and improvements in JS functions Enhancement: Documentation improvement Enhancement: Corrected few typos 1.0.1
      Bug fix: Various bug fixes and improvements in the duplication process 1.0.0
      Initial release Support this module
      If this module is useful for you, I am very thankful for your small donation: Donate 5,- Euro (via PayPal – or an amount of your choice. Thank you!)
      Download this module (Version 2.0.0)
      > Github: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate
      > PW module directory: https://modules.processwire.com/modules/inputfield-repeater-matrix-duplicate/
      > Old stable version (1.0.4): https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate/releases/tag/1.0.4
    • By Robin S
      A new module that hasn't had a lot of testing yet. Please do your own testing before deploying on any production website.
      Custom Paths
      Allows any page to have a custom path/URL.
      Note: Custom Paths is incompatible with the core LanguageSupportPageNames module. I have no experience working with LanguageSupportPageNames or multi-language sites in general so I'm not in a position to work out if a fix is possible. If anyone with multi-language experience can contribute a fix it would be much appreciated!
      Screenshot

      Usage
      The module creates a field named custom_path on install. Add the custom_path field to the template of any page you want to set a custom path for. Whatever path is entered into this field determines the path and URL of the page ($page->path and $page->url). Page numbers and URL segments are supported if these are enabled for the template, and previous custom paths are managed by PagePathHistory if that module is installed.
      The custom_path field appears on the Settings tab in Page Edit by default but there is an option in the module configuration to disable this if you want to position the field among the other template fields.
      If the custom_path field is populated for a page it should be a path that is relative to the site root and that starts with a forward slash. The module prevents the same custom path being set for more than one page.
      The custom_path value takes precedence over any ProcessWire path. You can even override the Home page by setting a custom path of "/" for a page.
      It is highly recommended to set access controls on the custom_path field so that only privileged roles can edit it: superuser-only is recommended.
      It is up to the user to set and maintain suitable custom paths for any pages where the module is in use. Make sure your custom paths are compatible with ProcessWire's $config and .htaccess settings, and if you are basing the custom path on the names of parent pages you will probably want to have a strategy for updating custom paths if parent pages are renamed or moved.
      Example hooks to Pages::saveReady
      You might want to use a Pages::saveReady hook to automatically set the custom path for some pages. Below are a couple of examples.
      1. In this example the start of the custom path is fixed but the end of the path will update dynamically according to the name of the page:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'my_template') { $page->custom_path = "/some-custom/path-segments/$page->name/"; } }); 2. The Custom Paths module adds a new Page::realPath method/property that can be used to get the "real" ProcessWire path to a page that might have a custom path set. In this example the custom path for news items is derived from the real ProcessWire path but a parent named "news-items" is removed:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'news_item') { $page->custom_path = str_replace('/news-items/', '/', $page->realPath); } }); Caveats
      The custom paths will be used automatically for links created in CKEditor fields, but if you have the "link abstraction" option enabled for CKEditor fields (Details > Markup/HTML (Content Type) > HTML Options) then you will see notices from MarkupQA warning you that it is unable to resolve the links.
      Installation
      Install the Custom Paths module.
      Uninstallation
      The custom_path field is not automatically deleted when the module is uninstalled. You can delete it manually if the field is no longer needed.
       
      https://github.com/Toutouwai/CustomPaths
      https://modules.processwire.com/modules/custom-paths/
    • By teppo
      Hey folks!
      I'm happy to finally introduce a project I've been working on for quite a while now: it's called Wireframe, and it is an output framework for ProcessWire.
      Note that I'm posting this in the module development area, maily because this project is still in rather early stage. I've built a couple of sites with it myself, and parts of the codebase have been powering some pretty big and complex sites for many years now, but this should still be considered a soft launch 🙂
      --
      Long story short, Wireframe is a module that provides the "backbone" for building sites (and apps) with ProcessWire using an MVC (or perhaps MVVM... one of those three or four letter acronyms anyway) inspired methodology. You could say that it's an output strategy, but I prefer the term "output framework", since in my mind the word "strategy" means something less tangible. A way of doing things, rather than a tool that actually does things.
      Wireframe (the module) provides a basic implementation for some familiar MVC concepts, such as Controllers and a View layer – the latter of which consists of layouts, partials, and template-specific views. There's no "model" layer, since in this context ProcessWire is the model. As a module Wireframe is actually quite simple – not even nearly the biggest one I've built – but there's still quite a bit of stuff to "get", so I've put together a demo & documentation site for it at https://wireframe-framework.com/.
      In addition to the core module, I'm also working on a couple of site profiles based on it. My current idea is actually to keep the module very light-weight, and implement most of the "opinionated" stuff in site profiles and/or companion modules. For an example MarkupMenu (which I released a while ago) was developed as one of those "companion modules" when I needed a menu module to use on the site profiles.
      Currently there are two public site profiles based on Wireframe:
      site-wireframe-docs is the demo&docs site mentioned above, just with placeholder content replaced with placeholder content. It's not a particularly complex site, but I believe it's still a pretty nice way to dig into the Wireframe module. site-wireframe-boilerplate is a boilerplate (or starter) site profile based on the docs site. This is still very much a work in progress, but essentially I'm trying to build a flexible yet full-featured starter profile you can just grab and start building upon. There will be a proper build process for resources, it will include most of the basic features one tends to need from site to site, etc. --
      Requirements and getting started:
      Wireframe can be installed just like any ProcessWire module. Just clone or download it to your site/modules/ directory and install. It doesn't, though, do a whole lot of stuff on itself – please check out the documentation site for a step-by-step guide on setting up the directory structure, adding the "bootstrap file", etc. You may find it easier to install one of the site profiles mentioned above, but note that this process involves the use of Composer. In the case of the site profiles you can install ProcessWire as usual and download or clone the site profile directory into your setup, but after that you should run "composer install" to get all the dependencies – including the Wireframe module – in place. Hard requirements for Wireframe are ProcessWire 3.0.112 and PHP 7.1+. The codebase is authored with current PHP versions in mind, and while running it on 7.0 may be possible, anything below that definitely won't work. A feature I added just today to the Wireframe module is that in case ProcessWire has write access to your site/templates/ directory, you can use the module settings screen to create the expected directories automatically. Currently that's all, and the module won't – for an example – create Controllers or layouts for you, so you should check out the site profiles for examples on these. (I'm probably going to include some additional helper features in the near future.)
      --
      This project is loosely based on an earlier project called pw-mvc, i.e. the main concepts (such as Controllers and the View layer) are very similar. That being said, Wireframe is a major upgrade in terms of both functionality and architecture: namespaces and autoloader support are now baked in, the codebase requires PHP 7, Controllers are classes extending \Wireframe\Controller (instead of regular "flat" PHP files), implementation based on a module instead of a collection of drop-in files, etc.
      While Wireframe is indeed still in a relatively early stage (0.3.0 was launched today, in case version numbers matter) for the most part I'm happy with the way it works, and likely won't change it too drastically anytime soon – so feel free to give it a try, and if you do, please let me know how it went. I will continue building upon this project, and I am also constantly working on various side projects, such as the site profiles and a few unannounced helper modules.
      I should probably add that while Wireframe is not hard to use, it is more geared towards those interested in "software development" type methodology. With future updates to the module, the site profiles, and the docs I hope to lower the learning curve, but certain level of "developer focus" will remain. Although of course the optimal outcome would be if I could use this project to lure more folks towards that end of the spectrum... 🙂
      --
      Please let me know what you think – and thanks in advance!
    • By tcnet
      PageViewStatistic for ProcessWire is a module to log page visits of the CMS. The records including some basic information like IP-address, browser, operating system, requested page and originate page. Please note that this module doesn't claim to be the best or most accurate.
      Advantages
      One of the biggest advantage is that this module doesn't require any external service like Google Analytics or similar. You don't have to modify your templates either. There is also no JavaScript or image required.
      Disadvantages
      There is only one disadvantage. This module doesn't record visits if the browser loads the page from its browser cache. To prevent the browser from loading the page from its cache, add the following meta tags to the header of your page:
      <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" /> <meta http-equiv="Pragma" content="no-cache" /> <meta http-equiv="Expires" content="0" /> How to use
      The records can be accessed via the Setup-menu of the CMS backend. The first dropdown control changes the view mode. There are 4 different view modes.
      View mode "Day" shows all visits of the selected day individually with IP-address, browser, operating system, requested page and originate page. Click the update button to see new added records. View mode "Month" shows the total of all visitors per day from the first to the last day of the selected month. View mode "Year" shows the total of all visitors per month from the first to the last month of the selected year. View mode "Total" shows the total of all visitors per year for all recorded years. Please note that multiple visits from the same IP address within the selected period are counted as a single visitor.
      Settings
      You can access the module settings by clicking the Configuration button at the bottom of the records page. The settings page is also available in the menu: Modules->Configure->ProcessPageViewStat.
      IP2Location
      This module uses the IP2Location database from: http://www.ip2location.com. This database is required to obtain the country from the IP address. IP2Location updates this database at the begin of every month. The settings of ProcessPageViewStat offers the ability to automatically download the database monthly. Please note, that automatically download will not work if your webspace doesn't allow allow_url_fopen.
      Dragscroll
      This module uses DragScroll. A JavaScript available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability in view mode "Day" to drag the records horizontally with the mouse pointer.
      parseUserAgentStringClass
      This module uses the PHP class parseUserAgentStringClass available from: http://www.toms-world.org/blog/parseuseragentstring/. This class is required to filter out the browser type and operating system from the server request.
      Special Feature
      PageViewStatistic for ProcessWire can record the time a visitor viewed the page. This feature is deactivated by default. To activate open the module configuration page and activate "Record view time". If activated you will find a new column "S." in the records which means the time of view in seconds. With every page request, a Javascript code is inserted directly after the <body> tag. Every time the visitor switches to another tab or closes the tab, this script reports the number of seconds the tab was visible. The initial page request is recorded only as a hyphen (-).
       
×
×
  • Create New...