Plugin Support
Peter
(@petersquirrly)
👋 Hi Darren,
Please keep in mind that here we offer Squirrly SEO support, where the error you shared is not on our end, and we believe an old version of WooCommerce is being used.
Squirrly correctly checks the permalink structure using the get_sample_permalink function on the post ID to see what permalink structure is applied.
As can be seen in the error, it’s a WooCommerce function that appears to be outdated and doesn’t check if the link is null.
Why it ends up with a null link from the post ID is something we can’t know, because it depends on their site — maybe the products don’t have a slug set.
The best course of action is to update WooCommerce, check that the products have slugs, and under Settings > Permalink > Product Permalink, make sure a Custom Base is selected. (screenshot here)
Note! For any additional questions on the subject which is unrelated to Squirrly SEO, please consult with WooCommerce Support, a developer that has knowledge on the matter or you can use ChatGPT. Thank you for your understanding!
peter
we are using latest elementor and woocommerce and wordpress.
we are using cutting ours is /shop/ rather than /product/
does this need to match
i had spoken woocommerce and a developer and they both advised to make you aware of the issue.
we haven’t blamed you but your very defensive and I don’t like the attitude you have taken .
Plugin Support
Peter
(@petersquirrly)
Thank you for your message, and we truly appreciate you taking the time to follow up.
First off, we want to sincerely apologize if our previous response came across as defensive—that was not our intention. We simply wanted to clarify that the issue doesn’t appear to be related to our plugin. As a team, we sometimes receive support requests for problems that originate outside our scope, and that can be a bit frustrating on our end. Still, that’s no excuse for how it may have come across, and we’re sorry if it felt dismissive in any way.
Regarding the permalink issue, from the information provided so far, the error still seems to be coming from WooCommerce itself. Unfortunately, without more detailed context or logs, it’s difficult for us to offer further insight—and it does fall outside the scope of what we can support directly.
If you manage to gather more specific technical details or a reproducible scenario involving our plugin, we’d be happy to take another look.
Thanks again for your understanding.
Plugin Support
Peter
(@petersquirrly)
Even if this goes outside our support scope, we made an exception and tried to fix their problem from our end.
Please try the latest version 12.4.11 and give it another try. Let us know if that helped.
hi , i am not sure what you did but amzing work as they have gone
Plugin Support
Peter
(@petersquirrly)
That’s good to hear, and glad to help!