Title: gohanman's Replies | WordPress.org --- # gohanman [ ](https://wordpress.org/support/users/gohanman/) * [Profile](https://wordpress.org/support/users/gohanman/) * [Topics Started](https://wordpress.org/support/users/gohanman/topics/) * [Replies Created](https://wordpress.org/support/users/gohanman/replies/) * [Reviews Written](https://wordpress.org/support/users/gohanman/reviews/) * [Topics Replied To](https://wordpress.org/support/users/gohanman/replied-to/) * [Engagements](https://wordpress.org/support/users/gohanman/engagements/) * [Favorites](https://wordpress.org/support/users/gohanman/favorites/) Search replies: ## Forum Replies Created Viewing 6 replies - 1 through 6 (of 6 total) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Wordfence Security - Firewall, Malware Scan, and Login Security] Nonsensical SSL Notification](https://wordpress.org/support/topic/nonsensical-ssl-notification/) * Thread Starter [gohanman](https://wordpress.org/support/users/gohanman/) * (@gohanman) * [8 years, 3 months ago](https://wordpress.org/support/topic/nonsensical-ssl-notification/#post-10231612) * FWIW, I did look at the documentation before posting. What’s distinctly not helpful about the documentation is that it also does not say which version of OpenSSL is supported. Saying “more than 5 years old” is way more ambiguous than listing a minimum version number. Also, OpenSSL 1.0.1 was released a bit over 6 years ago. * Forum: [Hacks](https://wordpress.org/support/forum/plugins-and-hacks/hacks/) In reply to: [How do I debug a fatal error activating a plugin?](https://wordpress.org/support/topic/how-do-i-debug-a-fatal-error-activating-a-plugin/) * Thread Starter [gohanman](https://wordpress.org/support/users/gohanman/) * (@gohanman) * [9 years, 8 months ago](https://wordpress.org/support/topic/how-do-i-debug-a-fatal-error-activating-a-plugin/#post-8475223) * The suggestion has less to do with honesty and more to do with failing in a logged manner. * If the environment is configured with display_errors off using trigger_error would provide even less information with a blank white screen instead of “Go away script kiddies”. But even if display_errors is on the point of the suggestion is to put it at the top of the script to prevent access. There’s nothing on the call stack to leak into display. * Forum: [Hacks](https://wordpress.org/support/forum/plugins-and-hacks/hacks/) In reply to: [How do I debug a fatal error activating a plugin?](https://wordpress.org/support/topic/how-do-i-debug-a-fatal-error-activating-a-plugin/) * Thread Starter [gohanman](https://wordpress.org/support/users/gohanman/) * (@gohanman) * [9 years, 8 months ago](https://wordpress.org/support/topic/how-do-i-debug-a-fatal-error-activating-a-plugin/#post-8475103) * Yeah. The problem actually stemmed from the security advice here: [https://codex.wordpress.org/Writing_a_Plugin#Plugin_Files](https://codex.wordpress.org/Writing_a_Plugin#Plugin_Files) * I wrote * ``` defined( 'ABS_PATH' ) or die( 'No script kiddies please!' ); ``` * instead of * ``` defined( 'ABSPATH' ) or die( 'No script kiddies please!' ); ``` * but die() isn’t really a fatal error. It just prints to STDOUT (which presumably gets eaten by output buffering somewhere) and exits. * Something like this would probably be a better solution. * ``` if (!defined('ABSPATH')) { trigger_error('Invalid call state', E_USER_ERROR); } ``` * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Search Everything] span tag code on admin search results](https://wordpress.org/support/topic/span-tag-code-on-admin-search-results/) * [gohanman](https://wordpress.org/support/users/gohanman/) * (@gohanman) * [10 years, 11 months ago](https://wordpress.org/support/topic/span-tag-code-on-admin-search-results/#post-6337303) * I’m also experiencing this in the latest version / 8.1.3. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Automatic Background Updates Unreliable, Difficult to Debug](https://wordpress.org/support/topic/automatic-background-updates-unreliable-difficult-to-debug/) * Thread Starter [gohanman](https://wordpress.org/support/users/gohanman/) * (@gohanman) * [11 years, 8 months ago](https://wordpress.org/support/topic/automatic-background-updates-unreliable-difficult-to-debug/#post-5580603) * Version control! I never had WordPress itself under VC, but there was an old . svn folder farther up the directory tree (an artifact of hosting multiple domains under the same root directory). It took a bit of digging through the code to figure out what paths it was checking for version control. * From what I saw tracing through this, it looks to me like automatic background updates won’t run under any of the following conditions: a) both cURL and streams are unavailable b) cURL and/or streams do not have SSL support c) WordPress appears to be under version control * IMO it would be helpful to note somewhere which of these checks is failing. I realize this isn’t useful information to all users and showing it prominently would confuse more than it helps, but having the details available somewhere would have been quicker than familiarizing myself with WP’s HTTP abstractions to figure out what was happening. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Black Studio TinyMCE Widget] Stopped Loading in some fields after 3.9](https://wordpress.org/support/topic/stopped-loading-in-some-fields-after-39/) * Thread Starter [gohanman](https://wordpress.org/support/users/gohanman/) * (@gohanman) * [12 years, 3 months ago](https://wordpress.org/support/topic/stopped-loading-in-some-fields-after-39/#post-4825916) * It’s entirely possible I’m in the wrong spot. I thought the plugin was responsible for adding a WYSIWYG editor. I may have mixed it up since both are labeled “TinyMCE”. Sorry about the mix up. * The TM Lunch Menu plugin did have WYSWYG fields prior to WP 3.9. But if your plugin has nothing to do with general WP’s general WYSWYG editor, this really isn’t the right place for debugging. Viewing 6 replies - 1 through 6 (of 6 total)