Automatically detect and process S B words in content about bigram HOT 7 CLOSED

It would also be nice if the targeted posts could refer back to their origins. Trackback kind of thingy.

from bigram.

The new file admin/bigram-sample-bigrams.php implements a batch routine that will search for SB's in the content. It generates new bigrams with the content <!--more-->Sampled from {$post->post_title}.
The new bigrams are created with the same timestamp as the post from which they are extracted.
The batch routine use class sample_bigrams.

The next stage is to implement a filter function for the_content to automatically generate the links to the bigrams. This should then automatically satisfy the trackback kind of thingy.

from bigram.

The batch routine works quite well. Now we need to implement logic to automatically create new SBs on Save. Note: There’s no need to detect changed SBs. Once an SB has been created it should remain in existence until it’s been determined that it wasn’t required, or is a duplicate.

from bigram.

There's a problem creating new bigrams.

I haven't fully debugged it but assume it's simply due to echo's in the code that was originally written for use in oik-batch and the fact that we're doing some processing during AJAX requests.

Proposed solution

We have to avoid echoing stuff when the request is not being run in batch.

• Add an echo method which does nothing when $this->echo is false.
• Provide a set_echo method to be used in batch.

Avoid doing any work for AJAX requests, especially saving of drafts in heartbeats.

from bigram.

There’s an edge case for when the bw_link shortcode expands to give an title containing Sxxx Bxxx. This is detected as a different link to the original. See ‘Stop blogging, start bigramming’.

from bigram.

There’s an edge case for when the bw_link shortcode expands to give an title containing Sxxx Bxxx. This is detected as a different link to the original. See ‘Stop blogging, start bigramming’.

I don't understand this comment. I'm going to close this issue now that bigram v0.4.1 has been delivered.

from bigram.

I looked at the code the sample_bigrams::sample_post() method and reckoned it should be easy to change it to sample bigrams when a bigram is first created. It doesn't need to check if it's an update so long as it checks that the post content doesn't contain <!--more-->Seen before which is the start of the post content created for a sample bigram. We don't want the code to go recursive.

from bigram.