Read more tag behavior change?

• 

  frozenroyalty · Member · Dec 5, 2013 at 10:37 pm

  • Copy link

  Sooo…is that acknowledging that a bug was introduced, or was it a behavior change that didn’t work as expected?

• 

  dandelionsalad · Member · Dec 5, 2013 at 10:41 pm

  • Copy link

  Wonderful news. Thank you so much for letting us know.

  Now, I’ll have to edit a lot of blog posts.

• 

  kraftbj · Staff · Dec 5, 2013 at 10:52 pm

  • Copy link

  It was an attempt to fix a bug that didn’t work as expected.

  In addition to the more tag, there is also a not-as-well-used “nextpage” tag that can divide your single post into multiple pages.

  The problem is, especially with nextpage tag, is the HTML can become “off-balanced” between the break point (where the more and nextpage tags are at in your post). For example, if you had a nextpage tag in the middle of bold text, the bold formatting wouldn’t be applied in both places.

  In the attempt to “balance” the tags—force both areas before and after the split point to use bold formatting—the behavior worked great for nextpage breakpoints, but caused these headaches for the more tag.

  Since it made things worse that the original bug it was fixing, it was reverted until a more robust solution was ready.

  The XHTML option is generally good to have checked—it helps ensure any XHTML on your site is valid according to the spec. In this case, though, having it unchecked turned off the poor performing “balancing” act.

  Thanks for your patience and understanding.

• 

  dandelionsalad · Member · Dec 5, 2013 at 11:04 pm

  • Copy link

  Are you going to change this again in the future? You said, “… until a more robust solution was ready.”

  What I need to know is will the “more” tag within blockquotes work only temporarily or forever?

  Thanks again.

• 

  kraftbj · Staff · Dec 5, 2013 at 11:21 pm

  • Copy link

  The specific case of the blockquote was raised as an example of how the fix failed, so it is at the front of the conversation as a condition that needs to work for any future fixes. In other words, it should continue to work after any future fix is developed.

  Anyone can join in the discussion at http://core.trac.wordpress.org/ticket/6297 about it (you don’t have to, but if you’re curious on seeing how the open-source software development process works).