Actually, what I did seems to have broken all the security for the site, the bands private audio files started showing up in a lot of listings that the public can see, here’s the code I added, is it wrong?

function wpmt_search_filter($query) {
if ($query->is_search() && $query->is_main_query() || is_archive() )  {
$query->set('post_status', array( 'publish', 'inherit' ));
$query->set( 'post_type', array( 'post', 'attachment' ) );
}
return $query;
}

add_filter('pre_get_posts','wpmt_search_filter');

One of the reasons why I’d rather not use category as the taxonomy for audio items is that the band already use category for their blobs, so I have to show the category widget in the sidebar and unfortunately adding category to audio items causes them to be displayed to the public, clicking on them allows any not logged in user to be able to play these “group only” files.

Ah, it’s not that simple it seems. I assigned a custom taxonomy to attachments and assigned taxonomy terms to each of the audio files. I have a taxonomy sidebar widget which is displaying the taxonomies but clicking on them just returns a page not found error.

I also assigned the default categories to attachments but whilst the items appear in the categories list, clicking on them just returns a heading of the term with no content.

I think I need a template page to display the attachments (attachments.php or similar) but I’m lost as to what to add into this to display (1) the list of attachment category items, and (2) the single attachment view.

Hi Brajesh,

I’m not sure what happened but today it’s all working! maybe I forgot to save my edit before transferring it to the server? I’m not sure. But anyway, issue resolved.

It works pretty well with Simple Front End Post, I was expecting a problem, but if the user enters a post with a duplicate title it takes them to the backend edit post page and gives them the message that they can’t post with the duplicate title. That’s a lot better than I was expecting. In an ideal world it would flash a warning while the user was creating the post in the front end but that’s probably for another day.