{"id":14742,"date":"2020-06-12T14:33:57","date_gmt":"2020-06-12T12:33:57","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=14742"},"modified":"2020-06-12T14:33:57","modified_gmt":"2020-06-12T12:33:57","slug":"wordfence-macht-probleme-mit-wordpress-5-4-2","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2020\/06\/12\/wordfence-macht-probleme-mit-wordpress-5-4-2\/","title":{"rendered":"WordFence has issues with WordPress 5.4.2"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline\" alt=\"\" src=\"https:\/\/www.borncity.com\/blog\/wp-content\/uploads\/2014\/07\/wp_thumb.jpg\" width=\"64\" align=\"left\" height=\"64\">[<a href=\"https:\/\/www.borncity.com\/blog\/2020\/06\/12\/wordfence-macht-probleme-mit-wordpress-5-4-2\/\" target=\"_blank\" rel=\"noopener noreferrer\">German<\/a>]The update of WordPress to version 5.4.2 may cause problems for some users who use the security plugin WordFence. The plugin cannot be activated or the page remains empty. <\/p>\n<p><!--more--><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" alt=\"\" src=\"https:\/\/vg07.met.vgwort.de\/na\/94bdbe0382f240faa533a84f1999f05c\" width=\"1\" height=\"1\">I didn't notice anything myself, because I still have exactly this combination running here in the blog. But I found out about the topic through <a href=\"https:\/\/www.facebook.com\/groups\/wpsicherheit\/permalink\/2673565526080603\/\" target=\"_blank\" rel=\"noopener noreferrer\">this German Facebook post<\/a> of Daniel R. <\/p>\n<p><img decoding=\"async\" title=\"WordFence-Post auf Facebook\" alt=\"WordFence-Post auf Facebook\" src=\"https:\/\/i.imgur.com\/Qh4CQ1J.jpg\"><\/p>\n<p>In the linked WordPress article <a href=\"https:\/\/wordpress.org\/support\/topic\/wont-activate-due-to-fatal-error-after-wp-5-4-2-update\/\" target=\"_blank\" rel=\"noopener noreferrer\">won't activate due to fatal error after WP 5.4.2 update<\/a> it says:<\/p>\n<blockquote>\n<p>This website simply produced a white screen and Jetpack monitor registered that the website had gone down around 20 mins after WP was updated to 5.4.2 . I disabled all plugins and after re-enabling one by one worked out it was Wordfence. When trying to reactivate it I get the message \"plugin could not be activated because it triggered a fatal error\". I deleted and reinstalled the plugin but same again. This is a Genesis framework theme. All my other sites (none are Genesis framework) which also all use Wordfence are OK.<\/p>\n<\/blockquote>\n<p>Background is probably that WordFence under WordPress 5.4.2 needs a lot of memory (300 MB), so that it comes to memory bottlenecks. <a href=\"https:\/\/wordpress.org\/support\/topic\/wordfence-is-causing-site-problems\/\" target=\"_blank\" rel=\"noopener noreferrer\">This post<\/a> in the WordPress forum also deals with this issue. <\/p>\n<blockquote>\n<p>Wordfence is causing site problems<\/p>\n<p>Wordfence is causing site problems. So I have tried to investigate the problem further and have come to the following. The problem may be the wordfenece security plugin. Since I have tried switching to other themes, reset wordfence settings to deafult and disabeling all plings except wordfence.  <\/p>\n<p>Anyone who have experienced something similar or know about this problem?<\/p>\n<\/blockquote>\n<p>Some people increase the amount of memory allowed so that the stuff runs again. The longer term solution might be to switch to other security solutions. Do I have to come in here and take a look at this place sometime. <\/p>\n","protected":false},"excerpt":{"rendered":"<p>[German]The update of WordPress to version 5.4.2 may cause problems for some users who use the security plugin WordFence. The plugin cannot be activated or the page remains empty.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,1547],"tags":[166,2479,359],"class_list":["post-14742","post","type-post","status-publish","format-standard","hentry","category-issue","category-software","tag-issues","tag-wordfence","tag-wordpress"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/14742","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=14742"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/14742\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=14742"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=14742"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=14742"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}