kevin_linden

Hi, smswise. I’m getting the same error. Even my hosting provider is complaining. Have you found a solution?

• This reply was modified 2 years, 5 months ago by kevin_linden.

I managed to make the space go away by adding this “additional CSS” in the customization section:

.wp-embed-responsive .wp-has-aspect-ratio .wp-block-embed__wrapper:before {
content: “”;
display: block;
padding-top: 0%;
}

However, I’d still like to know how the problem could be solved (by a theme update, perhaps) without me having to mess around with custom CSS, which might have as yet undiscovered negative effects elsewhere on the site.

Thanks!

What trianfeng wants is for images in posts and pages to always by default be linked to the full size media files, so readers can click on them to see the full size version.

Since Gutenberg/Block Editor has arrived, all images inserted into posts and pages are, by default, now linked to “none,” meaning linked to nothing.

What he (and I) want is some way to make them default to linking to “media file” instead of none when they are inserted in the editor page.

In the Classic Editor, WordPress remembered your last-used preference for this. Now it doesn’t do that anymore.

A solution would be most helpful.

• This reply was modified 5 years, 9 months ago by kevin_linden.

Oh, and by the way, it was removed in 4.9. Earlier versions had it.

Removing the unlink button from the main toolbar was a terrible mistake. I OFTEN have to remove all links from a large swathe of paragraphs of text, and it is CRAZY to force me to do each one individually, or ask me to install and configure a plugin on my many sites to get back this needed functionality. PLEASE, how can we convince WordPress to give us the unlink button back?

Okay, I just upgraded to 4.4.1 and this bug is now fixed. Thanks to the WordPress team for noticing!

Kevin.

Okay, I discovered the problem — though I don’t understand it. The site owner had put a custom .htaccess file up which contained some supposed security enhancements. When I reverted to a standard .htaccess file, the editor worked again. I don’t know why that file suddenly started causing the problem, though, since it’s been in use for over a year without issues. Perhaps the hosting provider made a server change that made it misbehave. Mysterious.

That solved the problem — thanks, James!

I think the best solution for this is to add the following line to your wp-config file:

define('TEST_COOKIE', 'wp_test_cookie');

This — by renaming the test cookie to a name that does not include the string “wordpress” — will make it so Super Cache doesn’t think you’re logged in when you’re logged out but on a login page.

Works for me!

I think the best solution for this is to add the following line to your wp-config file:

define('TEST_COOKIE', 'wp_test_cookie');

This — by renaming the test cookie to a name that does not include the string “wordpress” — will make it so Super Cache doesn’t think you’re logged in when you’re logged out but on a login page.

Works for me!