Closed (fixed)
Project:
WordPress Migrate
Version:
7.x-2.0
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
8 Jun 2012 at 21:20 UTC
Updated:
1 Sep 2015 at 19:22 UTC
Jump to comment: Most recent
Comments
Comment #1
mikeryanCan you explain what you mean by "more tags"? Is this a paging feature of WordPress?
Comment #2
spacegoat1701 commentedhttp://codex.wordpress.org/Customizing_the_Read_More
WordPress uses
for that function.
Comment #3
mikeryanOK, so the idea is that in the Drupal context, if there's a <!--more--> tag in the body, the content before the tag would become the Drupal teaser, right? Shouldn't be too hard to implement that...
Comment #4
mikeryanComment #5
spacegoat1701 commentedThe simplest thing might be just to replace
<!--more-->with
<!--break-->Comment #6
mikeryanCommitted.
Comment #8
ambient.impactHi there. I can see that this was apparently committed to the module three years ago, it doesn't seem to be working for me. All the imported nodes are still using the default trim value, without a teaser break set. When I look at the body contents, I can find the WordPress
<!--more-->tag, which I assumed was supposed to be converted to Drupal's<!--break-->? I'm using the following module versions:Migrate 7.x-2.8
Migrate Extras 7.x-2.5
WordPress Migrate 7.x-2.3+4-dev
And my blog posts from WordPress are being imported into the WP blog post content type provided by the WP Blog module, if that's in any way relevant.