Peter Wilson

The ads.txt file can be edited within the dashboard in the Settings > Ads.txt menu. You need to enter the contents of the file manually using required format.

The file itself can be seen in the root directory of your site by visiting example.com/ads.txt. The file is not created on your server and is virtual in the same way the blog posts, pages and other content are in WordPress.

I reached out to Jen Simmons on the Developer Experience team at Apple via Mastodon.

Jen has confirmed that the issue is due to a bug introduced in Safari 18 and a bug report has been filed on the WebKit bug tracker, see WebKit#280063. A minimal reproduction has been created by the WebKit team.

By root directory of your site, they are referring to the URL rather than file location. So having the contents accessible at https://culturematters.com/ads.txt is meeting their expectations even though it’s dynamically generated rather than a actual file sitting on the server.

@chrissmit, thanks for getting in touch.

The ads.txt and app-ads.txt URLs generated by this plugin are stored in the database similar to WordPress pages and posts. The files are not created so it’s expected that you can not see them when browsing the file listing on your server.

You can edit the contents of each in Settings > Ads.txt and Settings > App-ads.txt within the dashboard.

@devtat Thanks for getting in touch.

There isn’t an option to do so but you can add the following code to your theme’s function.php file or in a dedicated file within wp-content/mu-plugins.

This will remove the new actions allowing you to modify the parent’s of a page.

<?php

add_filter( 'page_row_actions', 'devtat_spo_page_row_actions', 20 );

function devtat_spo_page_row_actions( $actions ) {
	// Remove the move under sibling action item.
	unset( $actions['spo-move-under-sibling'] );

	// Remove the move under grandparent action item.
	unset( $actions['spo-move-under-grandparent'] );

	return $actions;
}

Hi @earthman100, thanks for getting in touch.

The team are aware of this issue and have a fix in the release queue for the next version. You can see the issue and the pull request fixing it on the GitHub repository for the plugin.

Sorry for the inconvenience, the next version should be out soon.

Thanks @tazling, are you able to share the Soundcloud URL you are testing with? That will make sure I’m testing what you are seeing exactly.

Hi folks, I just tested this after seeing the trac ticket and was able to embed successfully. I’m wondering if it was a temporary issue at Soundclound that has since been resolved.

Would someone be so kind as to test again to see if you’re still seeing the issue? You may need to do so in a new post as WP caches embeds in the post meta data.

Hi @adriantry

I’m an engineer at 10up and am working on a quick fix for this. Do you have a GitHub account I can use to ensure you get props for reporting this issue?

If you do have an account, you can link your www.ads-software.com account to GitHub by editing your profile.

thanks,
Peter

I’ve created a mini-plugin for site owners to use prior to the next WordPress release.

https://gist.github.com/peterwilsoncc/74ae0167e3a5d01502e7b1f94536a0fb

Hi Joerg,

I’ve attempted to reproduce this without success on a multisite sub-directory install but without success.

Are you able to help with the following:

* what type of Multisite step up is it: sub-directory, sub-domain or mapped domains?
* are you enabling RSA network wide or on each sub-site?
* any other plugins you have installed?

Hello,

I’m unable to reproduce this error, I’m sorry.

In your admin are you able to visit Tools > Site Health > Info (tab) and provide the following information:

* The version of WordPress you have installed
* The PHP version in your server (available in the Server section)
* All items in the active plugins section
* All items in the active theme section
* All items in the must use plugins section (if listed)
* All items in the drop-ins section (if listed)

This information will allow me to test on a WordPress configuration similar to your own.

In WordPress 5.2 a number of components were moved from the editor package to the block-editor package. Further details can be found on the Make/Core entry detailing the new package. It includes a list of all the items that have moved.

If your theme or a plugin includes any blocks that haven’t changed to use the block-editor packages and still refer the editor package then it will trigger the notice you are seeing on the block widgets screen.

If using ESNext syntax JavaScript, you can change the code import { Something } from '@wordpress/editor'; to import { Something } from '@wordpress/block-editor';

If using the current JavaScript syntax, references to wp.Editor.Something need to change to wp.BlockEditor.Something.

I tested this with a multisite install using the latest version of WP and was unable to reproduce the error, I’m afraid.

I ended up testing both sub-domain and sub-directory configurations and both tests were successfully running the AJAX request and returning 200 HTTP response codes.

It might be worth checking with your hosting provider to see if any configuration changes have been made recently. A 504 header usually indicates an error between the php server and the client.

Hi @bpathania,

I’ll test this on a multisite install. Are you using a sub-directory or a sub-domain configuration?

A 504 HTTP header usually indicates a proxy server is timing out but I’ll get back to you to ensure the web server isn’t the underlying cause of the issue.