Title: webifiedOne's Replies | WordPress.org --- # webifiedOne [ ](https://wordpress.org/support/users/webifiedone/) * [Profile](https://wordpress.org/support/users/webifiedone/) * [Topics Started](https://wordpress.org/support/users/webifiedone/topics/) * [Replies Created](https://wordpress.org/support/users/webifiedone/replies/) * [Reviews Written](https://wordpress.org/support/users/webifiedone/reviews/) * [Topics Replied To](https://wordpress.org/support/users/webifiedone/replied-to/) * [Engagements](https://wordpress.org/support/users/webifiedone/engagements/) * [Favorites](https://wordpress.org/support/users/webifiedone/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 30 total) 1 [2](https://wordpress.org/support/users/webifiedone/replies/page/2/?output_format=md) [→](https://wordpress.org/support/users/webifiedone/replies/page/2/?output_format=md) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[The Events Calendar] Is it safe yet to accept the 6.1.1 plugin update?](https://wordpress.org/support/topic/is-it-safe-yet-to-accept-the-6-1-1-plugin-update/) * Thread Starter [webifiedOne](https://wordpress.org/support/users/webifiedone/) * (@webifiedone) * [2 years, 11 months ago](https://wordpress.org/support/topic/is-it-safe-yet-to-accept-the-6-1-1-plugin-update/page/2/#post-16840285) * No, this is not resolved. Just fix the plugin so that it works in all supported environments. (If it fails in unsupported platforms/environments, that’s OK. But, disclose what you do not support. - This reply was modified 2 years, 11 months ago by [webifiedOne](https://wordpress.org/support/users/webifiedone/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[The Events Calendar] Is it safe yet to accept the 6.1.1 plugin update?](https://wordpress.org/support/topic/is-it-safe-yet-to-accept-the-6-1-1-plugin-update/) * Thread Starter [webifiedOne](https://wordpress.org/support/users/webifiedone/) * (@webifiedone) * [2 years, 11 months ago](https://wordpress.org/support/topic/is-it-safe-yet-to-accept-the-6-1-1-plugin-update/#post-16838716) * Nothing to say. Just speechless over the lack of a solution. - This reply was modified 2 years, 11 months ago by [webifiedOne](https://wordpress.org/support/users/webifiedone/). - This reply was modified 2 years, 11 months ago by [webifiedOne](https://wordpress.org/support/users/webifiedone/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[The Events Calendar] Is it safe yet to accept the 6.1.1 plugin update?](https://wordpress.org/support/topic/is-it-safe-yet-to-accept-the-6-1-1-plugin-update/) * Thread Starter [webifiedOne](https://wordpress.org/support/users/webifiedone/) * (@webifiedone) * [2 years, 11 months ago](https://wordpress.org/support/topic/is-it-safe-yet-to-accept-the-6-1-1-plugin-update/#post-16838711) * Otherwise, I think you have a rebellion on your hands. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[The Events Calendar] Is it safe yet to accept the 6.1.1 plugin update?](https://wordpress.org/support/topic/is-it-safe-yet-to-accept-the-6-1-1-plugin-update/) * Thread Starter [webifiedOne](https://wordpress.org/support/users/webifiedone/) * (@webifiedone) * [2 years, 11 months ago](https://wordpress.org/support/topic/is-it-safe-yet-to-accept-the-6-1-1-plugin-update/#post-16838710) * Then, prove that you have fixed it. * Win the trust of all those subscribers. Win it. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[The Events Calendar] Is it safe yet to accept the 6.1.1 plugin update?](https://wordpress.org/support/topic/is-it-safe-yet-to-accept-the-6-1-1-plugin-update/) * Thread Starter [webifiedOne](https://wordpress.org/support/users/webifiedone/) * (@webifiedone) * [2 years, 11 months ago](https://wordpress.org/support/topic/is-it-safe-yet-to-accept-the-6-1-1-plugin-update/#post-16838707) * The best thing to prove your point is to fix your defective plugin update. * Can you do that? * Prove it. Fix it. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[The Events Calendar] Is it safe yet to accept the 6.1.1 plugin update?](https://wordpress.org/support/topic/is-it-safe-yet-to-accept-the-6-1-1-plugin-update/) * Thread Starter [webifiedOne](https://wordpress.org/support/users/webifiedone/) * (@webifiedone) * [2 years, 11 months ago](https://wordpress.org/support/topic/is-it-safe-yet-to-accept-the-6-1-1-plugin-update/#post-16838703) * No. Nothing to keep in mind. You are not following industry standard IT best practices. * Something has gone awry since we first signed up with you. * But, things have taken a turn for the worse. * The industry no longer agrees with your practices, so we are going to choose to drop you. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[The Events Calendar] Is it safe yet to accept the 6.1.1 plugin update?](https://wordpress.org/support/topic/is-it-safe-yet-to-accept-the-6-1-1-plugin-update/) * Thread Starter [webifiedOne](https://wordpress.org/support/users/webifiedone/) * (@webifiedone) * [2 years, 11 months ago](https://wordpress.org/support/topic/is-it-safe-yet-to-accept-the-6-1-1-plugin-update/#post-16838602) * Thank you for your reply. It seems most serious and considerate. But, it does seem some industry standard testing methodologies that used to be employed might have gone wayside: ITIL V4, for example. AGIL methods? Are you using them? Regression analysis and testing? Github? (I can only hope.) * If there are “too many themes and plugins to keep up with,” then maybe you’re not keeping up. * Again, you should limit your scope of support — but make it clear what you support, to your end-users. Update your automated-testing to weed out unsupported devices and browsers, and to throw out an automated notice that can be used to inform end-users! * For example, in my line of IT dev work, we had to stop support on older versions of Apple software and completely stop support of Internet Explorer browsers. This was several years ago. We were able to send a mass email to the entire enterprise( several tens of thousands of users) to update, or change, or go unspported. * But, it remains a stark example. * Your plugin update notices might need to include a notice of what still breaks, and why it breaks, and why it is NOT supported, or NO LONGER supported. Etc. That kind of thing. * But, without such notices, the unexpected happens — everyone, everywhere just expects your plugins to magically work everywhere. That’s unrealistic. - This reply was modified 2 years, 11 months ago by [webifiedOne](https://wordpress.org/support/users/webifiedone/). - This reply was modified 2 years, 11 months ago by [webifiedOne](https://wordpress.org/support/users/webifiedone/). - This reply was modified 2 years, 11 months ago by [webifiedOne](https://wordpress.org/support/users/webifiedone/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[The Events Calendar] Is it safe yet to accept the 6.1.1 plugin update?](https://wordpress.org/support/topic/is-it-safe-yet-to-accept-the-6-1-1-plugin-update/) * Thread Starter [webifiedOne](https://wordpress.org/support/users/webifiedone/) * (@webifiedone) * [2 years, 11 months ago](https://wordpress.org/support/topic/is-it-safe-yet-to-accept-the-6-1-1-plugin-update/#post-16838462) * Well, fortunately, for us — we have learned our lesson the hard way and have not even attempted to try any updates, or tests, at all. Rather, we also are relying on the reported stack traces, tests, and end-user reports to determine when the “dust has settled” on this update. * Once we see reports that no more fatal errors exist, we’ll begin our own testing regimen to confirm no more errors exist. And, we also have the paid version, by the way, and utilize that for extended support once we actually begin our own testing routines, using ITIL framework to ensure all parties are involved in the testing. * But, we start here, in the public domain to see what the larger population is experiencing first. * Unfortunately, this is not the first time this has happened with Events Calendar updates, and so we have let our IT team know to view all future plugin updates with a wary eye — watch the support forums first, then test in a staging/test environment. * But, lately, in the last 18 months, there have been at least two updates that have completely crashed websites — I mean literally wiped out the home page. So, we’re not taking any chances. * I do have to say, this has been the most problematic plugin we use, when it comes to updates. * _** I strongly recommend improved testing methodologies that are based on knowledge of your overall audience.**_ - This reply was modified 2 years, 11 months ago by [webifiedOne](https://wordpress.org/support/users/webifiedone/). - This reply was modified 2 years, 11 months ago by [webifiedOne](https://wordpress.org/support/users/webifiedone/). - This reply was modified 2 years, 11 months ago by [webifiedOne](https://wordpress.org/support/users/webifiedone/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[The Events Calendar] FATAL error -STILL- exists in 6.1.1](https://wordpress.org/support/topic/fatal-error-still-exists-in-6-1-1/) * [webifiedOne](https://wordpress.org/support/users/webifiedone/) * (@webifiedone) * [2 years, 12 months ago](https://wordpress.org/support/topic/fatal-error-still-exists-in-6-1-1/page/2/#post-16826814) * I totally concur with [@tvalleau](https://wordpress.org/support/users/tvalleau/). This is ridiculous on Events Calendar development team’s part: Why “brag” about a new rollout with Version 6.1.1., if it still contains errors that already were reported in at least two previous releases in the same week? * I have asked my website team to consider cancelling our PRO subscription and completely removing The Events Calendar from the website. * Totally crazy that these guys seem not to be testing thoroughly enough before new updates. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Woody Code Snippets – Insert PHP, CSS, JS, and Header/Footer Scripts] Fatal Error due to conflict with the Events Calendar plugin](https://wordpress.org/support/topic/fatal-error-due-to-conflict-with-the-events-calendar-plugin/) * [webifiedOne](https://wordpress.org/support/users/webifiedone/) * (@webifiedone) * [6 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-due-to-conflict-with-the-events-calendar-plugin/#post-12381128) * Thank you, Artem. I passed that link and information to the support engineer. I am hopeful they are already working on this, or will now be able to better coordinate. * Thank you for posting to Github,as well. I think the Events Calendar developers will definitely take notice if it is on Github. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Woody Code Snippets – Insert PHP, CSS, JS, and Header/Footer Scripts] Fatal Error due to conflict with the Events Calendar plugin](https://wordpress.org/support/topic/fatal-error-due-to-conflict-with-the-events-calendar-plugin/) * [webifiedOne](https://wordpress.org/support/users/webifiedone/) * (@webifiedone) * [6 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-due-to-conflict-with-the-events-calendar-plugin/#post-12378312) * Hi, Artem: * We, too, are having the same conflict issue with Events Calendar Pro. We have an open support ticket with Modern Tribe (Events Calendar authors), and they say they have not received anything from you regarding this conflict. Could you please let me know who at Modern Tribe you have reached out to? I will pass the contact information on to the support engineer that I am working with. The engineer is anxious to get this logged as a bug report, so they can fix it. * Thanks! * Ben navajotimes.com * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[All-In-One Security (AIOS) – Security and Firewall] Root permissions at 1705 every morning](https://wordpress.org/support/topic/root-permissions-at-1705-every-morning/) * Thread Starter [webifiedOne](https://wordpress.org/support/users/webifiedone/) * (@webifiedone) * [6 years, 9 months ago](https://wordpress.org/support/topic/root-permissions-at-1705-every-morning/#post-11936807) * Here you go: * Plugin Version : 4.4.0 WP Version : 5.2.3 WPMU: No MySQL Version : 5.7.27 WP Table Prefix : xxxxx (obscured for security) PHP Version : 7.2.22 Session Save Path : /tmp/.priv WP URL: [https://navajotimes.com](https://navajotimes.com) Server Name : navajotimes.com Cookie Domain : navajotimes.com CURL Library Present: Yes Debug File Write Permissions : Writable * PHP Version : 7.2.22 PHP Memory Usage: 71.17 MB PHP Memory Limit : -1 PHP Max Upload Size : 64M PHP Max Post Size : 64M PHP Allow URL fopen : On PHP Allow URL Include : Off PHP Display Errors : On PHP Max Script Execution Time : 50000 Seconds * Host is IONOS.com - This reply was modified 6 years, 9 months ago by [webifiedOne](https://wordpress.org/support/users/webifiedone/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[All-In-One Security (AIOS) – Security and Firewall] Root permissions at 1705 every morning](https://wordpress.org/support/topic/root-permissions-at-1705-every-morning/) * Thread Starter [webifiedOne](https://wordpress.org/support/users/webifiedone/) * (@webifiedone) * [6 years, 9 months ago](https://wordpress.org/support/topic/root-permissions-at-1705-every-morning/#post-11934983) * Yes, thanks for that tip. * But, we tried that about a year ago on two different websites. * So long as your plugin was either not present, or was inactive, the permissions stayed the same. * Also, when we contacted the web hosting company, they concluded that it was your plugin that was causing the permissions to change.They said they have nothing on their side of operations that would cause such a change every single day. * Unfortunately, we have lived with the daily, every morning, routine of resetting the permissions in order to enjoy the benefits of the rest of the plugin. But, it is getting tedious and time consuming at this point. - This reply was modified 6 years, 9 months ago by [webifiedOne](https://wordpress.org/support/users/webifiedone/). - This reply was modified 6 years, 9 months ago by [webifiedOne](https://wordpress.org/support/users/webifiedone/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Wordfence Security - Firewall, Malware Scan, and Login Security] Wordfence is bloating the size of my WP database. Table: wp_wfConfig](https://wordpress.org/support/topic/wordfence-is-bloating-the-size-of-my-wp-database-table-wp_wfconfig/) * [webifiedOne](https://wordpress.org/support/users/webifiedone/) * (@webifiedone) * [6 years, 11 months ago](https://wordpress.org/support/topic/wordfence-is-bloating-the-size-of-my-wp-database-table-wp_wfconfig/#post-11740716) * Unfortunately, after updating Wordfence yesterday to the latest version, this problem hit me hard. My database doubled in size right after the update. * For now, I have done as the Plugin Support guys have instructed, and have left Wordfence deactivated. * Please let us know if there is a better solution, or a fix for this. Once that comes about, I’ll reinstall Wordfence. - This reply was modified 6 years, 11 months ago by [webifiedOne](https://wordpress.org/support/users/webifiedone/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[PHP Code Widget] PHP code to right sidebar](https://wordpress.org/support/topic/php-code-to-right-sidebar/) * [webifiedOne](https://wordpress.org/support/users/webifiedone/) * (@webifiedone) * [6 years, 11 months ago](https://wordpress.org/support/topic/php-code-to-right-sidebar/#post-11676648) * Hi, * This has been a great plugin, but today I received a security alert from Wordfence that this plugin has not been updated or tested in quite a while, and may pose a security risk as a result of being “abandoned.” * It appears the plugin is still being supported through the latest version of WordPress. Can you tell us whether we can ignore the Wordfence alert? Or, is there a suitable alternative to this plugin, if it no longer is supported? * Thanks! - This reply was modified 6 years, 11 months ago by [webifiedOne](https://wordpress.org/support/users/webifiedone/). Viewing 15 replies - 1 through 15 (of 30 total) 1 [2](https://wordpress.org/support/users/webifiedone/replies/page/2/?output_format=md) [→](https://wordpress.org/support/users/webifiedone/replies/page/2/?output_format=md)