Sermons should save content and excerpt into proper places

[nikola3244]

• Remove sermons rendering into post_content and post_excerpt
• Save content into post_content (instead of sermon_description)
• Save excerpt into post_excerpt (instead of sermon_excerpt)
• Also, make sure that content is also rendered into sermon_description, for backwards compatibility

cc-ing @robertmain

[robertmain]

Related to #183

[robertmain]

Just had a bit of a revelation with this one. I realised what post_content is being used for.

It looks like WP search doesn't search wp_postsmeta by default. The workaround for this appears to be to embed that data into post_content and then put the actual sermon text elsewhere (in this case in sermon_description). I'm wondering if something can be done to remedy this in a better way.. 🤔

[nikola3244]

Yessssss, that's it! I completely forgot why I did it, until now. 😆

If you go back through commit history (and support forum threads) - I was saying exactly that - that we are making WP search work (it's also in changelog)

[robertmain]

I guess my next question is where do we go from here? I'd say we have a few different options:

1. Do nothing. Keep things as they are. Actual post content goes into wp_postsmeta as sermon_description. I'd advise against this if at all possible not least because it would make Remove CMB and add our custom code for meta fields #190 more difficult

2. Try and intercept WP search and bolt-on support for searching wp_postsmeta. Not ideal, but I guess there are worse solutions

3. Drop first class support for search, put our content in post_content and recommend that users install a third-party search plugin such as Relevanssi or some such. This would be my preferred solution because it would be the cleanest imho (though I appreciate you do have obligations to your users to support existing features).

I suspect the second option would be rather difficult to do well because of the fact that WP search does full table scans and has no indexing support.

[robertmain]

Btw, "save into post_excerpt instead of sermon_excerpt" can be marked as complete on this issue

[nikola3244]

Thanks 😉

Let me know if you are waiting on me on something, I may have missed it in the ton of emails

[robertmain]

I'd be interested on hear your thoughts on the previous comment. #184 (comment)

[nikola3244]

Hahah, I knew that there was one, and it was right in front of me 😆

Okay:

1. That's not a bad idea, if second one is too complicated to be implemented. I'm just not sure what issues would be with Remove CMB and add our custom code for meta fields #190?
2. I like that idea, and this filter looks promising
3. I really don't want to require users to use 3rd party plugins to have some basic functionality of the plugin

[robertmain]

Well, I'd prefer not to do option 1 if possible since it isn't really a solution. Though, if we do end up doing that I guess we can close this issue.

That leaves us with the second and third options. The third is probably the cleanest solution, though like I said I understand your position of not wanting to require users to use 3rd party plugins.

The second is a workaround, but I'll look into it and see how things are.

PS: We can probably get rid of the first checkbox in the OP as it's a duplicate.

[nikola3244]

Alright, if we do second one, we'll just need to add another bit to the SQL query, doesn't seem too hard.

Regarding third option, if you'd like that option because of (possible current) incompatibility with that plugin - let's just make it compatible 😉 (open an issue, if there's a bug)

PS: First and third checkboxes aren't duplicates. First one is about removing plain text rendering of the Sermon Manager's view, second one is about saving the content into the same place

[robertmain]

My only concern is potential performance problems... We'll see I guess...