James Maiden

This as fixed it for me. Thank you very much for your help and your very useful plugin.

I was afraid you’d say that ??

OK, so “hse-bulletins” and others I’ve tried are definitely taxonomy terms.

Is the functionality restricted to standard WP categories and tags or should it work with custom taxonomies and their terms too?

Sorry Wayne, I hadn’t checked the box to activate the support log.

You should have received something this time.

Hey, thanks for following up.

I’ve installed that plugin and just run another test.

See what you can see ??

N.B. this is a custom taxonomy we are talking about. I am using Toolset Types plugin to create my custom posts and taxnomies.

Hi Wayne,

Thanks for the response. This looks like it should do it, but I’m not having any success.

Following your suggestion, the post is being created as the correct post type, but the category is not being assigned and the category slug is being included in the post title.

I’ve tried the brackets approach as suggested and also the colon approach, with cat-slug, cat name and ID.

All no joy. Any ideas?

thanks.

Thank you very much for the response and the good news about the future plans.

After flicking around, this had something to do with the difference between live and development sites.

To create the dev site in this instance, I copied the files and database of the live site.

The dev site customizer said there was no background image set (so there was no “remove image button”), though it was showing the image on the site’s frontend. The dev site customizer css was linking to the image file on the live site.

To get round the problem here, I had to add a new background image in the customizer and then remove it.

Great. Thanks.

Keep up the good work ??

That fixes it. Thanks.

Out of interest Bruno, did you ever figure this out? I would like to know the same.

Thanks for helping confirm an issue.

I can say the problem still persists even in version 4.7.2

What’s really weird about this is is that even when I deactivate all plugins and switch to twentysixteen to rule out a possible theme/plugin conflict, the problem is still there.

I think we can assume that 4.7 is working ok on the whole – I see it working fine for some sites using any number of plugins and different themes.

I wonder if there is something with the update process causing an issue. Fundamentally it looks like its a call for jQuery that’s the problem. I have thought that it could be a browser caching issue – an old call for jQuery lingering somewhere. I have tried clearing the browser cache on one site, but that didn’t help.

Still holding back updating a lot of sites because of this.

Good to know I’m not alone, though “updating a plugin (any plugin)” didn’t fix it for me on one out of two sites I tried it on.

Hi,
Thanks for the response.
Unfortunately no, deactivating W3TC doesn’t solve this.

I tried deactivating a few other plugins too, without luck. I also reset permalinks with no joy there either.

Hi there,

I had this issue too and resolved it as follows:

It looks like you have to uncheck the WooCommerce checkout settings box that forces SSL for checkout pages.

If you use the https redirection plugin to redirect to https, you don’t need to use the WooCommerce setting to force SSL on checkout pages.

Could you please share how you resolved this?

I seem to be missing the same thing you did.

Thanks