Download

Yet Another Related Posts Plugin (YARPP)

By Adknowledge

Description

Yet Another Related Posts Plugin (YARPP) displays pages, posts, and custom post types related to the current entry, introducing your readers to other relevant content on your site.

YARPP Basic for Standard Features

  • Thumbnail or list view of related content.
  • Related posts, pages, and custom post types.
  • Templating: The YARPP templating system gives you advanced control of how your results are displayed.
  • An advanced and versatile algorithm: Using a customizable algorithm considering post titles, content, tags, categories, and custom taxonomies, YARPP finds related content from across your site. Learn More.
  • Related posts in feeds: Display related posts in RSS feeds with custom display options.

This plugin requires PHP 5, MySQL 4.1, and WordPress 3.3 or greater. See the FAQ for answers to common questions.

Installation

Auto display on your website

  1. Copy the folder yet-another-related-posts-plugin into the directory wp-content/plugins/ and activate the plugin.
  2. (optionally) copy the sample template files inside the yarpp-templates folder into your active theme.
  3. Go to the “Related Posts (YARPP)” settings page to customize YARPP.

Auto display in your feeds

Make sure the “display related posts in feeds” option is turned on if you would like to show related posts in your RSS and Atom feeds. The “display related posts in feeds” option can be used regardless of whether you auto display them on your website (and vice versa).

Widget

Related posts can also be displayed as a widget. Go to the Appearance > Widgets options page and add the “Related Posts (YARPP)” widget. Choose to display content from YARPP Basic. The widget will only be displayed on single entry (permalink) pages.

The YARPP Basic widget can be used even if the “auto display” option is turned off.

Custom display through templates

YARPP allows the advanced user with knowledge of PHP to customize the display of related posts using a templating mechanism.

FAQ

Common Questions about YARPP Basic

Below are Frequently Asked Questions about YARPP basic.

If your question isn’t here, ask your own question at the WordPress.org forums.

Many pages list “no related posts.”

Most likely you have “no related posts” right now because the default “match threshold” is too high. Here’s what I recommend to find an appropriate match threshold: lower your match threshold in the YARPP “Relatedness” options to something very low, like 1. (If you don’t see the match threshold, you may need to display the “Relatedness” options via the “Screen Options” tab at the top.) Most likely the really low threshold will pull up many posts that aren’t actually related (false positives), so look at some of your posts’ related posts and their match scores. This will help you find an appropriate threshold. You want it lower than what you have now, but high enough so it doesn’t have many false positives.

How can I move the related posts display?

If you do not want to show the Related Posts display in its default position (right below the post content), first go to YARPP options and turn off the “automatically display” options in the “website” section. If you would like to instead display it in your sidebar and you have a widget-aware theme, YARPP provides a Related Posts widget which you can add under “Appearance” > “Widgets.”

If you would like to add the Related Posts display elsewhere, edit your relevant theme file (most likely something like single.php) and add the PHP code related_posts(); within The Loop where you want to display the related posts. (Make sure you don’t add echo related_posts(); or you may end up with duplicates in your related posts section.)

How can I limit related posts to a certain time frame? For instance, I don’t want to show posts from two years ago.

Yes. In WordPress, go to “Settings” and “Related Posts (YARPP)” and make sure “The Pool” is checked in the “Screen Options” section at the top of the page. In “The Pool” section, check the box next to “Show only posts from the past X months.”

Where do I tell YARPP to display related posts only by tags?

In WordPress, go to “Settings” and “Related Posts (YARPP)” and make sure “Relatedness” is checked in the “Screen Options” section at the top of the page. In the “Relatedness” section, configure the dropdown boxes next to “Titles,” “Bodies,” “Categories,” and “Tags.”

Can I specify related posts?

Sorry, but specifying related posts, displaying related posts from external WordPress sites, and pulling content from the Comments section are all outside the scope of YARPP at this time.

I’m seeing related posts displayed on the home page. How do I prevent that?

Some WordPress themes treat the home page as an archive or a “page.” Go to “Settings” then “Related Posts (YARPP)” and view the “Display Options” section. Make sure “Pages” and “Also display in archives” are not checked.

How can I prevent the “related posts” list from displaying on specific posts?

If you have several posts where you don’t want to display related posts and they all share a similar category or tag, you could use “Disallow by Category” or “Disallow by Tag” in “The Pool” section. (Go to “Settings” and “Related Posts (YARPP)” and make sure “The Pool” is checked in the “Screen Options” section at the top of the page.)

You could also add <!--noyarpp--> to the HTML code of any post to prevent related posts from displaying. This solution will only work if you are using “Automatic Display” in the “Display Options” section. If you are programatically calling related_posts() from PHP code, you’ll have to do your own checking to see if related posts are appropriate to display or not.

I’m using the Thumbnails display in YARPP 4. How do I override the style of the text that displays? The title only shows two lines, the font is larger than I’d like, I’d like to center the thumbnails, etc.

