The issue was originally reported 10 years ago with a proposed fix that does work:
https://wordpress.org/support/topic/restrict-path-logic-does-not-work-correctly/
Hi @lucasw89 ,
Thanks for following up, and you’re right to hold us to account on this one.
Some honest context first: Table of Contents Plus was abandoned by its original author, and our team took the plugin over more recently to keep it alive. We do plan to maintain and support it going forward.
On your report specifically: it is reproduced and logged in our internal tracker, and I’ve updated it this week with a full technical write-up and a proposed fix for our developers. For what it’s worth, the root cause turned out to be that the path check compares against the full request URI from the domain root, so on sites running WordPress in a subdirectory the option can never match. The older patch you linked unfortunately isn’t the right fix. It effectively disables the restriction rather than repairing it, which is part of why this lingered.
I can’t promise an exact release date, but this is now in front of our development team with the fix worked out, not sitting at the bottom of a backlog. A year is longer than this should have taken, and I appreciate you staying on it.
Hey @lucasw89,
Thank you for bringing this to our attention. I’m Arnaud, the Product Manager for AIOSEO.
I’m currently working on an update for the plugin and will make sure this gets resolved in that update. Expect it to land later this week or next week by the latest.
If you have any other feedback for us, let me know!
The bug has now been resolved. 🙂
Hello! Nice upgrade, the new design is a lot more modern and user-friendly. However, the described bug has not been fixed. The original patch that you said doesn’t work, works for me though. When I don’t use it, my site is showing TOC on the blog main feed using the TOC of the latest post.
When I use restrict path “/blog/”, it doesn’t hide it from the blog feed but stops showing it even on actual blog posts. So the only solution so far that worked was that patch that I referred to. With restrict path set to “/blog/” it hides it from the blog feed while preserving it for posts. I’m attaching screenshots.
https://ibb.co/SwKh1794
I’m not entirely sure why it shows on the /blog/ feed in the first place, since I only have it enabled for Posts…
-
This reply was modified 3 weeks ago by
lucasw89.
Hey @lucasw89,
Thank you for getting back to me.
I actually misunderstood your original issue from the fix you had referred to, because the fix you linked to targeted another issue but it probably coincidentally also fixed what you were experiencing.
The reason why the widget showed up on the blog page is because WordPress returns the first post on that page when you call get_post, which historically has been incredibly annoying behaviour for plugin developers because that’s obviously not the actual page you’re on.
Anyway, I released another update last week and you should be solid now. Can you check and see if the issue is resolved?
