Alex R

Nope, the problem is with outdated version of jQuery UI packaged with WP File Manager calling functions deprecated or outright removed by the current version of jQuery packaged directly with WordPress.

The JQMIGRATE log posted by @javierbermudez is likely the right path to resolve this. It shows that the jQuery UI included by WP File Manager is old and calls functions deprecated by the more current version of jQuery used by WordPress.

No worries, thanks again!

I thought I was basically giving a bug report to update WooCommerce’s built-in templates to better utilize its checking of default theme usage in order to conditionally add the missing template parts; is this not the place to submit such a bug report?

Hello! Thanks for taking the time to reply.

For clarification, I understand placement isn’t an existing table, it’s the slug for the custom taxonomy in the OP. I was hoping that I could subquery in the shortcode at least for the parent’s info, but if you’re saying that it’s either unpredictable/unstable results or not possible at all and PHP+SQL is pretty much the only reliable way to do it then I guess I’ll have to do it in PHP+SQL.

FWIW, I was looking to do it in the shortcode to have something more portable in the likelihood that I end up in the future having to work with WP installs that don’t allow me as much access to go a PHP or full plugin route. I am otherwise very comfortable working directly with PHP and SQL to make things happen and very often need to do that anyways. I guess the real request here is asking for built-in support for custom taxonomies to not only have their parent’s term_id accessible but technically their whole ancestry as some sort of taxonomy.ancestors array of full taxonomy objects or something and for the shortcode to allow such a query (e.g. taxonomy.ancestors HAS-SLUG 'slug-name' or 'slug-name' IN taxonomy.ancestors.slug or something). I know I could code this in PHP, but it would certainly be a nice-to-have

Thanks again for your advice, Jory, and Pods is still a great solution to the common problem of needing many custom types in a WordPress!

• This reply was modified 3 years, 11 months ago by Alex R. Reason: Added clarification

While the solution to modify a child theme is usable, it is obvious the issue isn’t with Twenty Twenty, the issue is with WooCommerce and @yazdaniwp could not understand that.

Twenty Twenty is a default WordPress theme and only pages that are specific to WooCommerce (shop, item details, etc) have the issue of not showing footer widgets or menu. Not all of them, though, “cart,” “checkout,” and “my account” pages seem to be just fine because they are regular pages with woocommerce shortcodes in them. I just came across this issue a few minutes ago myself (2020-12-10 3:00am US eastern) and so far am disappointed that WooCommerce pages actually do this at all, and even remove the “Template” option from the Page Attributes meta box even though Twenty Twenty is the active theme. The culprit looks to be WooCommerce template files like woocommerce/templates/single-product.php and such only calling get_header and get_footer with no help from the WP default theme support functions in getting any other relevant template parts, as well as not checking for various other theme supports apparently.

I’m running WooCommerce 4.8.0, WP 5.5.3.

• This reply was modified 3 years, 11 months ago by Alex R. Reason: Added clarification