CMSCritic Development Case Study

[ryan]

Since you guys asked for it, I'll take a stab at a case study on the development process. Most of the development was done in about a week and a half. I started with the basic profile, but it ended up being something somewhat similar to the Blog profile in terms of how it's structured. Below I'll cover some details on the biggest parts of the project, which included data conversion, the template structure, the front-end development and anything else I can think of. 

Data Conversion from WordPress to ProcessWire

One of the larger parts of the project was converting all of the data over from WordPress to ProcessWire. I wrote a conversion script so that we could re-import as many times as needed since new stories get added to cmscritic.com almost daily. In order to get the data out of WordPress, I queried the WordPress database directly (my local copy of it anyway) to extract what we needed from the tables wp_posts for the blog posts and pages, and then wp_terms, wp_term_relationships, and wp_term_taxonomy for the topics and tags.

WordPress stores its TinyMCE text in a state that is something in between text and HTML, with the most obvious thing being that there are no <p> tags present in the wp_posts database. Rather than trying to figure out the full methodology behind that, I just included WP's wp-formatting.php file and ran the wpautop() function on the body text before inserting into ProcessWire. I know a lot of people have bad things to say about WordPress's architecture, but I must admit that the fact that I can just include a single file from WordPress's core without worrying about any other dependencies was a nice situation, at least in this case. 

In order to keep track of the WordPress pages imported into ProcessWire through repeat imports, I kept a "wpid" field in ProcessWire. That just held the WordPress post ID from the wp_posts table. That way, when importing, I could very easily tell if we needed to create a new page or modify an existing one. 

Another factor that had to be considered during import was that the site used a lot of "Hana code", which looked like [hana-code-insert name="something" /]. I solved this by making our own version of the Hanna code module, which was posted earlier this week.

Here's an abbreviated look at how to import posts from WordPress to ProcessWire: 

$wpdb = new PDO("mysql:dbname=wp_cmscritic;host=localhost", "root", "root", 
  array(PDO::MYSQL_ATTR_INIT_COMMAND => "SET NAMES 'UTF8'"));

$posts = wire('pages')->get('/posts/');

$sql = "
  SELECT * FROM wp_posts 
  WHERE post_type='post' 
  AND post_status='publish' 
  ORDER BY post_date
  ";

$query = $wpdb->prepare($sql);
$query->execute();

while($row = $query->fetch(PDO::FETCH_ASSOC)) {
  
  $post = $posts->child("wpid=$row[ID]"); // do we already have this post?
  
  if(!$post->id) {
    // create a new post
    $post = new Page();
    $post->template = 'post';
    $post->parent = $posts;
    echo "Creating new post...\n";
  }
  
  $post->of(false);
  $post->name = wire('sanitizer')->pageName($row['post_name']);
  $post->title = $row['post_title'];
  $post->date = $row['post_date'];
  $post->summary = $row['post_excerpt'];
  $post->wpid = $row['ID'];
  
  // assign the bodycopy after adding <p> tags
  // the wpautop() function is from WordPress /wp-includes/wp-formatting.php
  $post->body = wpautop($row['post_content']);
  
  $post->save();
  echo "Saved post: $post->path\n";
}

What I've left out here is the importing of images, topics, tags, and setting the correct authors for each post. If anyone is interested, I'll be happy to go more in depth on that, but didn't want to overwhelm this message with code. 

Template File Structure

This site makes use of the $config->prependTemplateFile to automatically include the file _init.php before rendering a template file, and $config->appendTemplateFile to automatically include the file _main.php after. So the /site/config.php has this:

$config->prependTemplateFile = '_init.php';
$config->appendTemplateFile = '_main.php';

You may recognize this as being the same setup from the Skyscrapers profile. The _init.php includes files containing functions we want to be available to all of our templates, and set default values for the regions we populate: 

/site/templates/_init.php

/**
 * Include function and hook definition files
 *
 */
require_once("./includes/render.php");
require_once("./includes/hooks.php");