If you’re familiar with CSS, you can override any YARPP styles by editing your theme’s style.css file, or any other CSS file you may have created that loads after the YARPP one. To edit your theme’s CSS file, go to “Appearance” then “Editor” and then click style.css in the right sidebar. Add changes at the bottom of the file and click “Save.” If you do edit this file, just make sure you add !important after each style declaration, to make sure they’ll override the YARPP rules.

Some common overrides that YARPP users have added are:

/* Reduces the title font size and displays more than two title lines */
.yarpp-thumbnail {height: 200px !important;}
.yarpp-thumbnail-title {font-size:0.8em !important; max-height: 4em !important}

/* Centers the thumbnail section */
.yarpp-related-widget {text-align:center !important;}

Once you save any CSS changes, empty your browser’s cache and reload your page to see the effect.

I’m using the Thumbnails display. How can I change the thumbnail size?

The default YARPP thumbnail size is 120px by 120px. The thumbnail size can be specified programmatically by adding add_image_size('yarpp-thumbnail', $width, $height, true); to your theme’s functions.php file with appropriate width and height variables. In the future I may add some UI to the settings to also set this. Feedback is requested on whether this is a good idea.

Each time you change YARPP’s thumbnail dimensions like this, you will probably want to have WordPress regenerate appropriate sized thumbnails for all of your images. I highly recommend the Regenerate Thumbnails plugin for this purpose.

I’m using the Thumbnails display. Why aren’t the right size thumbnails being served?

By default, if an appropriately sized thumbnail is not available in WordPress, a larger image will be served and will be made to fit in the thumbnail space via CSS. Sometimes this means images will be scaled down in a weird way, so it is not ideal. What you really want is for YARPP to serve appropriately-sized thumbnails.

There are two options for doing so:

  • First, you can use the Regenerate Thumbnails plugin to generate all these thumbnail-sized images in a batch process. This puts you in control of when this resizing process happens on your server (which is good because it can be processor-intensive). New images which are uploaded to WordPress should automatically get the appropriate thumbnail generated when the image is uploaded.

  • Second, you can turn on a feature in YARPP to auto-generate appropriate size thumbnails on the fly, if they have not yet been created. Doing this type of processing on the fly does not scale well, so this feature is turned off by default. But if you run a smaller site with less traffic, it may work for you. Simply add define('YARPP_GENERATE_THUMBNAILS', true); to your theme’s functions.php file.

I’m using the Thumbnails display. Why are some of my posts missing appropriate images?

YARPP’s thumbnail view requires that a WordPress “featured image” be set for each post. If you have many posts that never had a featured image set, I recommend the plugin Auto Post Thumbnail, which will generate post thumbnails for you.

How can I use the custom template feature?

YARPP’s custom templates feature allows you to uber-customize the related posts display using the same coding conventions and Template Tags as in WordPress themes. Custom templates must be in your active theme’s main directory in order to be recognized by YARPP. If your theme did not ship with YARPP templates, move the files in the yarpp-templates directory which ships with YARPP into your active theme’s main directory. Be sure to move the files (which must be named yarpp-template-….php) to your theme, not the entire directory.

Is YARPP compatible with WordPress Multisite?

YARPP should work fine in a multisite environment, and many users are running it without any issues using WordPress Multisite. It will, however, only get results within each blog. It will not display related posts results from across your network.

I want to use YARPP on a site with content in multiple languages.

The recommended solution in such cases is to use the Polylang plugin. Polylang has posted a tutorial for using YARPP with Polylang.

Does YARPP work with full-width characters or languages that don’t use spaces between words?

YARPP works fine with full-width (double-byte) characters, assuming your WordPress database is set up with Unicode support. 99% of the time, if you’re able to write blog posts with full-width characters and they’re displayed correctly, YARPP will work on your blog.

However, YARPP does have difficulty with languages that don’t place spaces between words (Chinese, Japanese, etc.). For these languages, the “consider body” and “consider titles” options in the “Relatedness options” may not be very helpful. Using only tags and categories may work better for these languages.

Does YARPP slow down my blog/server?

The YARPP calculation of related content does make a little impact, yes. However, YARPP caches all of its results, so any post’s results need only be calculated once. YARPP’s queries have been significantly optimized since version 3.5.

If you are running a large site and need to throttle YARPP’s computation, try the official YARPP Experiments plugin which adds this throttling functionality. If you are looking for a hosting provider whose databases will not balk under YARPP, I personally have had great success with MediaTemple.

Are there any plugins that are incompatible with YARPP?
  • DISQUS: go to the DISQUS plugin advanced settings and turn on the “Check this if you have a problem with comment counts not showing on permalinks”.
  • SEO_Pager plugin: turn off the automatic display option in SEO Pager and instead add the code manually.
  • Pagebar 2;
  • WP Contact Form III plugin and Contact Form Plugin;
  • WPML: various incompatibilities have been reported. The multilingual plugin Polylang has great support for YARPP and is suggested as a replacement for WPML.
  • Other related posts plugins, obviously, may also be incompatible.

Please submit similar bugs by starting a new thread on the WordPress.org forums. I check the forums regularly and will try to release a quick bugfix.

YARPP seems to be broken since I upgraded to WordPress X.X.

