gtrout

I figured out it was a conflict with the plugin Intuitive Custom Post Order, which was rewriting the query_vars for the search results to be by “menu_order” rather than the orderby specified. I’ve disabled the sorting, but I was wondering if there’s a hook in Relevanssi where I can disable that filter for search results only?

here’s what I added to disable the offending orderby:

global $hicpo;
remove_filter( 'pre_get_posts', array( $hicpo, 'hicpo_pre_get_posts' ) );

Thanks for taking the time to respond. I don’t think I’ll be able to wait for a new version for my current project, but I’m sure it would be a useful feature for others too! Thanks, again!

Thanks for the reply!

I don’t think this solves my problem, though. I’d really need to offer an alternate price in points along side of a regular USD price. A straight exchange rate won’t work because the exchange rate isn’t the same for all products:
Product #1: $12.95 or 100 points (exchange .1295)
Product #2: $9.99 or 200 points (exchange .049)
Product #3: $13.99 or 300 points (exchange .046)
Product #4: $65.00 or 600 points (exchange .108)

We’re trying to use BadgeOS to offer rewards for completion of certain tasks but we want to offer tiered rewards so that users can do one set of tasks for a small prize or save up and do multiple sets for a larger prize.

Just as another data point: same issue here and unchecking “find and show hyperlinks” seems to have fixed it (thanks mlustig!).

I was having a problem with the login widget returning me to a post detail page because of the is_home condition in wp-members-sidebar.php:73. This was because I’m using the Showcase Template from Twentyeleven. I changed the first if statement to use is_front_page instead and it seems to work fine.

Thanks for the great plugin and awesome community participation. Devs like you are what WP is all about.

One note: the fix applies to all new posts, but I found that if you go back and edit posts that were made before the fix, they still reproduce, so just keep an eye out for that.

I tested for that and didn’t have that issue. Is it possible that the ones this is occurring on are ones that were updated between when you upgraded to 3.1.3 and when you had the version with the fix.

I have the same problem – the development version fixes the problem on new posts but old posts are still duplicated on update.

Thanks for this. For anybody else, replace lines 73-75 with his code. And add the action code at line 33.