/**
 * Initialize variables populated by templates that get output in _main.php
 *
 */
$browserTitle = $page->get('browser_title|title');
$body = "<h1>" . $page->get('headline|title') . "</h1>" . $page->body;
$side = '';
$renderMain = true; // whether to include the _main.php file

The includes/render.php file that is included above includes several functions for generating markup of navigation and post summaries, or any other shared markup generation functions. Examples are renderPost(), renderNav(), renderTags(). This is similar to the blog.inc file from the Blog profile except that I'm letting these functions generate and return their own markup rather than splitting them into separate view files. I personally find this easier to maintain even if it's not as MVC. 

The includes/hooks.php sets up any hooks I want to be present for all of my templates. I could have also done this with an autoload module, but found this to just be a little simpler since my hooks were only needed on the front-end. The main hook of interest is one that makes all posts look like they live off the root "/" level rather than "/posts/" (where they actually live). This was in order to keep consistency with the URLs as they were in WordPress, so that the new site would have all the same URL as the old site, without the need for 301 redirects. 

 

/site/templates/includes/hooks.php

/**
 * This hook modifies the default behavior of the Page::path function (and thereby Page::url)
 *
 * The primary purpose is to redefine blog posts to be accessed at a URL off the root level
 * rather than under /posts/ (where they actually live). 
 *
 */
wire()->addHookBefore('Page::path', function($event) {
  $page = $event->object;
  if($page->template == 'post') {
    // ensure that pages with template 'post' live off the root rather than '/posts/'
    $event->replace = true;
    $event->return = "/$page->name/";
  }
}); 

Our /site/templates/_main.php contains the entire markup for the overall template used site wide, from <html> to </html>. It outputs those variables we defined in _init.php in the right places. For example, $body gets output in the <div id='bodycopy'>, $side gets output in the right <aside>, and $browserTitle gets output in the <title> tag.

/site/templates/_main.php

<?php if($renderMain): ?>
<html>
  <head>
    <title><?=$browserTitle?></title>
  </head>
  <body>
    <div id='masthead'>
       // ...
    </div>
    <div id='content'>
      <div id='bodycopy'><?=$body?></div>
      <aside id='sidebar'><?=$side?></aside>
    </div>
    <footer>
      // ...
    </footer>
  </body>
</html>
<?php endif; ?>

We use the rest of the site's template files to simply populate those $body, $side and $browserTitle variables with the contents of the page. As an example, this is an abbreviated version of the /site/templates/post.php template: 

/site/templates/post.php

// functions from /site/templates/includes/render.php
$meta = renderMeta($page); 
$tags = renderTags($page); 
$authorBox = renderAuthor($page->createdUser); 
$comments = renderComments($page); 

$body = "
  <article class='post post-full'>
    <header>
      <h1>$page->title</h1>
      $meta
    </header>
    $page->body
    $tags
    $authorBox
    $comments
  </article>
  ";

if(count($page->related)) {
  $side = "<h4>Related Stories</h4>" . renderNav($page->related);
}

What might also be of interest is the homepage template, as it handles the other part of routing of post URLs since they are living off the root rather than in /posts/. That means the homepage is what is triggering the render of each post:

/site/templates/home.php

if(strlen($input->urlSegment2)) {
  // we only accept 1 URL segment here, so 404 if there are any more
  throw new Wire404Exception();

} else if(strlen($input->urlSegment1)) {
  // render the blog post named in urlSegment1 
  $name = $sanitizer->pageName($input->urlSegment1);
  $post = $pages->get("/posts/")->child("name=$name");
  
  if($post->id) echo $post->render();
    else throw new Wire404Exception();
  
  // tell _main.php not to include itself after this
  $renderMain = false;

} else {
  // regular homepage output
  $limit = 7; // number of posts to render per page
  $posts = $pages->find("parent=/posts/, limit=$limit, sort=-date");
  $body = renderPosts($posts); 
}

