MilenKo

@adrian I did not care much of the categories as I am planning on completely redoing most of the post information, pictures, tags, categories etc. I noticed that after moving the custom type posts to the standard WP post all the posts got to Uncategorized (the default WP category). During the import I do see the category created and pages have the Uncategorized as their category so my guess is that if everything was OK with the posts and categories, they will be imported properly. One other thing I just noticed is that the tags are also not imported and the field that was automatically created by the module is not allowing to add new tags (need to change a few settings to allow it). Again, reaching to this level is waaay more than I have ever expected so I am sure others would follow switching from WP to PW and enjoying the simplicity and elegance of the code (not to mention the support of the community!) I am PM-ing you the XML and thanking you in advance for looking into it.

Hello @adrian . I installed your updated module and tested to import ONLY THE POSTS export. To be clear, I still needed to convert all custom type posts to the standard Wordpress posts as otherwise it only creates a few empty pages and that is all. I tried to start the import this time with the entire XML so as expected I got an error: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away (in other words it means that the import took quite a time and server gives up). To help the server "survive" I decided to edit the my.cnf changing the wait_timeout from 60 to 6000 and this time it worked fine. Unfortunately the issue still exists with the Home page being renamed and unfortunately it is a page that has some comments in it too. It appears that it does not just import to the parent of the page pointed to the module but straight to home. Another thing I just noticed is that the comments date is not preserved, so most of the comments appear to be posted with a timestamp of the import. It might not be such a big issue, however it won't make much sense to have the page added 3-4 years ago and containing 50-100 comments within the last XX minutes. In other words if the comments timestamp can be fixed and the page that imports into the home properly inserted to the parent, it will be all perfect!

Adrian, you are 100% right and how come I did not think of that earlier. I will export now only the posts, but I am not sure if I do that will the export include the comments too. Will test it right away and see what is happening. One thing is sure though - nobody would care if the name of the old website was imported or not as those settings will have to be changed to apply with PW and new theme. Crossing my fingers and trying it now with the latest version of the Migrator.

Ok. Tried with the whole file and for the testing purposes inside the Home I created a child page WordPress inside of which I created another child calling it Import. Pointed the module to the Import page as parent and thought that this way the Home would not change but would the Wordpress. Well I was wrong - the Home title changed again to the same so for some reason the import grabs a page (probably the first) and imports it to Home. On top of that, if I try to import the whole file, then some of the pages were not imported (those that were originaly as Wordpress pages). Categories list is empty too. After the import in both cases I noticed another error: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'post' in 'field list' along with the message of successful import. So for now importing the XML in chunks works much better and properly includes categories as well as users etc. Even if I will have to recreate the page that is imported in the Home, I am still totally OK but just reporting to make sure others won't be able to move on.

Hello @adrian I tested the importer and got an error. Here are the steps I took and the error to just check if I did everything right or missed something: 1. I cut the whole WordPress file (14-15Mb size) in 6 pieces of 2Mb to make it much smaller and reduce the load etc. as per your instructions. To reduce the size of the file I used a simple app called wxrsplitter that I know worked for WP before. 2. Installed fresh PW 3.0.55 with blank profile and only added ProcessMigrator & MigratorWordpress (I downloaded latest update for ProcessMigrator from the git source but MigratorWordpress was kept the same as I did not se any updated files). 3. Created a page Wordpress and assigned it as parent at the Import page. 4. Selected to import user details. 5. Selected to Import created/modified dates. 6. Choose to automatically download and install missing filetypes. 7. As data source used WordPress Migrator and pointed to the first chunk. The error I got after the import is: Error: Call to a member function eq() on a non-object (line 1704 of C:\OpenServer\domains\recipemagician.pw\site\assets\cache\FileCompiler\site\modules\ProcessMigrator\ProcessMigrator.module) This error message was shown because: you are logged in as a Superuser. Error has been logged. If I refresh the page, then it continued and finished with the informing message of how many pages were imported successfully. The same thing is applied for the rest of the files or if I use the file at once (which by obvious reasons takes more time to import but does not fail other than the error). So I pushed the whole file for the test and was able to import 559 posts as child pages of Wordpress. I checked a few pages with comments and they were all posted in the proper amount and approved with an ability to change the status if needed! It is clear now that all posts were imported. I am unable yet to say would all comments be properly imported but I don't see a reason if one works fine why the rest would not. So will consider that also done perfectly. In regards to the Home page title, it changed again (before it was Home and now is imported a the first page alphabetically added. Because of that it looses its fields and comments (this happened when I imported the XML chunks). Will try now to import the whole file but I doubt that this would happen again. For sure I can preserve the content of the page imported to the Home by creating and adding all the necessary fields to it and reimporting, but just reporting that something is still to be fixed. If a need be, I can provide you with the slices of XML.

