ronald.fuquay

6.9.1 seems to have fixed this issue. Thanks for the quick fix.

You can download older versions of WooCommerce here: https://developer.woocommerce.com/releases/

This can temporarily fix your site while they are working on this.

You can download older versions of WooCommerce here: https://developer.woocommerce.com/releases/

I am having the exact same issue and had to revert back to an older version myself until fixed.

Also also… I know blocks are the new thing that is meant to replace shortcodes, but the website this will be developed for is using a page builder that doesn’t work with the Gutenberg editor (Divi Theme). If this was a fresh website build I was doing I would have planned to use a block instead of a shortcode.

Also, if you think this could be handled better by not using Vue.js, please feel free to let me know. I know most of what I am using Vue in the plugin can be handled with generic javascript. I just used it for its ease in implementation and my (limited) previous experience using Vue.

I think its fixed, ty!

Hmm interesting, ok I will see if anything else is trying to install font awesome!

Thanks for the direction to look.

@mrtom414 thanks again! That is definitely an interesting way to do it, and one I will likely look further into if there isn’t a way to actually set new registrations as pending for approval.

I know setting a specific user role registrations requiring approval should be doable as many membership plugins have this functionality. I am just hoping there is a snippet out there that lets me do that.

As an update, I found this answer on stack exchange. Is this putting me down the right track? is there anything wrong about his code?

Thanks @mrtom414 but I already am using members to create my custom role. I just want to set things up where new registrations have to be approved before their account is active.

Perfect! Thanks

Awesome, thanks @westonruter! I think that sent me down the right path

Ok thanks, that helps

Hmmm… I think I see what you’re saying @ikaring !

I would have to make the CPT hierarchal, then I could have two different post templates, one for series (so it displays its children to click through to) and one for single sermon.

Lastly, I could just throw in a checkbox to disable the series parent from the rss feed so that it doesn’t populate in our podcast.

Thank you so much!

• This reply was modified 5 years, 7 months ago by ronald.fuquay. Reason: forgot to mark as resolved

I just realized that the image I posted above had some conflicting naming conventions (sermon vs message) here is an updated diagram with unified terminology. Link to Diagram.