The rest of the site's template files were handled in the same way. Though most were a little simpler than this. Several were simply blank, since the default values populated in _init.php were all that some needed. 

Front-end development using Foundation 4

The front-end was developed with the Foundation 4 CSS framework. I started with the Foundation blog template and then tweaked the markup and css till I had something that I thought was workable. Then Mike and I sent the _main.php template file back and forth a few times, tweaking and changing it further. There was no formal design process here. It was kind of a photoshop tennis (but in markup and CSS) where we collaborated on it equally, but all under Mike's direction. After a day or two of collaboration, I think we both felt like we had something that was very good for the reader, even if it didn't originate from a design in Photoshop or some other tool like that. I think it helps a lot that Foundation provides a great starting point and lends itself well to fine tuning it the way you want it. I also felt that the mobile-first methodology worked particularly well here. 

Comments System using Disqus

 

We converted the comments system over to Disqus while the site was still running WordPress. This was done for a few reasons: Disqus comments provide one of the best experiences for the user, in my opinion. They also are platform agnostic, in that we could convert the whole site from WP to PW and not have to change a thing about the comments… no data conversion or importing necessary. Lastly, ProcessWire's built-in comments system is not quite as powerful as WordPress's yet, so I wanted cmscritic.com to get an upgrade in that area rather than anything else, and Disqus is definitely an upgrade from WP's comments. In order to ensure that Disqus could recognize the relations of comment threads to posts, we again made use of that $page->wpid variable that keeps the original WordPress ID, and also relates to the ID used by the Disqus comments. This is only for posts that originated in WordPress, as new posts use a ProcessWire-specific ID. 

[cmscritic]

A truly epic write up Ryan. I'm sure all those who visit this forum will benefit from your knowledge. Thanks for sharing it.

[DaveP]

Just clicking 'Like' doesn't seem enough.

Ryan, you make it all sound so easy.

[kongondo]

Massive! Thanks for the write-up Ryan! I'm especially intrigued by the import script and the URL hook.

[cmscritic]

I feel like a padawan learning from Yoda..  ;P

#lamestarwarsreferenceforthewin

[bcartier]

This is great stuff! 

I'd love to see some additional detail about how you managed images, topics, tags and assigning authors. I have a few big sites to migrate.

I'd also love to see your take on managing page references for related content, if applicable.

Thanks for sharing!

-Brent

[renobird]

  On 6/6/2013 at 2:44 PM, ryan said:

Most of the development was done in about a week and a half.

Let that sink in. 

Ryan, I can't absorb the knowledge you share fast enough — thank you!

 

[ryan]

  Quote

I'd love to see some additional detail about how you managed images, topics, tags and assigning authors. I have a few big sites to migrate.

I'll cover these each separately. First I'll start with the images, and will come back to the others a little later when I've got more time.  

WordPress really only uses images for placement in body copy, so I extracted the links to them right out of there and imported them that way. I did this after the pages had already been imported. In order to keep track of which images had already been imported (so that I could feasibly run the importer multiple times without getting duplicate images), I turned on ProcessWire image "tags" option, and stored the original filename in there. Here's the function I used, which I've used many different variations of over the years with different sites. You basically just give it a $page you've already imported (but is still linking to the old site's images) and it converts the images linked in the body copy from the old site to the new. 

function importImages(Page $page) {
  
  if(!$page->id) return 'You need to save this page first';
  
  $out = '';
  $body = $page->body;
  
  // find all images reference in the 'body' field
  $regex = '{ src="(http://www.cmscritic.com/wp-content/uploads/[^"]+)"}'; 
  if(!preg_match_all($regex, $body, $matches)) return $out;
 
  foreach($matches[0] as $key => $fullMatch) {
  
    $url = $matches[1][$key]; // image URL
    $tag = basename($url); // image filename
    $tag = wire('sanitizer')->name($tag); // sanitized filename
    $image = $page->images->getTag($tag); // do we already have it?
  
    if(!$image) {
      // we don't already have this image, import it
      try {
        $page->images->add($url);
      } catch(Exception $e) {
        $out .= "<div>ERROR importing: $url</div>";
        continue;
      }
      $numAdded++;
      $image = $page->images->last(); // get image that was just added
      $status = "NEW";
    } else {
      $status = "Existing";
    }
  
    $image->tags = $tag; 
    // replace old image URL with new image URL
    $body = str_replace($url, $image->url, $body);
    // report what we did 
    $out .= "<div>$status: $image->basename</div>";
  }
 
  // assign the updated $body back to the page
  $page->body = $body;
 
  // return a printable report of what was done
  return $out;
}

