chumtarou

Hi AITpro,

The host is currently looking into this and hope to have further response this week. I can either add more to this or email you privately once I learn more.

Good news is it appears to affect 1 out of the 4 hosting companies I’m currently using. Aside from this one having issues, the others don’t seem to have any issues with .53.1.

Hope I’ll get a response. Will keep you posted.

I’ll keep you posted – I have contacted the hosting company and will get back to you as soon as I get their response.

Okay, I can confirm that this causes the Error 500:

RewriteCond %{REQUEST_METHOD} ^(HEAD) [NC]
RewriteRule ^(.*)$ - [R=405,L]

And, adding this does not cause an error:

RewriteCond %{REQUEST_METHOD} ^(HEAD) [NC]
RewriteRule ^(.*)$ - [R,L]

I have now added this to the custom code section to ensure it updates like the above going forward.

Thank you!

I have started removing each item one by one and it appears this code may have caused the Error 500:

#RewriteCond %{REQUEST_METHOD} ^(HEAD) [NC]
#RewriteRule ^(.*)$ - [R=405,L]

Everything else is left as is.

Strange…

Thanks for your support – I have followed these steps and still shows Error 500.

However, if I go back to .53 it works okay. Would there be something between this and 53.1 that could affect the site? Thanks

There is a specific support post on this topic at Elegant Themes support site. Login and search for “Divi Backend Stuff Showing In Yoast” and you’ll see the topic. Appears there is no solution yet but Yoast and Elegant Themes are looking into it.

Thanks for your post – I have the exact same issue and have been trying to find a solution online. Hope there is a solution as it is affecting 404’s in Google Webmaster Tools.

Not sure this will help anyone but here is what I have done:

1. I have added this to my functions and removed the previous shortcode method.

add_filter("user_specific_content_blocked","show_login_form");
function show_login_form(){
    return wp_login_form(array('echo' =>false));
}

2. since this method no longer allows me to show a message and only shows the login prompt, I have added other code in the page template to show a welcome message to logged out visitors explaining this page is only visible to authorized users:

<?php
if ( is_user_logged_in() ) {
	echo '<a href="' . wp_logout_url() . '" title="Logout" class="logoutbutton">Logout</a>
';
} else {
	echo '
	<h1>message for people that are not logged in here</h1>
	';
};
?>

The reason for this is if I added a do_shortcode in the template, it duplicated the login form so I used this method instead.

Sorry to ask again:

Is there any way to add a shortcode in the Global Blocked Message section.

My goal is to add a login form on the page someone is trying to access.

With this shortcode, it allows me to ensure the visitor can fill in their login details and only view that page without seeing WordPress’s backend. They only see the page.

Example:

<div id=”loginmessage”><h1>Private page. Authorized access only.</h1>

[my-login-form]

In 1.0.3, the short code worked well. In 1.0.4, the shortcode no longer works.

If there is a better way to do this, could anyone suggest a way to add a login form the the page without being redirected to WP’s backend?

Thanks everyone

Just to be more clear, I have my own shortcode for a login form in Functions called [my-login-form]. I had put this into the Global Blocked Message section.

However, since 1.0.4 the ability for shortcodes in this section stopped working.

Hi Ed,

I have am now experiencing this as well with installations that use the Featured Image function. Unfortunately, I’ve had to remove BPS for the time being to work around this and would be great to know if there is a way to keep BPS on all sites.

I’ll send you the web url by email in a moment.

Thanks!

LOL too true. This makes me think of Missing Missy ?? If you haven’t read it, I think you’ll enjoy it.

LOL agreed – your clean interface is what makes it a great for us on each installation and much more straight forward to clients which we appreciate. And *really* appreciate your care and time to consider this option for a future version.

Cheers!

Much appreciated thanks!

Would be great if future updates to this plugin won’t re-comment out options -indexes so that installations we don’t check often won’t become open. Just in case we’ll add .htaccess to non-wp folders but thought I’d mention in case you were designing a new function for this.

Again, thanks for your plugin – I’ll be asking clients to go your way for security services when they are live.