Jump to content

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

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!

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.

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.

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

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.

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

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
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
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
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
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
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
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.

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  

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

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 FireWire
      Hello community!

      I want to share a new module I've been working on that I think could be a big boost for multi-language ProcessWire sites.

      Some background, I was looking for a way for our company website to be efficiently translated as working with human translators was pretty laborious and a lack of updating content created a divergence between languages. I, and several other devs here, have talked about translation integrations and have recognized the power that DeepL has. DeepL is an AI deep learning powered service that delivers translation quality beyond any automated service available. After access to the API was opened up to the US, I built Fluency, a DeepL translation integration for ProcessWire.
      Fluency brings automated translation to every multi-language field in the admin, and also provides a translation tool allowing the user to translate their text to any language without it being inside a template's field. With Fluency you can:
      Translate any plain textarea or text input Translate any CKEditor content (yes, with markup) Translate page names for fully localized URLs on every page Translate your in-template translation function wrapped strings Translate modules Fluency is free, and now so is DeepL
      Since this module was first built DeepL has introduced free Developer accounts that allow anyone to start using Fluency at zero cost and beginning with the version 0.3.0 release Fluency now supports free DeepL accounts. As of June 2021 DeepL supports translation to 26 languages and continues to offer more!
      Installation and usage is completely plug and play. Whether you're building a new multi-language site, need to update a site to multi-language, or simply want to stop manually translating a site and make any language a one-click deal, it could not be easier to do it. Fluency works by having you match the languages configured in ProcessWIre to DeepL's. You can have your site translating to any or all of the languages DeepL translates to in minutes (quite literally).
      Let's break out the screenshots...
      When the default language tab is shown, a message is displayed to let users know that translation is available. Clicking on each tab shows a link that says "Translate from English". Clicking it shows an animated overlay with the word "Translating..." cycling through each language and a light gradient shift. Have a CKEditor field? All good. Fluency will translated it and use DeepL's ability to translate text within HTML tags. CKEditor fields can be translated as easily and accurately as text/textarea fields.

      Repeaters and AJAX created fields also have translation enabled thanks to a JavaScript MutationObserver that searches for multi-language fields and adds translation as they're inserted into the DOM. If there's a multi-language field on the page, it will have translation added.

      Same goes for image description fields. Multi-language SEO friendly images are good to go.

      Creating a new page from one of your templates? Translate your title, and also translate your page name for native language URLs. (Not available for Russian, Chinese, or Japanese languages due to URL limitations). These can be changed in the "Settings" tab for any page as well so whether you're translating new pages or existing pages, you control the URLs everywhere.

      Language configuration pages are no different. Translate the names of your languages and search for both Site Translation Files (including all of your modules)

      Translate all of the static text in your templates as well. Notice that the placeholders are retained. DeepL is pretty good at recognizing and keeping non-translatable strings like that. If it is changed, it's easy to fix manually.

      Fluency adds a "Translate" item to the CMS header. When clicked this opens up a modal with a full translation tool that lets the user translate any language to any language. No need to leave the admin if you need to translate content from a secondary language back to the default ProcessWire language. There is also a button to get the current API usage statistics. DeepL account owners can set billing limitations via character count to control costs. This may help larger sites or sites being retrofitted keep an eye on their usage. Fluency can be used by users having roles given the fluency-translate permission.

      It couldn't be easier to add Fluency to your new or existing website. Simply add your API key and you're shown what languages are currently available for translation from/to as provided by DeepL. This list and all configuration options are taken live from the API so when DeepL releases new languages you can add them to your site without any work. No module updates, just an easy configuration. Just match the language you configured in ProcessWire to the DeepL language you want it to be associated with and you're done. Fluency also allows you to create a list of words/phrases that will not be translated which can prevent items such as brands and company names from being translated when they shouldn't

       
      Limitations:
      No "translate page" - Translating multiple fields can be done by clicking multiple translation links on multiple fields at once but engineering a "one click page translate" is not feasible from a user experience standpoint. The time it takes to translate one field can be a second or two, but cumulatively that may take much longer (CKEditor fields are slower than plain text fields). There may be a workaround in the future but it isn't currently on the roadmap. No "translate site" - Same thing goes for translating an entire website at once. It would be great, but it would be a very intense process and take a very (very) long time. There may be a workaround in the future but it isn't on the roadmap. No current support for Inline CKEditor fields - Handling for CKEditor on-demand hasn't been implemented yet, this is planned for a future release though and can be done. I just forgot about it because I've never really used that feature personally.. Alpha release - This module is in alpha. Releases should be stable and usable, but there may be edge case issues. Test the module thoroughly and please report any bugs via a Github issue on the repository or respond here. Please note that the browser plugin for Grammarly conflicts with Fluency (as it does with many web applications). To address this issue it is recommended that you disable Grammarly when using Fluency, or open the admin to edit pages in a private window where Grammarly may not be loaded. This is an issue that may not have a resolution as creating a workaround may not be possible. If you have insight as to how this may be solved please visit the Github page and file a bugfix ticket.
      Requirements:
      ProcessWire  3.0+ UIKit Admin Theme That's Fluency in a nutshell. A core effort in this module is to create it so that there is nothing DeepL related hard-coded in that would require updating it when DeepL offers new languages. I would like this to be a future-friendly module that doesn't require developer work to keep it up-to-date.
      The Module Is Free
      This is my first real module and I want to give it back to the community as thanks. This is the best CMS I've worked with (thank you Ryan & contributors) and a great community (thank you dear reader).
      DeepL Developer Accounts
      In addition to paid Pro Developer accounts, DeepL now offers no-cost free accounts. Now all ProcessWire developers and users can use Fluency at no cost.
      Learn more about free and paid accounts by visiting the DeepL website. Sign up for a Developer account, get an API key, and start using Fluency today.
      Download & Feedback
      Download the latest version here
      https://github.com/SkyLundy/Fluency-Translation/archive/main.zip
      Github repository:
      https://github.com/SkyLundy/Fluency-Translation
      File issues and feature requests here (your feedback and testing is greatly appreciated):
      https://github.com/SkyLundy/Fluency-Translation/issues
       
      Thank you! ¡Gracias! Ich danke Ihnen! Merci! Obrigado! Grazie! Dank u wel! Dziękuję! Спасибо! ありがとうございます! 谢谢你!

    • By monollonom
      (once again I was surprised to see a work of mine pop up in the newsletter, this time without even listing the module on PW modules website 😅. Thx @teppo !)
      Github: https://github.com/romaincazier/FieldtypeQRCode
      Modules directory: https://processwire.com/modules/fieldtype-qrcode/
      This is a simple module I made so a client could quickly grab a QR Code of the page's url in the admin.
      There's not much to it for now, but if need be you can output anything using a hook:
      $wire->addHookAfter("FieldtypeQRCode::getQRText", function($event) { $event->return = "Your custom text"; }) You can also output the QR code on your front-end by calling the field:
      echo $page->qr_code_field; The module uses the PHP library QR Code Generator by Kazuhiko Arase. When looking for a way to generate a QR Code in PW I came across @ryan's integration in his TFA module. I'm not very familiar with fieldtype/inputfield module development so I blindly followed @bernhard (great) tutorial and his BaseFieldtypeRuntime. At some point I'll take a deeper look to make a module on my own.
      Some ideas for improvements :
      add the ability to choose what to ouput : page's url / editUrl / file(s) / image(s) / ... allow to output multiple QR codes ?
    • By Chris Bennett
      https://github.com/chrisbennett-Bene/AdminThemeTweaker
      Inspired by @bernhard's excellent work on the new customisable LESS CSS getting rolled into the core soon, I thought I would offer up the module for beta testing, if it is of interest to anyone.

      It takes a different approach to admin styling, basically using the Cascade part of CSS to over-ride default UiKit values.
      Values are stored in ModuleConfig Module creates a separate AdminThemeTweaker Folder at root, so it can link to AdminThemeTweaker.php as CSS AdminThemeTweaker.php reads the module values, constructs the CSS variables then includes the CSS framework Can be switched on and off with a click. Uninstall removes everything, thanks to bernhard's wonderful remove dir & contents function.
      It won't touch your core. It won't care if stuff is upgraded. You won't need to compile anything and you don't need to touch CSS unless you want to.

      It won't do much at all apart from read some values from your module config, work out the right CSS variables to use (auto contrast based on selected backgrounds) and throw it on your screen.
      You can configure a lot of stuff, leave it as it comes (dark and curvy), change two main colors (background and content background) or delve deep to configure custom margins, height of mastheads, and all manner of silly stuff I never use.

      Have been developing it for somewhere around 2 years now. It has been (and will continue to be) constantly tweaked over that time, as I click on something and find something else to do.
      That said, it is pretty solid and has been in constant use as my sole Admin styling option for all of those 2 years.

      If nothing else, it would be great if it can provide any assistance to @bernhard or other contributor's who may be looking to solve some of the quirkier UiKit behavior.
      Has (in my opinion) more robust and predictable handling of hidden Inputfields, data-colwidths and showIf wrappers.
      I am very keen to help out with that stuff in any way I can, though LESS (and any css frameworks/tools basically) are not my go.
      I love CSS variables and banging-rocks-together, no-dependency CSS you can write with notepad.



       

    • By opalepatrick
      I see old posts saying that repeaters are not the way to go in Custom Process Modules. If that is the case, when using forms (as I am trying to do) how would one tackle things like repeat contact fields where there can be multiple requirements for contact details with different parameters? (Like point of contact, director, etc) or even telephone numbers that have different uses?
      Just for background I am creating a process module that allows me to create types of financial applications in the admin area (no need to publish any of this, pure admin) that require a lot of personal or company information.
      Maybe I am thinking about this incorrectly?
    • By HMCB
      I ran across a reference to IftRunner module. The post was 6 years ago. I cant find it in available modules. Has it been pulled?
×
×
  • Create New...