greentp

Thanks. It was just filling up my log file. I’ve now changed my settings to exclude NOTICE errors. I look forward to the fix in due course.

Many thanks for the quick fix. 3.7.7 seems to have solved the problem.

Ok, thanks. I think what you are saying is that Appearance -> Additional CSS no longer works (without triggering the deprecation notice), but that Appearance -> Customize -> Additional CSS does, albeit without SCSS or LESS support. Is that correct? It’s a bit confusing!

Does it mean that I can’t add additional CSS without updating to a block-based theme? Or can I still add additional CSS to Twenty Sixteen by temporarily enabling the “Enhance CSS customisation panel” button to add the CSS and them disabling it afterwards to get rid of the deprecation notice?

I’ve investigated it a bit more and found that it’s nothing to do with wp_load.php and the PHP app. It was just the error handling in the app that was alerting me to the issue and I now see that the debug.log is filling up with similar messages when I am just in the dashboard. I have found this post but am a bit confused by it. I am using the Twenty Sixteen theme with additional CSS. What do I need to do?

• This reply was modified 5 months, 2 weeks ago by greentp.

OK, thanks.

I’m currently using the Twenty Sixteen theme. I suspect I’m going to have to update to a more modern theme which handles additional CSS in the currently approved fashion. Bit of a pain.

Deactivating WP Forms makes no difference, but deactivating Jetpack does, which is what I’d expect as the message is saying that “Jetpack no longer supports Custom CSS”.

Many thanks for the quick response. That seems to have fixed it.