blueclochard

Apologies, I see that version 4.6 had the same third party javascript issue already. Question would still be the same though. I have no other plugins that depend on scripts from other website.

@mailgun Could you please explain how wp-config.php can be used to set different settings for different domains? At the moment the FAQ only explains how to configure it globally. That is only useful if you use the same e-mail address for all sites.

Also, many of here do not understand why the settings page was removed. Even for advanced users, changing settings on a settings page is easier than changing them in wp-config.php.

The developers behind Gutenberg unfortunately seem to be on a holy crusade to destroy the code editor. In the initial phases until about one year ago everything useful was still there, such as the button to add images and the ability to insert links. The reason they removed them was to encourage users to switch to the Gutenberg visual editor with all those nice blocks.

A few months ago they also greyed out the button to add blocks in the code editor. A few weeks ago they discussed removing the document outline and block navigation buttons. I guess the next step will be to remove the code editor altogether.

Seriously, why would anybody want an archaic code editor when you can work with blocks instead!!?

Fixed in 1.6.1, thanks!

@rhinogroup, thanks for this solution. I still would like to hear from Mailgun whether this was intentional or not though.

Can confirm. I have exactly the same problem. Disabling the plugin or downgrading to 4.5.2 solves the problem.

Hello Gioni,

Since upgrading to WordPress 4.4.1 I have the same problem as romulis, but I cannot seem to fix it. My White IP Access List is empty, yet I am still taken to the login page when I try to access /wp-login.php. This also happens when I access /wp-login.php from a different computer with a different IP address. Custom url login works, but the Disable wp-login.php option right underneath it does not.

I also tried loading the default settings but that didn’t help. Is there anything else I can try? I remember it worked before with WordPress 4.4.

AITpro, your solution works indeed. And it’s a better solution than using .htaccess. Thanks! Marking this topic as resolved.

Okay, I tested WP 4.4 with default settings, but just found out that the X-Pingback header is not set if you disable pingbacks. This was fixed for 4.4 in ticket #20226. So that fixes that.

As for the REST API HTTP header: I tried for hours, even with the wp-headers filter as bcworkz suggested, but I just can’t seem to find a working solution.

In the end I opted for a simple workaround by adding this line to .htaccess:

<IfModule mod_headers.c>
Header always unset Link
</IfModule>

Even though it works for me, it will not be a solution to everybody. You need to use Apache and have mod_headers enabled. There are probably similar ways to unset headers on Nginx and ISS though.

If anybody still finds a way to disable this header using functions.php, please report back so that I can mark this topic as resolved.

Unfortunately that is only for the header section in the HTML. I still have not found a way to remove the HTTP Headers.

Hello WatCystal,

You can use these lines to remove the REST API lines from the HTML Header:

remove_action( 'wp_head', 'rest_output_link_wp_head', 10 );
remove_action( 'wp_head', 'wp_oembed_add_discovery_links', 10 );

That works for me at least. Please report back if you also happen to find a way to remove it from the HTTP Header!

Hey romzen,

Thanks for your reply! I had this info already though. It disables the REST API and gives this message when you try to access https://www.example.com/wp-json/:

{"code":"rest_disabled","message":"The REST API is disabled on this site."}

The HTTP Header pointing to it is still there however, so unfortunately it is not a solution.