[ryan]

Topics and tags: The first step was to create the parent pages and templates for these. For topics, there were only a few of them, so I created all the category pages ahead of time. On the other hand, with tags, there are 2000+ of those, so those are imported separately. Here are the manual steps that I performed in the PW admin before importing topics and tags: 

1. Created template "topics" and page /topics/ that uses this template. 
2. Created template "topic" and 6 topic pages that use it, like /topics/cms-reviews/ for example.
3. Created Page reference field "topics" with asmSelect input, set to use parent /topics/ and template "topic". 
4. Created template "tags" and page /tag/ that uses this template. Note that I used /tag/ as the URL rather than /tags/ for consistency with the old WordPress URLs. Otherwise I would prefer /tags/ as the URL for consistency with the template name. 
5. Created template "tag".
6. Created Page reference field "tags" with PageAutocomplete input, set to use parent /tag/ and template "tag". I also set this one to allow creating of new pages from the field, so the admin can add new tags on the fly. 
7. Added the new "topics" and "tags" fields to the "post" template. 

With all the right templates, fields and pages setup, we're ready to import. WordPress stores the topics, tags and the relationships of them to posts in various tables, which you'll see referenced in the SQL query below. It took some experimenting with queries in PhpMyAdmin before I figured it out. But once I got the query down, I put it in a function called importTopicsAndTags(). This function needs a connection to the WordPress database, which is passed into the function as $wpdb. For more details on $wpdb, see the first post in this thread. 

/**
 * Import WordPress topics and tags to ProcessWire
 *
 * This function assumes you will do your own $page->save(); later. 
 *
 * @param PDO $wpdb Connection to WordPress database
 * @param Page $page The ProcessWire "post" page you want to add topics and tags to. 
 *     This page must have a populated "wpid" field. 
 * @return string Report of what was done. 
 *
 */
function importTopicsAndTags(PDO $wpdb, Page $page) {
  $out = '';
  $sql = <<< _SQL
 
  SELECT wp_term_relationships.term_taxonomy_id, wp_term_taxonomy.taxonomy, 
  wp_term_taxonomy.description, wp_terms.name, wp_terms.slug
  FROM wp_term_relationships
  LEFT JOIN wp_term_taxonomy 
    ON wp_term_taxonomy.term_taxonomy_id=wp_term_relationships.term_taxonomy_id
  LEFT JOIN wp_terms 
    ON wp_terms.term_id=wp_term_taxonomy.term_id
  WHERE wp_term_relationships.object_id=$page->wpid
  ORDER BY wp_term_relationships.term_order
 
_SQL;
 
  $query = $wpdb->prepare($sql);
  $query->execute();
 
  while($row = $query->fetch(PDO::FETCH_ASSOC)) {
 
    if($row['taxonomy'] == 'category') {
      // this is a topic: find the existing topic in PW
      $topic = wire('pages')->get("/topics/$row[slug]/");
      if($topic->id) {
        // if $page doesn't already have this topic, add it
        if(!$page->topics->has($topic)) $page->topics->add($topic);
        // report what we did
        $out .= "<div>Topic: $topic->title</div>";
      }
 
    } else if($row['taxonomy'] == 'post_tag') {
      // this is a tag: see if we already have it in PW
      $tag = wire('pages')->get("/tag/$row[slug]/");
      if(!$tag->id) {
        // we don't already have this tag, so create it 
        $tag = new Page();
        $tag->template = 'tag';
        $tag->parent = '/tag/';
        $tag->name = $row['slug'];
        $tag->title = $row['name'];
        $tag->save();
      }
      // if $page doesn't already have this tag, add it
      if(!$page->tags->has($tag)) {
        $page->tags->add($tag);
        $out .= "<div>Tag: $tag->title</div>";
      }
    }
  }
 
  return $out;
}
 

