thoughtwell

Yes, that’s it. Hmmm. I did try doing due-diligence and searching topics but nothing came up in the forum. Shortly thereafter, I found several blog posts from other devs discussing this issue.

No worries. I ended up just eliminating the widget area altogether by unhooking it in my theme and hard coding this into the functions file, then re-hooking back into the header. Probably for the best anyhow, as I don’t want a client fidgeting w/ this. Were this a theme for the theme market, it would probably be a bigger problem, but since it’s a custom theme for a client, I believe having it hard coded is going to be a better solution anyhow.

I’ll mark this as resolved, at least for my particular needs. Thanks!

Okay, so instead of all of this, I ended up finding the genesiswooc_product_archive and genesiswooc_content_product functions (thanks, hookr.io) in the template-loader.php file within the plugin and copying those functions over to my template.

I then removed the title and archive description output from both those, then renamed them and stuck the revised functions into my template page where the OG code went. Since this is where the title and description are declared and that bit was removed, there’s no need to remove the action responsible for this higher up in the template, so I deleted those.

Because I renamed the functions, I don’t have to worry about updates to the plugin effecting this, but I guess I will need to keep tabs on any major changes to woocommerce and adjust my code as needed down the road.

A simple idea of how to remove the title through a hook like I’m able to do w/ the description would have been ideal to do what I wanted to do, but since that information wasn’t forthcoming (I’m kind of a novice, here), this solution will seem to do unless someone else can fill me on how that title is hooked into the page, since as a filter, all I was able to do was return false, and I didn’t want to completely take the title away.

• This reply was modified 9 years, 2 months ago by thoughtwell. Reason: made easier to read

Okay, checked settings and they are consistent w/ your suggestion. I am also using get_the_powerpress_content(); as mentioned in my code snippet… I’ve actually used several variations of it as well as the do_shortcode(‘[power press]’); tag/function and still no luck. I looked deeper at my code and the irony is, in the CPT archive where I use WP_Query, it will work. Where it’s not working (the deeper-level taxonomy archive page) I’m actually NOT using a new Query since it’s using the default taxonomy loop… so I was incorrect in my explanation. But still, no luck.

While it would be nice if I can get it working so we can have the audio player sitting in tandem with our video presentations, in all honesty, I kind of perceive this as being redundant when there’s a video sitting right along next to it. Most likely, a user will opt to utilize the video vs. an audio feed in most cases when they’re on site viewing content. The audio content makes more sense to use when off-site, and for that, it would probably be more to podcast users’ preference to have them subscribe to the podcast feed, directly using whatever service they typically use to consume this type of content.

Therefore, until I (or someone in your camp or out on the internet trying to do the same) can figure it out, I’ll probably just include a modal popup that pulls up the subscription options, calling that page content from the subscription page. I can still include the latest podcast within a player in the featured block on the next-level up (CPT Archive where it works).

This seems like the most logical workaround without reinventing the wheel. However, if you come up w/ a reason why get_the_powerpress_content(); won’t work on a taxonomy loop and the issue gets resolved, perhaps we can introduce the audio player later. It’s a compromise, but the modal subscription option should do… at least for now. Unfortunately, as more of a front-end fellow, I don’t quite have the skill-set to dissect the plugin’s code and figure this out.

Thank you, Angelo. Any and all help is certainly appreciated.

Hey Angelo, thanks for getting back to me on this. It makes sense what you said about using them (podcasts) in the past… it’s likely that back before the complete overhauling of the site, the church was using the sermons under the standard feed… which is good to know, because the media director and myself were kind of wondering where all those were going to.

I’ll follow your suggestion and just use the options tick box to turn it off on those other screens–most of the folks contributing probably won’t go turn it back on anyhow… but I would welcome your feature update for those using PTPs vs. the standard feed, as it would completely remove that std. entry box.

As I play around w/ the plugin a bit more, it’s beginning to make more sense… like I had noticed that the PTP editor carries over the same meta fields as the general editor, but it’s completely separate. This was a little confusing at first until I realized that it’s pretty much its own thing and the ‘standard’ feed is completely separate.

Thanks again for the fast response. I’ll look at future update notes to see if that feature becomes available if you have a chance to bake that in. As far as I’ve come across, this plugin is definitely the most full featured and seems to have the best workability towards integrating more on a theme level than any of the other plugins and services we’ve vetted.