Apologies, I didn’t explain that very clearly. We were filtering a taxonomy field by a term. The term slug was changed, after which posts tagged by that term could no longer be picked. My initial thought was that if it was using the term ID, surely it wouldn’t falter when trying to filter posts, even if the slug had been changed?
Thanks for your quick response John. The website isn’t using Woocommerce and it’s not do with the theme or any plugins, I know that much as I developed the site myself from scratch.
However, to answer your question, the site is using the following plugins:
- ACF Pro 5.3.5
- Disable Comments 1.4
- Yoast SEO 3.1.1
I’d refer to @jacobajjarapu and @trainoasis’s comments – it’s working fine in local and staging but not in production. The fields definitely aren’t being used elsewhere. It’s a strange one. For now I’m just going to hardcode the fields as a workaround, but it would be great to know if anybody else is experiencing this issue.
Hi John. There are two fields, one is basket_url and the other is checkout_url.
Any ideas?
I experienced this issue yesterday on a client’s live site – we tried to update a URL field in a custom options page with a new value and instead of saving the changes, it threw out a 404. The odd thing is that the URL field was working fine in local and staging environments.
Any ideas? Does anybody know if a fix is being worked on for this?