[MatthewSchenker]

Greetings,

I have been following this discussion -- an excellent example of a case study with highlights of how to accomplish several key goals in ProcessWire.

This last post highlights a couple of interesting points for me:

1. Emphasizes the advantage of having everything exist as a page in ProcessWire (in this case, tags).

2. How easy it is to use the API to implement functions that take care of major actions in ProcessWire.

3. How to migrate an existing CMS to ProcessWire. Might be dangerous if more people in the WordPress community knew about it!

Regarding 3: I come from the Joomla world. It seems that WordPress databases are more logical than Joomla databases. I think the migrate script for Joomla would be much more involved because simple "page" data is very fragmented in that CMS. But the same principles would apply.

As always, a very illuminating discussion!

Thanks,

Matthew

[ryan]

For authors, there were only about 6 of them at import time, so I created the authors as users in PW manually. I also added the "wpid" field to the "user" template, and populated the value of that manually. That was easy to find in WordPress just by editing the author and noting the ID in the URL. The WordPress wp_posts table has a field in it called post_author, which is the ID of the author. So assuming we've got a user in ProcessWire with a "wpid" that matches up to that, it's easy for us to assign the right PW user to each post. You'll see how this takes place in the code below.

Wrapping it up

Here is the same "import" code as in the first post, but I added all the code accounting for authors, topics, tags, and images back into it. This all just goes in a ProcessWire template file, and viewing the page triggers the import. Because it's aware of stuff that is already imported, it can be run multiple times without causing duplication. 

<!DOCTYPE html>
<html lang="en">
<head>
  <meta http-equiv="content-type" content="text/html; charset=utf-8" />
  <title>Import Posts</title>
</head>
<body>
  <table border='1' width='100%'>
  <thead>
    <tr>
      <th>New?</th>
      <th>ID</th>
      <th>Author</th>
      <th>Date</th>
      <th>Name</th>
      <th>Title</th>
      <th>Images</th>
      <th>Topics</th>
      <th>Changes</th>
    </tr>
</thead>
<tbody>
<?php
 
// get access to WordPress wpautop() function
include("/path/to/wordpress/wp-includes/formatting.php"); 
 
$wpdb = new PDO("mysql:dbname=wp_cmscritic;host=localhost", "user", "pass", 
  array(PDO::MYSQL_ATTR_INIT_COMMAND => "SET NAMES 'UTF8'"));
 
$posts = wire('pages')->get('/posts/');
 
$sql = "
  SELECT * FROM wp_posts 
  WHERE post_type='post' 
  AND post_status='publish' 
  ORDER BY post_date
  ";
 
$query = $wpdb->prepare($sql);
$query->execute();
 
while($row = $query->fetch(PDO::FETCH_ASSOC)) {
  
  $post = $posts->child("wpid=$row[ID]"); // do we already have this post?
  
  if(!$post->id) {
    // create a new post
    $post = new Page();
    $post->template = 'post';
    $post->parent = $posts;
    echo "Creating new post...\n";
  }
  
  $post->of(false);
  $post->name = wire('sanitizer')->pageName($row['post_name']);
  $post->title = $row['post_title'];
  $post->date = $row['post_date'];
  $post->summary = $row['post_excerpt'];
  $post->wpid = $row['ID'];
 
  // find the post author
  $author = wire('users')->get("wpid=$row[post_author]");
  // if we don't have this post author, assign one (Mike)
  if(!$author->id) $author = wire('users')->get("mike");
  // set the post author back to the page
  $post->createdUser = $author;
  
  // assign the bodycopy after adding <p> tags
  // the wpautop() function is from WordPress /wp-includes/wp-formatting.php
  $post->body = wpautop($row['post_content']);
 
  // give detailed report about this post
  echo "<tr>" .
       "<td>" . ($post->id ? "No" : "Yes") . "</td>" .
       "<td>$row[ID]</td>" .
       "<td>$row[post_author]</td>" .
       "<td>$row[post_date]</td>" .
       "<td>$row[post_name]</td>" .
       "<td>$row[post_title]</td>" .
       "<td>" . importImages($post) . "</td>" .
       "<td>" . importTopicsAndTags($wpdb, $post) . "</td>" .
       "<td>" . implode('<br>', $post->getChanges()) . "</td>" .
       "</tr>";
 
  $post->save();
 
}
 