Before upgrading to a new WordPress version, you should first deactivate all plugins, then upgrade your WordPress, and then reactivate your plugins. Even then, you may still find that something went wrong with your YARPP functionality. If so, try these steps:

  1. Visit the “Related Posts (YARPP)” settings page to verify your settings.
  2. Deactivate YARPP, replace the YARPP files on the server with a fresh copy of the new version, and then reactivate it.
  3. Install the official YARPP Experiments plugin to flush the cache.
Can I clear my cache? Can I build up the cache manually?

The official YARPP Experiments plugin adds manual cache controls, letting you flush the cache and build it up manually.

I removed the YARPP plugin but I still see YARPP-related database tables. Shouldn’t those be removed, too?

Beginning with version 4.0.7, YARPP includes clean uninstall functionality. If you no longer wish to use YARPP, first deactivate YARPP using the “Plugins” page in WordPress, then click the “Delete” link found on the same page. This process will automatically remove all YARPP-related files, including temp tables. If you manually try to remove YARPP files instead of going through WordPress, some files or temp tables could remain.

Does YARPP support custom post types?

Yes. To make YARPP support your custom post type, the attribute yarpp_support must be set to true on the custom post type when it is registered. It will then be available on options on the YARPP settings page.

'yarpp_support' => true

If you would like to programmatically control which post types are considered in an automatically-displayed related posts display, use the yarpp_map_post_types filter.

Can I customize how YARPP displays?

Yes. Developers can call YARPP’s powerful relatedness algorithm from anywhere in their own code. Some examples and more details are in my slides from my WordCamp Birmingham talk.

yarpp_related(array(
    // Pool options: these determine the "pool" of entities which are considered
    'post_type' => array('post', 'page', ...),
    'show_pass_post' => false, // show password-protected posts
    'past_only' => false, // show only posts which were published before the reference post
    'exclude' => array(), // a list of term_taxonomy_ids. entities with any of these terms will be excluded from consideration.
    'recent' => false, // to limit to entries published recently, set to something like '15 day', '20 week', or '12 month'.
    // Relatedness options: these determine how "relatedness" is computed
    // Weights are used to construct the "match score" between candidates and the reference post
    'weight' => array(
        'body' => 1,
        'title' => 2, // larger weights mean this criteria will be weighted more heavily
        'tax' => array(
            'post_tag' => 1,
            ... // put any taxonomies you want to consider here with their weights
        )
    ),
    // Specify taxonomies and a number here to require that a certain number be shared:
    'require_tax' => array(
        'post_tag' => 1 // for example, this requires all results to have at least one 'post_tag' in common.
    ),
    // The threshold which must be met by the "match score"
    'threshold' => 5,

    // Display options:
    'template' => , // either the name of a file in your active theme or the boolean false to use the builtin template
    'limit' => 5, // maximum number of results
    'order' => 'score DESC'
),
$reference_ID, // second argument: (optional) the post ID. If not included, it will use the current post.
true); // third argument: (optional) true to echo the HTML block; false to return it

Options which are not specified will default to those specified in the YARPP settings page. Additionally, if you are using the built-in template rather than specifying a custom template file in template, the following arguments can be used to override the various parts of the builtin template: before_title, after_title, before_post, after_post, before_related, after_related, no_results, excerpt_length.

If you need to use related entries programmatically or to know whether they exist, you can use the functions yarpp_get_related( $args, $reference_ID ) and yarpp_related_exist( $args, $reference_ID ). yarpp_get_related returns an array of post objects, just like the WordPress function get_posts. yarpp_related_exist returns a boolean for whether any such related entries exist. For each function, $args takes the same arguments as those shown for yarpp_related above, except for the various display and template options.

Note that custom YARPP queries using the functions mentioned here are not cached in the built-in YARPP caching system. Thus, if you notice any performance hits, you may need to write your own code to cache the results.

Does YARPP support custom taxonomies?

Yes. Any taxonomy, including custom taxonomies, may be specified in the weight or require_tax arguments in a custom display as above. term_taxonomy_id specified in the exclude argument may be of any taxonomy.

If you would like to choose custom taxonomies to choose in the YARPP settings UI, either to exclude certain terms or to consider them in the relatedness formula via the UI, the taxonomy must (a) have either the show_ui or yarpp_support attribute set to true and (b) must apply to either the post types post or page or both.

Which languages does YARPP support?

YARPP is currently localized in the following languages:

Reviews

No support for over a month

The plugins looks great at the begining but after a while, I found a few errors.
After trying to contact the author (through the forum here and through Facebook) and did not get an answer, I have no choice but to give only two stars, because I waited too long for response and it was just a waste of time. If you have the choise pick a differest plugin.

Weak

Instead of block category should be ignore

PS. For now JetPacks releateg is better 🙁

Pročitajte svih 176 recenzija

Suradnici i Programeri

“Yet Another Related Posts Plugin (YARPP)” is open source software. The following people have contributed to this plugin.

Contributors

“Yet Another Related Posts Plugin (YARPP)” has been translated into these 6 locales: Japanese, Croatian, Spanish, Czech, English (UK), English (Canada). Thank you to the translators for their contributions.

