[Plugin: Relevanssi – A Better Search] Custom post types marked are no show in admin results

I don’t think this is the issue.

My public custom post types are show in admin search results. The private custom post types do not.

I did a quick search for “private” on the options screen and didn’t see anything.

Any other ideas?

I did try it. I’ve even confirmed that under “Indexing options” that my custom post type are checked to be Indexed and denoted as yes to Public.

If the custom post type was configured as exclude_from_search, the Public column would be no.

Other ideas?

I did confirm again that private items aren’t in the search result, but public are.

I’ve fixed my issue. It’s come down to two things.

1. I needed to enable read_private_videos and read_private_documents for my roles.

add_action( 'init', 'mbr_modify_roles' );

function mbr_modify_roles () {
    global $wp_roles;

    $roles                      = $wp_roles->get_names();

    foreach ( $roles as $role => $value ) {
        $wp_roles->add_cap( $role, 'read_private_videos' );
        $wp_roles->add_cap( $role, 'read_private_documents' );
    }
}

2. I’ve added private to the allowed indexes to keep on indexing and updating index. Patch attached below.

Index: relevanssi.php
===================================================================
--- relevanssi.php	(revision 152)
+++ relevanssi.php	(working copy)
@@ -429,7 +429,8 @@
     }

 // END added by renaissancehack
-	if ($post_status != 'publish') {
+    $index_statuses = array('publish', 'private');
+	if ( ! in_array( $post_status, $index_statuses) ) {
 		// The post isn't public anymore, remove it from index
 		relevanssi_remove_doc($post, true);
 	}

If you’ve got the fixes as patches, I can pull the code together and send back to you in whole for review and to offer up as beta to other.

I’ve been thinking to put the Indexing actions to an Ajax process so that timeouts stop happening. This would mean a separate processing screen like that for my Flickr Shortcode Importer and TYPO3 Importer, http://wordpress.org/extend/plugins/flickr-shortcode-importer/screenshots/, than options.

Have you also thought to move the options screen to an easier to handle class? Say something like http://plugins.svn.wordpress.org/flickr-shortcode-importer/trunk/class.options.php?

Once I’ve started separating my options and processing screens, plugin development has gotten so much easier to manage. Also, less buggy.

How do you maintain separate Relevanssi and Relevanssi Premium code bases?

Thanks again for the Relevanssi efforts.

Ciao,

Michael

I’m wondering why not make the premium portion a single or two file include on the free?

This way, maintenance would be easier since code sharing would be in place.

I’d be happy to help with either version to give you a baseline for the Ajax indexing and options page. To me, this would be a fun project since I use Relevanssi for clients and myself.

I’d like to start work with the WordPress SVN’d version so that we could have beta testers more readily ensure our efforts are solid. Then I can help you find an easier way to manage including the premium options.

How are you handling bug reports? I never noticed if WordPress had a bug reporting option for us plugin contributors.

Your thoughts?