function importTopicsAndTags(PDO $wpdb, Page $page) {
  // see implementation in previous post
}
 
function importImages(Page $page) {
  // see implementation in previous post
}
 
?>
</tbody>
</table>
</body>
</html>
 

[ryan]

This hasn't been asked, but wanted to cover how the permissions and publish workflow work on the site. It has a very simple, though nice setup, where authors can submit new posts but can't edit already published posts, nor can they edit unpublished posts by other authors. It enables Mike to have full control over any content that gets published on the site, while still allowing easy submission and edits for the authors.

Post workflow

All of the authors have a role called "author" with page-edit permission.

On the "post" template, the boxes for "edit" and "create" are checked for this "author" role. 

This site also makes use of the page-publish permission, which is an optional one in ProcessWire that you can add just by creating a new permission and naming it "page-publish". Once present, it modifies the behavior of the usual page-edit permission, so that one must also have page-publish in order to publish pages or edit already published pages.

The "author" role does not have page-publish permission. As a result, authors on the site can submit posts but can't publish them. Nor can they edit already published posts. In this manner, Mike has final say on anything that gets posted to the site. 

Post ownership

The default behavior in ProcessWire is that the Role settings control all access... meaning all users with role "author" would be able to do the same things, on the same pages. In this case, we don't want one author to be able to edit an unpublished/pending post created by another author. This was easily accomplished by adding a hook to /site/templates/admin.php:

/**
 * Prevent users from being able to edit pages created by other users of the same role
 *
 * This basically enforces an 'owner' for pages
 *
 */
wire()->addHookAfter('Page::editable', function($event) {
  if(!$event->return) return; // already determined user has no access
  if(wire('user')->isSuperuser()) return; // superuser always allowed
  $page = $event->object; 
  // if user that created the page is not the current user, don't give them access
  if($page->createdUser->id != wire('user')->id) $event->return = false; 
}); 

Planned workflow improvements

Currently an author has to let Mike know "hey my article is ready to be published, can you take a look?". This is done by email, I'm assuming. An addition I'd like to make is to add a Page reference field called "publish_status" where the author can select from: 

• DRAFT: This is a work in progress (default)
• PUBLISH: Ready for review and publishing
• CHANGE: Changes requested - see editor notes
• DELETE: Request deletion

Beyond that, there is also an "editor_notes" text field that only appears in the admin. It's a place where Mike and the author can communicate, if necessary, about the publish status. This editor_notes field doesn't appear on the front-end of the site. 

All this can be done in ProcessWire just by creating a new field and adding these as selectable page references. That's easy enough, but I want to make it so that it notifies both Mike (the reviewer) and the author by email, every time there is a change in publish status or to the editor_notes. This will be done via another hook in the /site/templates/admin.php: 

