askapache

Getting closer to 4.8 – eta 1m

Humblest apologies. Other than deleting your whole site, this is the worst class of bug.

Working on 4.8 now, its going to be a spectacular improvement ??

Patch sent. Deepest apologies.

Will have a larger update 4.8 by next week. I jumped the gun on releasing this version. Will fix it.

Here’s a simple fix for at least preventing these links from showing up publically.. haven’t found a fix for the editors yet.

/*
 * Never allow link placeholders to show up
 */
function askapache_filter_link_placeholder( $content ) {
	if ( isset( $content[10] ) && strpos( $content, '_wp_link_placeholder' ) !== false ) {
		// remove links to /_wp_link_placeholder by replacing them with WP_SITEURL
		return preg_replace( '#_wp_link_placeholder#', WP_SITEURL, $content );
	}
	return $content;
}
add_filter( 'the_content', 'askapache_filter_link_placeholder' );
add_filter( 'the_content_feed', 'askapache_filter_link_placeholder' );
add_filter( 'get_the_content', 'askapache_filter_link_placeholder' );
add_filter( 'the_excerpt', 'askapache_filter_link_placeholder' );
add_filter( 'content_save_pre', 'askapache_filter_link_placeholder' );
add_filter( 'excerpt_save_pre', 'askapache_filter_link_placeholder' );

And then in robots.txt

Disallow: /_wp_link_placeholder

Here is one thing I did to prevent these _wp_link_placeholder links from showing up publically..

/*
 * Never allow link placeholders to show up
 */
function askapache_filter_link_placeholder( $content ) {
	if ( isset( $content[10] ) && strpos( $content, '_wp_link_placeholder' ) !== false ) {
		// remove links to /_wp_link_placeholder by replacing them with WP_SITEURL
		return preg_replace( '#_wp_link_placeholder#', WP_SITEURL, $content );
	}
	return $content;
}
add_filter( 'the_content', 'askapache_filter_link_placeholder' );
add_filter( 'the_content_feed', 'askapache_filter_link_placeholder' );
add_filter( 'get_the_content', 'askapache_filter_link_placeholder' );
add_filter( 'the_excerpt', 'askapache_filter_link_placeholder' );
add_filter( 'content_save_pre', 'askapache_filter_link_placeholder' );
add_filter( 'excerpt_save_pre', 'askapache_filter_link_placeholder' );

And then in robots.txt

Disallow: /_wp_link_placeholder

:0 Turned out to be 5% user-error, 90% lack of UX/scope, and 5% lack of real-world QC IMO.

:0 Turned out to be 5% user-error, 90% lack of UX/scope, and 5% lack of real-world QC IMO.

https://core.trac.www.ads-software.com/ticket/36637

https://core.trac.www.ads-software.com/ticket/36637

fix??? My clients are pissed and now I’m having to debug 4.5 code on a fri night… I’ll post the fix when I get it

This is happening on several of my sites as well… working on a fix now.. This is actually the 2nd tinymce-related bug I’ve found so far that should have blocked the release of 4.5.

Bug seems to be from wp-includes/js/tinymce/plugins/wplink/plugin.js or wp-includes/js/wplink.js

Ok actually I just used my headers tool to check https:// wakeup and there is definitely a problem other than htaccess.

You need to find the error log for apache, and then paste in the relevant lines here. A 400 Bad Request error is indicative of a more serious problem than just a https => http redirect, or any redirect. You should also paste in your entire htaccess file (cleaning it to remove any identifiable strings).

Until this issue is resolved your site will be fubar

Code from Dipak is in the right direction, but I’d reverse the blocks. So:

<IfModule mod_rewrite.c>
# BEGIN Force http to https
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^(.*) https://%{HTTP_HOST}/$1 [R=301,L]
# END Force http to https
</IfModule>

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

But I really think your problems root cause/culprit is in your database. I posit that your db still has a ton of links to http references, such as to your media files like images. What you need to do is search your entire db for references to https:// and replace with https://. It’s not enough to just setup redirects to https, you need to link to https everywhere.

5.0.2 fixes the issues with the previous versions. What exactly did you dislike?