rbaugh

You can try and use this gist to help you out. I am doing this call in my CPT class. The issue-section is a query_var that I use to connect to a taxonomy and what I use to load in the template.

This doesn’t load in the template from the plugin into the FSE and it doesn’t allow for making modifications through FSE, but it does allow for overriding the template in the theme. SO you can at least have a template in the plugin and then override by the theme. While you can actually make the edits to the theme template, they do not render based on this code.

I haven’t gone back in to see if I can locate the modified theme template through FSE to load it instead of the actual file. Just have to lookup the wp_template post type that matches the file name, but not sure just yet how to allow for adding other FSE templates to this.

For additional reference, using the cpt-slug as my CPT slug, the default block templates would be $theme/templates/archive-cpt-slug.html and $theme/templates/single-cpt-slug.html. For the url call where I want to have the taxon appended to the end of a post item’s url, I would then want to load in a template like $theme/templates/single-cpt-slug-{taxon-term}.html or $theme/templates/single-cpt-slug-{taxon-name}.html. This would allow me to render out a block template that is based on the taxon name or term.

• This reply was modified 1 year, 6 months ago by rbaugh.

Sorry, I didn’t get any notices of your replies. The site does not have any folders as part of the root url. It is just the domain.

When I was trying to figure out what was going on I was outputting the value of the url to check it as I was under the same impression as you. That maybe the url wasn’t matching. But it was matching. I was outputting the value of the permalink in the set_requested_permalink function.

I went back and copied this value from the logs I still have around and it is matching the value that was set in the filter rule.

Jeff,
The changes seems to get things back, but I think the issue is in the get_bloginfo function. When I applied 10.1.8 and had the issue, I just changed the code back in the MU class file and everything started working again. I see you added checks for the Server variable first and then resort to the get_bloginfo function, but I wonder if that may cause the same issues in which this still ignores the code this plugin provides and loads all plugins as default. It may not be needed for a CLI call, but just sharing. I haven’t dug in further, but wonder if somehow the get_bloginfo is loading in all plugins as that line causes your plugin to not function as needed. If I just replace the if statements with the one line from 10.1.8 it breaks the plugin again.

I seem to have an issue with the latest change. While the code may be able to get the url, it seems to cause issues in which this plugin isn’t limiting plugins as it once was. If I revert back to 10.1.7, the plugins disabled in the filters are working again, but not when 10.1.8 is installed.

Once the transients were cleared, the DB update complete showed and the WC DB Version is not matching the WC version.

Thanks for the info

Some of the support report I didn’t want shared on the public since I am managing for a client. But I will try the transients and see what it does. I had cleared the memcache in case it was something with that, but nothing changed.