wire()->addHookAfter('Page::saveReady', function($event) {
  // get the page about to be saved
  $page = $event->arguments(0);

  // if this isn't a post, don't continue
  if($page->template != 'post' || !$page->id) return;

  // if this post wasn't made by an "author" don't continue
  if(!$page->createdUser->hasRole('author')) return;

  $subject = '';
  $message = '';

  if($page->isChanged('publish_status') || $page->isChanged('editor_notes')) {
    // the publish status or editor notes have changed
    $subject = "CMSCritic post publish status";
    $notes = $page->isChanged('editor_notes') ? "Notes: $page->editor_notes" : "";
    $message = "
      Title: $page->title\n
      URL: $page->httpUrl\n
      Status: {$page->publish_status->title}\n
      $notes
      ";

  } else if($page->isChanged('status') && !$page->is(Page::statusUnpublished)) {
    // page was just published
    $subject = "CMSCritic post published";
    $message = "The post $page->httpUrl has been published!";
  }

  if($message) {
    $reviewer = wire('users')->get('mike'); 
    $author = $page->createdUser; 
    mail("$reviewer->email, $author->email", $subject, $message); 
    $this->message("Email sent: $subject"); 
  }

}); 
 

Mike, if you are reading this, does this sound useful to you? 

[cmscritic]

Sounds awesome. Let's make it happen!

[ryan]

CMSCritic just launched another part of the site which is a directory of CMS products (powered by ProcessWire of course). Hope you guys enjoy: http://www.cmscritic.com/dir/

While you are there, maybe click the "like" button for ProcessWire if you are so inclined.  

[apeisa]

It looks and works great on mobile! It has all the possibilities to become very popular. Good luck!

[cmscritic]

  On 8/22/2013 at 6:29 PM, apeisa said:

It looks and works great on mobile! It has all the possibilities to become very popular. Good luck!

Glad you like it. Ryan's a code genius so it's better than I was hoping for.

[horst]

Note: when I try use the filter, I don't get PW with: /dir/cms/free/php/
only with: /dir/cms/open-source/php/

There are other open source cms also listed with the free filter, PW not. Why?

[cmscritic]

It was missing a couple of flags. I've fixed it. Thanks for pointing that out.

[pwired]

  Quote

Data Conversion from WordPress to ProcessWire

Respect if one can accomplish such a coding job.

[MECU]

I'm having trouble with dates coming over properly. All the dates are getting set to the current time of import, which is obviously not useful.On line 53 of the revised code, you have:
 

$post->date = $row['post_date'];

But I don't see the date method in the $page documentation. I tried:
 

$post->created = strtotime($row['post_date']);
$post->modified = strtotime($row['post_modified']);

But with the same results. Any suggestions?
 

---

Also, for others attempting this, I encountered this tidbit that may be useful to you:
The SQL to get the data starts:

  SELECT * FROM wp_posts 

But I had modified my WordPress table definition prefix for security reasons (like everyone should have), so I had to change wp_posts to wp_xxx_posts

That threw me for half an hour.

[Martijn Geerts]

date is a field.

[MECU]

Seems like one should be able to modify the created and modified properties (correct term?).

I created a field for date and then was able to move this field over to the posts so it would be easier to manage with new posts as well with:

update pages,field_date set pages.created=field_date.data where pages.id=field_date.pages_id

Since I'm only doing a one-time import, I can now delete the date field.

[adrian]

Quiet mode will help you with the created part:

https://processwire.com/talk/topic/5109-page-save-silently/?p=49275

but to set the modified you'll still need to use SQL because as soon as you save the page, modified gets updated again. At least that is my experience. Maybe there is another workaround I haven't thought of.

https://processwire.com/talk/topic/651-set-created-by-creating-a-page-via-api/?p=5293

[webpig]

Awesome!  Everything seemed so perfect！ Admire extremely admire.

Thanks for sharing.

[Steven]

Thank you for sharing this Ryan, great stuff!

I would really like to use PW for an upcoming project, but since it is heavily relying on publishing news, I'm still hesitating to use WP, to take advantage of all the scheduling options.

So my question: since CMSCritic posts very frequently, did you use a scheduling mechanism/module to be able to post on certain days and hours, throuigh cron (or lazycron)?

Since this is not built in in PW, I searched for some tips on the forum, but besides the known module there's not much buzz around scehduling posts.

Thank you!