Title: EarShell's Replies | WordPress.org --- # EarShell [ ](https://wordpress.org/support/users/earshell/) * [Profile](https://wordpress.org/support/users/earshell/) * [Topics Started](https://wordpress.org/support/users/earshell/topics/) * [Replies Created](https://wordpress.org/support/users/earshell/replies/) * [Reviews Written](https://wordpress.org/support/users/earshell/reviews/) * [Topics Replied To](https://wordpress.org/support/users/earshell/replied-to/) * [Engagements](https://wordpress.org/support/users/earshell/engagements/) * [Favorites](https://wordpress.org/support/users/earshell/favorites/) Search replies: ## Forum Replies Created Viewing 7 replies - 1 through 7 (of 7 total) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Printful Integration for WooCommerce] Changelog](https://wordpress.org/support/topic/changelog-214/) * [EarShell](https://wordpress.org/support/users/earshell/) * (@earshell) * [1 year, 9 months ago](https://wordpress.org/support/topic/changelog-214/#post-17950630) * It seems odd to me that the only option to view the changelog is to locate it buried in the source code, and not see it readily displayed here in the Development tab (as is standard practice with other plugins). * I will also say that, looking at the changelog, some of it is meaningless to me as a drag-and-drop developer, and not someone who does much coding. For example, I do not know what “QIT changes” are (it would be helpful if the acronym “QIT” was defined at least once in the changelog, but it isn’t). * Further back in the changelog, it says “Fixed – Security issues” a couple of times. While fixing security issues is good, I think the changelog should provide more detail about what, exactly, was fixed. For example, the WooCommerce changelog includes a sentence describing each security fix, which is often accompanied by links to pages with further info. * That aside, the main takeaway from the changelog for me is that the plugin has not been tested with WordPress 6.6.1 (it only says “Updated – WordPress compatibility to 6.5.4”). As for WooCommerce, the Printful changelog says “compatibility to 8.9.3”. So, are there any problems with running the Printful plugin in conjunction with WooCommerce 9.1.4 (latest version)? * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Printful Integration for WooCommerce] Changelog](https://wordpress.org/support/topic/changelog-214/) * [EarShell](https://wordpress.org/support/users/earshell/) * (@earshell) * [1 year, 10 months ago](https://wordpress.org/support/topic/changelog-214/#post-17903134) * Yes, where is the changelog? If I am not mistaken, there used to be one, but now it is gone. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LoftLoader] It stopped working](https://wordpress.org/support/topic/it-stopped-working-16/) * [EarShell](https://wordpress.org/support/users/earshell/) * (@earshell) * [5 years, 6 months ago](https://wordpress.org/support/topic/it-stopped-working-16/#post-13670561) * I am seeing the same problem. Today I updated LoftLoader from 2.3.2 to 2.3.3.. After doing so, it stopped working. I tried to troubleshoot this by disabling and then reenabling the plugin, but that did not help. FYI, I am running Divi 4.6.6 on WP 5.5.3. Thought you should know. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Wordfence Security - Firewall, Malware Scan, and Login Security] Quick Page/Post Redirect Plugin](https://wordpress.org/support/topic/quick-pagepost-redirect-plugin-2/) * [EarShell](https://wordpress.org/support/users/earshell/) * (@earshell) * [10 years, 1 month ago](https://wordpress.org/support/topic/quick-pagepost-redirect-plugin-2/#post-7306473) * Today I received the same message from WordFence regarding the same plugin file noted by Atmara. * I have the same question as Atmara, which is that if WordFence had no concern with the file before, why is it being flagged now? * Your insight on this would be appreciated, WordFence. * Thanks! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Quick Page/Post Redirect Plugin] Problem with qppr_frontend_script.min.js file?](https://wordpress.org/support/topic/problem-with-qppr_frontend_scriptminjs-file/) * [EarShell](https://wordpress.org/support/users/earshell/) * (@earshell) * [10 years, 1 month ago](https://wordpress.org/support/topic/problem-with-qppr_frontend_scriptminjs-file/#post-7305993) * I received the same message from WordFence today as well. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Wordfence Security - Firewall, Malware Scan, and Login Security] Completely Unacceptable](https://wordpress.org/support/topic/completely-unacceptable/) * [EarShell](https://wordpress.org/support/users/earshell/) * (@earshell) * [10 years, 7 months ago](https://wordpress.org/support/topic/completely-unacceptable/#post-6628201) * I am not convinced that we are done with this issue. * To the best of my knowledge, the setting “Block access to the rest of the site( outside the login form)” is OFF by default. However, Wordfence suddenly turned it ON in my sites — an enormous problem. * If I am correct in saying that this setting is OFF by default (it would be bizarre to have it ON by default), then this is an entirely different bug. * Furthermore, Wordfence: Please, when important issues arise such as this, do not simply make an announcement on Facebook and Twitter. Your users (and especially paying subscribers) deserve the courtesy of an email. * At the risk of repeating what I said in another post, I believe I speak for many users when I say that there is a good chance that we are not “following” you on social media. We use security software so that we can “set it and forget it”. If there is an issue that you should be disclosing (especially one such as this), get a message directly to our in-boxes, so that we can take action and fix our sites. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Wordfence Security - Firewall, Malware Scan, and Login Security] Latest Update: Turning on settings that were uncheked](https://wordpress.org/support/topic/latest-update-turning-on-settings-that-were-uncheked/) * [EarShell](https://wordpress.org/support/users/earshell/) * (@earshell) * [10 years, 7 months ago](https://wordpress.org/support/topic/latest-update-turning-on-settings-that-were-uncheked/#post-6631425) * I have been corresponding with Wordfence today via email, and they stated the following: * “We released a fix that addressed a bug introduced with version 6.0.19. The issue was that if a Wordfence option checkbox is unchecked and was different from the default setting, the release resets the Wordfence setting to the default setting of checked.” * Unfortunately, even though I am a paying subscriber, I did not receive an email alert about this issue. I find this to be strange, as Wordfence has sent emails regarding its latest blog posts, and even a cheerful press-release-style note about its new logo. But, when an important bug such as this should have been announced there was nothing in my inbox. * The Wordfence support person indicated to me that an announcement had been made on Twitter and Facebook. But’s let’s be realistic here: Many of Wordfence’s users will not be “following” the company on social media. People do not follow many of the products that they use. Further to that idea, Wordfence is a product that is supposed to provide peace of mind. With security software, users want to “ set it and forget it” rather than to pay attention to it on Twitter. * It is a huge disappointment to me that a security product would relegate a critical bug announcement to a social-media-only audience. I am certain that I am not the only one that, as a paying subscriber, expects the simple courtesy of an email. Viewing 7 replies - 1 through 7 (of 7 total)