Translate “Yet Another Related Posts Plugin (YARPP)” into your language.

Interested in development?

Browse the code or subscribe to the development log by RSS.

Changelog

4.4

  • Discontinuing the YARPP Pro service

4.3.6

  • Removed new file

4.3.5

  • Fix ‘unable to update’

4.3.4

  • Don’t allow new YARPP Pro signups
  • Discontinuing the YARPP Pro service as of 01/31/2017

4.3.3

  • Fix ‘Undefined index’ in YARPP_Cache.php (credit to Derrick Hammer/@pcfreak30)

4.3.2

  • Fix ksort error in YARPP_Cache.php (credit to Derrick Hammer/@pcfreak30)
  • Discontinuing the YARPP Pro service as of 12/31/2016

4.3.1

  • Tested on WordPress 4.4.
  • Fix $lang missing error in YARPP_Cache.php
  • Fix WP_Widget deprecation PHP error

4.2.5

  • Tested on WordPress 4.2.2.
  • Styling fix: User can now override all YARPP CSS styling

4.2.4

  • Bugfix: Missing internal version number update

4.2.3

  • Tested on WordPress 4.0.
  • Bugfix: Made logo image url in css scheme-less (fix http/https)

4.2.2

  • Tested on WordPress 3.9.1.
  • Bugfix: Duplicate related post links removed.
  • Bugfix: Removed extra <br> at the end of post content.

4.2.1

  • Bugfix: Resolved the issue related to “Warning: in_array() expects parameter 2 to be array, null given”.

4.2

  • Tested on WordPress 3.9.
  • YARPP Basic and YARPP Pro can now be used simultaneously, rather than being mutually exclusive.
  • Added a YARPP Pro option to the YARPP sidebar widget.
  • Enlarged “Display Options” panel textbox for increased usability.
  • Updated YARPP Pro script to allow for future enhancements.
  • Updated MyISAM check notice message to explain its impact on “Pages.”
  • Added descriptive text to explain new enhancements.

4.1.2

  • Tested on WordPress 3.8.
  • Added field boxes with API Key information to Domain page.
  • MyISAM check notice message was updated to better express what it does and a feedback message was added in case the fulltext index creation fails.
  • Bugfix: MyISAM check overwrite was broken since 4.1.x release.
  • Bugfix: PHP title not defined warning when creating new cache entry.
  • Bugfix: Uninstall script now deletes options with empty, false or 0 values.
  • Bugfix: Scrollbar functionality on YARPP Pro Domain Settings page.

4.1.1

  • Bugfix: Incompatibility with PHP < 5.3.x

4.1

  • Added optional YARPP Pro enhancements:
    • Revenue-generating ad content interspersed with related posts display
    • Detailed reports for Clicks, Click-Through Rate, and Revenue
    • Ability to display related content from multiple domains
    • UI settings for related content display, including thumbnail size and layout
    • Refined “relatedness” algorithm is now independent of MyISAM or InnoDB engines
    • “Relatedness” is calculated and stored externally, minimizing server load
  • Based on user feedback, the “Screen Options” section displays all YARPP options panels by default.

4.0.8

  • The recent 4.0.7 YARPP update included a settings modification to opt in users to our tracking pixel by default. By doing so, our intent was to use this expanded information to better understand the geographic reach of the popular plugin. We have been made aware that this change infringed upon the WordPress guidelines. We apologize for the issue and have remedied the situation in update 4.0.8. Going forward, we would really appreciate your input to help us continue to improve the product. We are primarily looking for country, domain, and date installed information. Please help us make YARPP better by opting in to this information and by filling out our quick, 5 question survey. Thank you.