Huh, it is true - ideas we could have plenty, but there are only 24 hours in 1 day and they are never enough Thank you again for being so helpful...

Oh, I should be the one thanking you. I was thinking about the post import - would it be possible to do that limitting via the API and some coding versus cutting the posts manually? Saying the import goes in a step of 20, 50 etc. and keeps on doing it until the last one is processed. This way you might import a bigger DB without the need of messing around with the XML.

@adrian Thank you very much for the update and I am glad I helped a bit in the process. I will try to import a few posts first and see how it goes after which I will try to import the whole database. If the posts are imported properly but only one changes the homepage - I can totally live with this, but I understand your point of having that fixed so that it does not affect somebody else using the module. To import the WP to PW I am definitely using the latest PW 3.X with a blank profile. After I do that, I will just need to import my existing profile I have almost finished. But let's do this step by step and at the end we will have a nice and smooth approach. Will let you know as soon as finish both tests.

Btw, thinking of the conversion from WP to PW, it seems like I need to export from the PW profile the pages, images, comments etc. to the theme profile as well so the fun will be on MAX but it worth every effort knowing how many years I have tried to work the things out with WP and how for a really short time I got my first theme (thanks to you and others).

Done

@adrian, I did not import the WP blog directly to homepage but created a page called Import and setup the module to point to it. Somehow I ended up with the home page changed to one of the WP Posts, and inside the include folder I got all the pages with the comments. If you feel like having some time, I would send you the XML archive to try and see if it works for you. Thanks in advance

@adrian Looks like I had some progress by creating a simple template matching most of the field names etcl with the wordpress one. Installed the FieldTypeComments and imported the XML. For an unknown reason the name/content of my home page changed to one of the pages from the import as well as the comments are imported in repeating one commment several times (ex, Comment1 x10, Comment 2 x10 etc.) I know I need to go over every page and make the fields properly so that won't be an issue even if I have to work over all comments in the page, but in the admin of the comments I just see them with Pending status and I am unable to just delete the repeating ones.

I will Adrian. The posts are imported correctly but the comments are not there. This is the only issue. I have a feeling that I might have not set up properly the comments field or something else. There are no issues with sending you the XML file but I would first try to recover the issue myself using your tool and other infos and in case I am failing, will use the Joker

Adrian, thanks for the points. The need to switch the post type is that the themes I used were using custom post types so most of the converters are made to just look into the standard type - posts or else, but not news (for example). Switching the post type is not an issue and is semi automatic (semi, as I had to do around 100 posts at once to avoid the server timeout.) I will google the error and see where would that lead. Even if the pages are not properly inserted, but the comments are assigned to a title, that would fully satisfy my needs. Again, I have planned the post cleanup no matter of the CMS but PW is now my top prefference.

Ok. I installed 2.8.5 with the ProcessMigrator that you suggested + MigratorWordpress. It seemed to surpass the initial error but now after uploading the wordpress XML file is showing me this error: Can't save page 1: /: Selected homepage template cannot be used because it does not define access. After that, going back to the home screen I only see two pages created (Categories & Tags). I noticed that the error above is showing only when I use replace/overwrite. If I choose Append, it was showing that all 571 posts were processed properly but in the pages I did not see them. I decided to try and convert the posts to pages (with comments) and this time I was able to see all the pages created. Now the issue is that I do not see the comments so I guess I should redo the import but setup a template with all the fields created in advance and have them added to a template that would be used for the imported pages. On top of that I did not have installed the comments field module so it seems like it might work once I rethink the whole process again. Do you have any idea how to make replace/overwrite work without the error saving the page? P.S. It looks like if I use Append, there are no comments attached to the page even though I have the module now installed and created a template with all fields that were initially created during the Append. So I need to figure out how to define the access for the selected template and try again.

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

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

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?

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

