[Andrew]

Oh that’s very interesting. Hmmm.

For the pro version, do you still have the type set to “Recipe (wprm_recipe)” instead of Post? Under source it should just be Post, and under Custom Posts include custom post “wprm_ingredients,” …then on the include/exclude tab make it only for category Recipe.

[Andrew]

Yes you’re right that the custom type wprm_recipes is typically associated with posts in the category called Recipes. What I meant was that I want to be able to make similar searches (not using the wprm_recipes type necessarily) in different categories. I want to be able to include (other) custom field types in other post categories. Anyway, sorry I wasn’t very clear before 🙂

An example of a search term that worked great in Lite is “sesame seed.” This pulled up a recipe that didn’t have that in the title, excerpt, etc, but was in the ingredient list. Since switching to pro, it pulls up no results.

[Andrew]

Thanks for checking it out and getting back to me so fast.

No, unfortunately that’s not the solution. I want it to be “posts” and then be able to restrict by category, especially because I will be using this same bar for other categories. This was actually why I bought the plugin — the Life version was doing such a great job and I wanted to create more search bars just like it but in different categories.

Anyway, if you’ve identified that the issue is with a bad import then perhaps the solution is to create a new search from scratch (instead of importing from lite)?

[Andrew]

You cannot access this content.

[Andrew]

Hi Ernest,

Thank you for the prompt reply! Yes, the custom field is selected (see attached screenshot).

I’ll include the login details in a separate, private reply.

Thanks!
Andrew

[Author]

Posts