4.0.7

  • Bugfix: Now more robust against certain custom options.
  • Updated plugin de-activate/delete functionality to drop all tables. Prior to fix some legacy tables remained which required manual deletion in wp_options from phpmyadmin.
  • Updated FAQs section.
  • Update to YARPP’s data collection terms and conditions.
  • Added Macedonian (mk_MK) localization by [WPdiscounts] (http://wpdiscounts.com).

4.0.6

  • YARPP’s automatic display will not run on posts which include the HTML comment <!--noyarpp--> by request.
  • More robust activation handling, particularly when network-activated.
  • Improved handling of exceptions, for example when fulltext indexes cannot be created or non-MyISAM tables are used.
  • YARPP no longer triggers the generation of YARPP-thumbnail-sized images (120×120) when YARPP thumbnails are not used.
    • If you are using YARPP programmatically and using the thumbnails view and having troubles with YARPP’s thumbnail size being registered, a manual control to force image size registration has been added to the YARPP Experiments plugin.
  • Bugfix: calls to yarpp_related_exist() type functions were causing errors.
  • Bundled yarpp-template-wpml.php is now called yarpp-template-multilingual.php, following discussion with the author of the Polylang plugin.
  • Localizations

4.0.5

  • Bugfix: Some upgrade code would try to access the global $yarpp before it was properly initialized
  • Added experimental graph data method to the YARPP table cache class

4.0.4

  • Bugfix: 4.0.3 broke some paginated post displays
  • Bugfix: custom post type support was not working properly in widget displays
  • Bugfix: widget control JS was not working right when first adding a widget
  • Added ability to set widget-specific heading for the thumbnails view, by request
  • Added the filter yarpp_results
  • Localizations:
    • Updated French localization and stopword list
    • Added Slovenian (sl_SI) localization by Silvo Katalenić
  • Bugfix: forces the DB Cache Reloaded (Fix) plugins to flush when necessary

4.0.3

  • Bugfix: on sites where custom templates are not available, the “thumbnails” display option would get reset when visiting the YARPP settings page
  • Bugfix: the CSS for YARPP’s thumbnails display would load at the foot of the page, and therefore would cause some style-flashing. This is fixed for automatic includes, but not for widgets or manual calls.
  • Restoration of the $post global after YARPP is now more robust. Fixes the display of incorrect metadata on some complex themes.
  • YARPP template files no longer recognize Template Name fields in their headers, instead using YARPP Template. This is to avoid confusion with regular page templates.
  • Added “Related Posts” meta box to other “auto display” post types
  • Updated Polish localization

4.0.2

  • Bugfix: cache should be cleared when the “show only previous posts?” option is changed
  • Bugfix: In the thumbnail display, sometimes the default image was not displayed, even though no post thumbnail was available.
  • Localization updates
    • Updated Polish, Japanese, Hebrew localizations
    • Better right-to-left layout support

4.0.1

  • Improvements to thumbnail handling
    • See new FAQ entry for practical details
    • Thumbnail size can be specified programmatically (see FAQ)
    • YARPP now registers its thumbnail size properly as yarpp-thumbnail
    • Fixed a typo and simplified an item in the dynamic styles-thumbnails.php styles
    • Code to generate thumbnails of appropriate size on the fly has been added, but is turned off by default for performance reasons (see FAQ)
  • Bugfix: a class of yarpp-related- with a stray hyphen was sometimes being produced. Now fixed so it produces yarpp-related.
  • Bugfix: term_relationships table was being joined when unnecessary
  • Bugfix: widget options would not display if custom templates were not available
  • Bugfix: some transients expired too soon if object caching was used
  • The yarpp_map_post_types filter now also applies to feeds and takes an extra argument to know whether the context is website or rss.

4.0

  • New thumbnail template option!
    • No PHP required—just visit the settings page
    • Edit your theme’s CSS file to modify the styling
  • Auto display settings changes:
    • Easily choose which post types you want related posts to display on
    • Added an “also display in archives” option
  • Bugfix: uses of related_posts_exist() and get_related() without explicit reference ID parameter would incorrectly return no related posts.
  • Changes to the output HTML:
    • All YARPP output is now wrapped in a div with class yarpp-related, yarpp-related-widget, or yarpp-related-rss as appropriate (by request). If there are no results, a yarpp-related-none class is added.
    • The “related posts brought to you by YARPP” text is only added if there were results.
  • Refinements to settings UI:
    • A new design for the template chooser
    • Example code display is now hidden by default; turn them back on from the “screen options” tab.
    • A new “copy templates” button allows one-button installation of bundled templates into the current theme, if filesystem permissions make it possible.
    • Header information in YARPP custom templates are now displayed to users in the settings UI. Available fields are YARPP Template, Description, Author, Author URI, in the same format as plugin and theme file headers. See bundled templates for examples.
  • Code cleanup:
    • Settings screen UI have been rewritten to use divs rather than tables!
    • Inline help in settings screen now use WordPress pointers
    • Removed keyword cache table, as it does not ctually improve performance much and the overhead of an additional table is not worth it.
  • Default option changes:
    • Default result count is now 4
    • Default match threshold is now 4
    • Default for “before related entries” heading uses h3 instead of p
  • Added yarpp_map_post_types filter to programmatically specify what post types should be looked at for automatic displays
  • Added option to send YARPP setting and usage information back to YARPP (off by default). This information will be used to make more informed decisions about future YARPP development. More info available in the settings.

3.5.6

  • Typo fix for postmeta cache
  • Added Traditional Chinese (Taiwan, zh_TW) localization by Pseric

3.5.5

  • Quick bugfix for how admin screen code was loaded in in WordPress < 3.3.

3.5.4

  • New Help tab, which displays help text from the readme.
  • Retina icons! Now served faster, in sprite form.
  • Added Croatian (hr) localization by gocroatia.com
  • Cleanup:
    • Bugfix: stopwords would not be loaded if WPLANG is defined but blank.
    • Added new stats method to YARPP_Cache_* objects.
    • Load meta boxes on screen_option hook. Improves performance on admin pages.
    • Changed default option of “show only previous posts” to false and removed FAQ text, as it no longer improves performance much.

3.5.3

  • Bugfix: Fixed a common cause of “no related posts”!
  • Better post revision handling
  • Bugfix: setup wasn’t automatic for network activations.
  • Code cleanup:
    • Bugfix: tables should be created using WordPress charset settings
    • YARPP_Cache_*::update methods are now protected
    • Simplified some post status transition handling
    • Ensure that delete_post hook receives relevant post ID information
    • Various functions now refer to the enforce method which will activate if it’s a new install, or else upgrade if necessary. (Part of the fix for the network activation above.)

3.5.2

  • Bugfix: fix an unfortunate typo which caused “no related posts” on many environments with non-MyISAM tables
  • Fixed a bug where related posts would not be recomputed on post update, on environments using the table YARPP cache method and a persistent object caching system, like W3 Total Cache or memcached
  • Bugfix: reference to get_post_types() failed in ajax display
  • Fixed a bug where some RSS display options were not being obeyed
  • Fixed a bug where the “automatic display” was being displayed on some custom post types without any control.
  • Localizations:
  • Clarified readme to require WordPress 3.1
  • Code cleanup:
    • PHP 5.3+: replaced an instance of ereg_replace
    • Removed warning on settings save
    • Sometimes a warning was printed on upgrade from YARPP < 3.4.4
    • Fixed PHP warning when no taxonomies are considered
    • No longer using clear_pre function which has been deprecated since WordPress 3.4.

3.5.1

  • Bugfix: change $yarpp->get_post_types() to return array of names by default
  • Ensure that all supported post types are used when “display results from all post types” is set

3.5

  • New public YARPP query API, which supports custom post types
    • Documentation in the “other notes” section of the readme
    • Changed format of weight, template, recent parameters in options and in optional args
  • Further main query optimization:
    • What’s cooler than joining four tables? Joining two.
    • Exclude now simply uses term_taxonomy_ids instead of term_ids
  • Bugfix: “related posts” preview metabox was not always working properly
  • Changes to the related_*() and yarpp_related() function signatures.
  • Added “consider with extra weight” to taxonomy criteria as well
  • Code cleanup:
    • Don’t clear the cache when it’s already empty
    • protect the sql method as it shouldn’t be public
    • Further use of utility functions from 3.1 like wp_list_pluck()
    • New constant, YARPP_EXTRA_WEIGHT to define the “extra weight.” By default, it’s 3.
  • Localizations:
    • Added Slovak (sk_SK) localization by Forex
    • Added Romanian (ro_RO) localization by Uhren Shop
    • Updated it_IT, ko_KR, fr_FR, sv_SE, ja localizations

3.4.3

  • Bugfix: keywords were not getting cleared on post update, meaning new posts (which start blank) were not getting useful title + body keyword matches. This often resulted in “no related posts” for new posts.
  • Postmeta cache: make sure to clear keyword cache on flush too
  • Make welcome pointer more robust
  • More custom post type support infrastructure
  • Updated Turkish localization by Barış Ünver.

3.4.2

  • Bugfix: 3.4 and 3.4.1 assumed existence of wp_posts table.
  • Fix typo in yarpp-template-random.php example template file
  • Improve compatibility with DB Cache Reloaded plugin which doesn’t properly implement set_charset method.

3.4.1

  • Bugfix: restore global $post access to custom templates
  • Bugfix for missing join_filter on bypass cache
  • Bugfixes to query changes:
    • Bugfix: Shared taxonomy terms were not counted correctly
    • Bugfix: exclusion was not working
  • Bugfix: “disallow” terms were not being displayed for custom taxonomies.
  • Add defaults for the post_type arg
  • Strengthen default post ID values for related_* functions
  • Added nonce to cache flushing. If you would like to manually flush the cache now, you must use the YARPP Experiments plugin.
  • Updated sv_SE, ko_KR, fr_FR localizations

3.4

  • Major optimizations to the main related posts query, in particular with regard to taxonomy lookups
    • Performance improvements on pages with “no related posts”
  • Now can consider custom taxonomies (of posts and pages), in addition to tags and cateogories! Custom taxonomies can also be used to exclude certain content from The Pool.
  • Add welcome message, inviting users to check out the settings page
  • Bug fix: Custom templates could not be used in widget display
  • Significant code cleanup
    • Move many internal functions into a global object $yarpp of class YARPP; references to the global $yarpp_cache should now be to global $yarpp->cache
    • Created the “bypass” cache engine which is used when custom arguments are specified.
      • Switch to bypass cache for demos
    • Now only clears cache on post update, and only computes results for actual posts, not revisions (thanks to Andrei Mikhaylov)
    • Removed the many different options entries, replacing them with a single yarpp option (except yarpp_version)
    • Fixed issues with display options field data escaping and slashing once and for all
    • Streamlined keyword storage in YARPP_Cache_Postmeta
    • Create YARPP_Cache abstract class
    • Updated minor bug for computing how many results should be cached
    • Adding some filters: yarpp_settings_save, yarpp_blacklist, yarpp_blackmethods, yarpp_keywords_overused_words, yarpp_title_keywords, yarpp_body_keywords, yarpp_extract_keywords
    • New systematic use of YARPP_ constants to communicate cache status
    • Use get_terms to load terms
  • Get lazy and embrace asynchronicity:
    • Implement lazy/infinite scrolling for the “disallow tags” and “disallow categories,” so the YARPP settings screen doesn’t lock up the browser for sites which have a crazy number or tags or categories
    • Don’t compute related posts for the metabox on the edit screen; display them via ajax instead
    • Only clear cache on post save, not recompute
  • Added yarpp_get_related() function can be used similar to get_posts()
  • Support for YARPP Experiments.
  • Fix formatting of the Related Posts meta box
  • Localizations

3.3.3

  • Bug fix: a fix for keyword computation for pages; should improve results on pages. May require flushing of cache: see FAQ for instructions.
  • Init YARPP on the init action, for compatibility with WPML
  • Updated Polish, Italian, and Japanese localizations; added Dutch stopwords by Paul Kessels
  • Code cleanup:
    • Minor speedup to unnecessarily slow i18n code
    • Fixed fatal error in postmeta keyword caching code
    • Fewer globs
    • Bug fix: ignore empty blog_charsets

3.3.2

  • Bugfix: removed an unlocalized string
  • Bugfix for users of WordPress 3.0.x.

3.3.1

3.3

  • Pretty major rewrite to the options page for extensibility and screen options support
    • By default, the options screen now only show the display options. “The Pool” and “Relatedness” options can be shown in the screen options tab in the top right corner of the screen.
    • Removed the “reset options” button, because it wasn’t actually doing anything.
  • Rebuilt the new version notice to actually have a link which triggers the WordPress plugin updater, at least for new full versions
  • Changed default “relatedness” settings to not consider categories, to improve performance
  • Added BlogGlue partnership module
  • Localizations
    • Quick fix to Czech word list file name
    • Updated Italian localization (it_IT)
    • Added Hungarian (hu_HU) by daSSad
    • Added Kazakh (kk_KZ) by DachaDecor
    • Added Irish (gb_IR) by Ray Gren

3.2.2

  • Now ignores soft hyphens in keyword construction
  • Minor fix for “cross-relate posts and pages” option and more accurate related_*() results across post types
  • Localization updates:
    • Updated de_DE German localization files
    • Fixed an encoding issue in the pt_PT Portuguese localization files
    • Added es_ES Spanish localization by Rene of WordPress Webshop
    • Added ge_KA Georgian by Kasia Ciszewski of Find My Hosting
    • Added Czech (cs_CZ) overused words list by berniecz

3.2.1

3.2

  • Better caching performance:
    • Previously, the cache would never actually build up properly. This is now fixed. Thanks to Artefact for pointing this out.
    • The appropriate caches are cleared after posts are deleted (#1245).
    • Caching is no longer performed while batch-importing posts.
  • A new object-based abstraction for the caching system. YARPP by default uses custom database tables (same behavior as 3.1.x), but you now have an option to use the postmeta table instead. To use postmeta caching, add define('YARPP_CACHE_TYPE', 'postmeta'); to your wp-config.php file.
  • Localizations:
  • Added WordPress HelpCenter widget for quick access to professional support.
  • Some code cleanup (bug #1246)
  • No longer supporting WordPress versions before 3.0, not because I suddenly started using something that requires 3.0, but in order to simplify testing.

3.1.9

  • Added Standard Arabic localization (ar) by led
  • The Related Posts Widget now can also use custom templates. (#1143)
  • Fixed a conflict with the Magazine Premium theme
  • Fixes a WordPress warning of “unexpected output” on plugin installation.
  • Fixes a PHP warning message regarding array_key.
  • Fixed a strict WordPress warning about capabilities.
  • Bugfix: widget now obeys cross-relate posts and pages option
  • For WPMU + Multisite users, reverted 3.1.8’s get_site_options to get_options, so that individual site options can be maintained.

3.1.8

  • Added Turkish localization (tr_TR)
  • Bugfix: related pages and “cross-relate posts and pages” functionality is now working again.
  • Some bare minimum changes for Multisite (WPMU) support.
  • Reimplemented the old “show only previous posts” option. May improve performance for sites with frequent new posts, as there is then no longer a need to recompute the previous posts’ related posts set, as it cannot include the new post anyway.
  • Minor bugfix to threshold limiting.
  • Minor fix which may help reduce strip_tags() errors.
  • Updated FAQ.
  • Code cleanup.

3.1.7

  • Added Egyptian Arabic localization (ar_EG)
  • Changed default option for automatic display of related posts in feeds to OFF. May improve performance for new users who use the default settings.
  • “Use template” options are now disabled when templates are not found. Other minor tweaks to options screen.
  • 3.1.7 has been lightly tested with WP 3.0. Multisite (WPMU) compatibility has not been tested yet.

3.1.6

  • Added Latvian localization (lv_LV)
  • Added a template which displays post thumbnails; requires WordPress 2.9 and a theme which has post thumbnail support

3.1.5

  • Quick bugfix to new widget template (removed extra quote).

3.1.4

3.1.3

3.1.2

3.1.1

3.1

  • New snazzy options screen
  • Smarter, less confusing caching
    • No more manual caching option—”on the fly” caching is always on now.
  • Bugfix: fixed related pages functionality
  • Bugfix: an issue with options saving
  • Bugfix: a slash escaping bug
  • Minor fixes:
    • Fixed yarpp_settings_link dependency when disabled.
    • Breaks (<br />) are now stripped out of titles.
    • Added plugin incompatibility info for Pagebar.
    • Faster post saving.

3.0.13

  • Quick immediate bugfix to 3.0.12

3.0.12

  • Yet another DISQUS note… sigh.
  • Changed default markup to be make the output validate better.
  • Reformatted the version log in readme.txt
  • Added a Settings link to the plugins page
  • Some initial WPML support:
    • Tweaked a SQL query so that it was WPML compatible
    • Added YARPP template to be used with WPML
  • Added Hebrew localization

3.0.11

  • Quick fix for compare_version code.

3.0.10

  • Added Ukrainian localization
  • Incorporated a quick update for the widget display thanks to doodlebee.
  • Now properly uses compare_version in lieu of old hacky versioning.

3.0.9

  • Added Uzbek, Greek, Cypriot Greek, and Vietnamese localizations
  • Further bugfixes for the pagination issue

3.0.8

3.0.7

  • Bugfix: additional bugfix for widgets.
  • Reinstating excerpt length by number of words (was switched to letters in 3.0.6 without accompanying documentation)
  • Localizations:
    • Updated Italian
    • Added Belarussian by Fat Cow
  • Confirmed compatibility with 2.8.1

3.0.6

3.0.5

  • Added link to manual SQL setup information by request
  • Added Portuguese localization
  • Updated info on “on the fly” caching – it is strongly recommended for larger blogs.
  • Updated “incomplete cache” warning message so it is only displayed when the “on the fly” option is off.

3.0.4

  • A fix to the version checking in the options page – now uses Snoopy
  • Adding Dutch localization

3.0.3

  • Reinstated the 3.0.1 bugfix for includes
  • Bugfix: Fixed encoding issue in keyword caching algorithm
  • Bugfix: One SQL query assumed wp_ prefix on tables
  • Added Polish localization
  • Added note on DISQUS in readme
  • Making some extra strings localizable
  • Bugfix: a problem with the Italian localization

3.0.2

3.0.1

  • Bugfix: In some situations before YARPP options were updated, an include PHP error was displayed.

3.0

  • Major new release!
  • Caching for better SQL performance
  • A new templating feature for custom related posts displays
  • Cleaned up options page
  • New and updated localizations

2.1.6

  • Versioning bugfix – same as 2.1.5

2.1.5

2.1.4

2.1.3

2.1.2

  • Bugfix: MyISAM override handling bug

2.1.1

  • Bugfix: keywords with forward slashes () could make the main SQL query ill-formed.
  • Bugfix: Added an override option for the false MyISAM warnings.
  • Preparing for localization! (See note at the bottom of the FAQ.)
  • Adding a debug mode–just try adding &yarpp_debug=1 to your URL’s and look at the HTML source.

2.1 – The RSS edition!

  • RSS feed support!: the option to automagically show related posts in RSS feeds and to customize their display, by popular request.
  • A link to the Yet Another Related Posts Plugin RSS feed.
  • Further optimization of the main SQL query in cases where not all of the match criteria (title, body, tags, categories) are chosen.
  • A new format for pushing arguments to the related_posts() functions.
  • Bugfix: compatibility with the dzoneZ-Et and reddZ-Et plugins.
  • Bugfix: related_*_exist() functions produced invalid queries
  • A warning for wp_posts with non-MyISAM engines and semi-compatibility with non-MyISAM setups.
  • Bugfix: a better notice for users of WordPress < 2.5 regarding the “compare tags” and “compare categories” features.

2.0.6

  • A quick emergency bugfix (In one instance, assumed existence of wp_posts)

2.0.5

2.0.4 – what 2.0 should have been

  • Bugfix: new fulltext query for MySQL 5 compatibility
  • Bugfix: updated apply_filters to work with WP 2.6

2.0.3

2.0.2

  • Versioning bugfix (rerelease of 2.0.1)

2.0.1

2.0

  • New algorithm which considers tags and categories, by frequent request
  • Order by score, date, or title, by request
  • Excluding certain tags or categories, by request
  • Sample output displayed in the options screen
  • Bugfix: an excerpt length bug
  • Bugfix: now compatible with the following plugins:
    • diggZEt
    • WP-Syntax
    • Viper’s Video Quicktags
    • WP-CodeBox
    • WP shortcodes

1.5.1

  • Bugfix: standardized directory references to yet-another-related-posts-plugin

1.5

  • Simple installation: automatic display of a basic related posts install
  • code and variable cleanup
  • FAQ in the documentation

1.1

  • Related pages support!
  • Also, uses apply_filters to apply whatever content text transformation you use (Wikipedia link, Markdown, etc.) before computing similarity.

1.0.1

  • Bugfix: 1.0 assumed you had Markdown installed

1.0

  • Initial upload

Meta

Ocjena

Prikaži sve

Podrška

Problemi riješeni u zadnja dva mjeseca:

0 od 7

Pregledaj forum za podršku