Hello again, @Robin S . No matter how strange it could sound, I included the jQuery that was provided with the demo folder by moving it to the proper scripts direction and including it in the header of the page. That did not work but including the online version from googleapis or code.jquery.com did the trick. One less task to concur and now the only thing to do is to style it place the rating in the proper location and style it appropriately. But that is a story for another day. I am again extremely thankful to your kind assistance and most of all - the patience Once I have the working code, will share it with the audience here so that we can move forward with the theme.

@Robin S I installed Tracy Debugger to see how it works and how can it help me troubleshoot the issue. To be sure there is no theme/styling issue, I installed the PW default profile and the FieldTypeRate module. Created a new field rating and assigned it to both - home and basic page. Added the rating to _main.php: <main id='main'> <!-- main content --> <div id='content'> <h1><?php echo $title; ?> - <?php echo $page->rating; ?></h1> <?php echo $content; ?> </div> <!-- sidebar content --> <?php if($sidebar): ?> <aside id='sidebar'> <?php echo $sidebar; ?> </aside> <?php endif; ?> </main> Checked with Tracy and was able to see the code inserted in the page source with no errors pointed: But still I see no rating etc. How were you able to make it work? Anything different than the steps I took? The only thing to check is if the plugin might not work with some of the settings of my local server (php version etc.) but I highly doubt everything else would and only that not. Read several times the installation instructions, checked the path to jquery.raty.min.js (clicking on the link opens the file in the browser), see the ratings call, checked the images and they are there too, reinstalled the module on 3 different themes - still nothing. If possible, could you quickly share the steps you took to install the module and make it work as well as which version of php you are usin (just in case to match as close as possible to your setup)?

I am installing Tracy Debugger now, @Robin S You are right that the default debug message is not quite explanatory (especially for beginners). About recipe_rating - it was a typo so the correct is article_rating. I am playing with two themes and confused them. Will see what Tracy has to say about the issue as far as the rating is still not showing. Thanks again for all the clever ideas and willing to share/help.

Thanks for your info, @Robin S That it is exactly what I am looking for, however the issue is that it does not work with me. I installed the module, created a fiield article-rating and added a type Rate. After that I went to the articles-inner.php and put the call to the place I need to show the rating by: <? echo $page->recipe_rating;?> The issue is that I see nothing showing. To make sure it is not with some CSS overlaping or else, I moved the rating call to different places within the page but had no luck (I even tried to export the profile and test the module with PW 2.8.35 as it says works with 2x). Oh, and I commented out the line 66 too. On the admin side, I set 5 stars and set the default score to 3. In the module config, other than that, there is nothing to configure (besides the access, advanced etc.) Am I missing something here?

OK. I spent more than 4-5 hours trying to find a profile that has a rating or to find a working rating module that could be manipulated through FieldType or at least would allow simple voting and I did not found anything so far. There are two modules only that are working on the backend but you need to code your way out to a star interface through which you would push the rating or else. How are you guys accomplishing such a request if you have a theme to work on? It would have been great to see the PW default profile to have implemented comments, ratings and other useful stuff other than the logical API calls to pages, hyperlinking, menus etc.

I just checked the fieldtype-star-rating and it seems like it is not exactly what is needed as far as the module allows you to set a page rating within the admin and show the star numbers on the frontend. For my needs I need to have the reversed function (it would be good to have the rating manipulations from the admin but most important - it should allow visitors/users to vote for the page content). Will be checking now the page-ratings to see how can this be implemented and if it would allow the above mentioned functionality to be achieved.