threadi

Yes, I can see that now on Newscrunch. But that’s all I’ve seen so far. There’s actually a lack of compatibility with changes in WordPress 7.0, which needs to be addressed by the theme developer.

If you want to remove a specific style sheet from the output, you need to use its handle in wp_dequeue_style(). However, there is no handle named “twentytwentyfive” when using the default TwentyTwentyFive theme.

With block themes, CSS styles are dynamically generated from the templates and the settings in theme.json. No files are created in this process; at most, the style.css file from the theme or from plugins that supplement it is used. If you’re looking for something like that, you’d have to switch to classic themes (such as the last classic default theme, TwentyTwentyOne).

What you enter as Additional CSS is simply an addition to the styles that WordPress already generates for you via the theme. You can store additional CSS in the Additional CSS section – as the name suggests.

I’m a bit unsure what you’re actually getting at here. If you don’t want the settings in Additional CSS to appear on the front end, simply leave that field blank. No coding is required for this.

And what do you mean by “external CSS” in this context? By that, I mean a style specification that is loaded from a different server. For example, if you run your website at example1.com, you could include CSS from example2.com – and you want to prevent that? Perhaps some specific examples from you would be helpful to move forward here.

I don’t see any option for that at the moment, so I’d recommend submitting your request to the Gutenberg team: https://github.com/WordPress/gutenberg/issues

First of all: there is still no AI in WordPress Core. What has been added are AI connectors. These enable a standardized integration of AI, if you choose to use it. It’s like a train station, where tracks are needed for the trains. The station is WordPress, which provides the tracks for the trains.

If you want to disable the AI connectors, simply add the following line:

define( 'WP_AI_SUPPORT', false);

The other lines you mentioned simply suppress the visible output in the backend (though nothing will appear there).

Alternatively, you can try this plugin: https://ww.wp.xz.cn/plugins/turn-off-ai-features/

However, this only applies to AI connectors that support this setting. Currently, these are all the ones recommended by WordPress itself. If additional connectors are added in the future, they will also have to comply with this.

Plugins that include their own AI integration are not affected by this setting at all.

If you’d like to see changes made here, it’s best to submit a request on Core Trac. I haven’t been able to find anyone else there yet who has requested the same thing: https://core.trac.ww.wp.xz.cn/newticket

You made a typo. The correct code is:

define( 'WP_AI_SUPPORT', false );

Once this is set, you will no longer see any of the default AI connectors under Settings > Connectors, and consequently, you won’t be able to use them. The view will then look like this (if you don’t have another plugin that acts as a connector and ignores this constant):

https://snipboard.io/Vc9nI3.jpg

As an alternative to the constant, you can also use a hook: https://developer.ww.wp.xz.cn/reference/hooks/wp_supports_ai/

Or a plugin: https://ww.wp.xz.cn/plugins/turn-off-ai-features/

This spelling, which can be seen there, doesn’t appear anywhere in the WordPress core: https://github.com/search?q=repo%3AWordPress%2FWordPress%20uploading…&type=code

However, it does appear in Elementor, which you’ve apparently activated. I would therefore recommend that you contact their support forum: https://ww.wp.xz.cn/support/plugin/elementor/