Thank you and apologies for the delay in response. Our host only supports PHP 7.4 or 8.2 and our payment processor is blocking sites still using 7.4 in its next update, so unfortunately our hand has been forced. This isn’t a big deal as it doesn’t seem to have any ill effects; I just wanted to report the warning.
I’ve figured out how to trigger it but can’t work out why it’s happening. If a site visitor goes to:
/faqs/single-faq/FAQSLUGNAME/faq-category/FAQCATEGORYNAME/
Where FAQSLUGNAME is a valid UFAQ slug and FAQCATEGORYNAME is its valid category, the error appears in the log multiple times. The displayed content is just our existing /faqs/ page (which is a curated Page full of 14x UFAQ category shortcodes which doesn’t trigger any error when visited normally via /faqs/). Significantly, the PHP warning appears 14x in the log at this moment, implying that it’s visiting /faqs/ via the /faqs/single-faq/FAQSLUGNAME/faq-category/FAQCATEGORYNAME/ referrer which is causing the problem.
What I haven’t worked out is why anyone would ever visit an address in that format in the first place. Our FAQs are all organized with pretty permalinks under /ufaq/FAQSLUGNAME so /faqs/ shouldn’t be happening. Is this because we have pretty permalinks enabled? The link doesn’t exist anywhere in our site db content so I’m trying to work out where it’s being generated to allow people to reach it. If I can find a way of disabling this behavior then nothing needs fixing.