cavemonkey50

<p>WordPress 2.1 introduces a nasty “feature” to feeds. Instead of abiding by your feed preferences, WordPress will truncate your feed’s content anywhere you insert a <!–more–> tag. Full Text Feed undos this functionality, allowing your feeds to contain the full text regardless of <!–more–> usage.</p>


Full Text Feed

Prevents WordPress 2.1+ from adding a more link to your website's feed.

ishitaka

<p>Replaces site search with full-text search.</p>
<p>Replace the site search from LIKE search to Japanese full-text search (MySQL + Ngram parser or Mroonga engine + TokenMecab parser). This will significantly improve search performance.</p>
<p>Search for pure strings (plain text) without HTML tags. This will prevent HTML tags from being searched.</p>
<p>The data (index) for searching is stored in a dedicated table. It does not rewrite existing table structures or post data (posts table).</p>
<p>Searches for text in PDF, Word (doc, docx), Excel, and PowerPoint files. Secured PDF file are currently not supported.</p>
<p>It supports WordPress multisite.</p>
<h4>Search string options</h4>
<ul>
<li><code>OR</code> (uppercase letter) – Combine searches. Example: foo OR bar</li>
<li><code>-</code> – Exclude words from the search. Example: foo -bar</li>
<li><code>""</code> – Search for an exact match. Example: “foo bar”</li>
<li><code>*</code> – Search by wildcard. Mroonga only. Example: foo*</li>
<li><code>()</code> – Grouping. Mroonga only. Example: (foo OR bar) baz</li>
</ul>
<h4>Operating environment</h4>
<p>Requires MySQL 5.6 or later, or Mroonga engine.</p>
<p>Mroonga engine is strongly recommended. InnoDB engine performs significantly worse with large amounts of data.</p>


Full-Text Search

Replaces site search with full-text search.

Full Text Feed vs Full-Text Search