Gastón

??

@ampforwp Update: Mysteriously the fault no longer occurs. I tried again to activate the plugin in version 0.9.97.2 and now it does not give the Error 500. I really do not understand what happened, but it is already working fine again.

@ampforwp It is obvious that they have to revert some of the changes they implemented in version 0.9.97.7 or 0.9.97.1 (by the way, where is the changelog for these two versions?) Because until version 0.9.96.1 I had no problem.

When activating the plugin the /wp-amin is blocked and it gives Error 500, I can not continue administering the blog, and apparently we are not the only ones to whom this happens to us.

@ampforwp When I updated to the latest version, the administration panel started throwing me an Error 500. The web worked, but the admin panel did not. This forced me to have to disable the plugin manually by FTPing the server.

Please solve this bug.

I have the same problem whem I installed the lasted version 0.9.97.1

Confirmated! This Bug is solved in the 3.1 version.

Update: I discovered that if I go to: BPS Security – Setup wizard – Setup wizard Options, and changing AutoFix On by AutoFix Off, the problem no longer occurs.

What do I lose if I leave AutoFix Off?, is it safe to leave it like this?

Hi, thanks for the quick response.

With respect to php this is what I have:
PHP Actual Configuration Memory Limit: 256M
PHP Ver.: 5.6.30

The same day that BulletProof was updated, these plugins were also updated:
Yoast SEO
Relevanssi
EWWW Image Optimizer
Accelerated Mobile Pages
WP-Optimize

I do not understand why this happens, until version 2.9 everything worked wonders.

I only have the wordpress menus in the dasboard, when I click on any of the menus it does not show me anything in the center, except if I deactivate bulletproof that returns everything to normality.

Can it be a css failure or one of the improvements introduced?

I think I found the cause of the problem here: https://www.ads-software.com/support/topic/completely-broken-due-to-twitter-api-update?replies=9

Update! This is how I solved it:

For me this worked: disable the sitemap feature by unchecking the box, save, and then check on again. Now maps are visible.
Conclusions that I have drawn after repeated experiences of this kind: after any update or upgrade or big modification check the Yoast sitemap, because it’s not stable or reliable.
In these cases, might works:
1) Click save in the sitemap’s page settings
2) Click save in the permalinks plugin page settings
3) Disable the sitemap feature, save, and then check back

Solution published by @tizz, here: https://www.ads-software.com/support/topic/404-error-when-trying-to-create-a-sitemap?replies=20

Thank you @tizz! Your solution worked for me.

I also I have the same problem. I’m using W3TC, and you tried to make the change mentioned in this publication: https://yoast.com/xml-sitemap-in-the-wordpress-seo-plugin/ but apparently that’s not solving the problem.

What else I can do?