1,528 reputation
420
bio website about.me/adam.bosco
location San Luis Obispo, CA
age 24
visits member for 2 years, 3 months
seen 2 days ago

Level 6 Dire Code Monkey


Apr
15
revised Prevent wp_debug from polluting ajax within plugin
deleted 62 characters in body
Apr
15
comment Prevent wp_debug from polluting ajax within plugin
Let us continue this discussion in chat.
Apr
15
revised Prevent wp_debug from polluting ajax within plugin
deleted 62 characters in body
Apr
15
comment Prevent wp_debug from polluting ajax within plugin
The only true solution is to solve the problems creating unexpected output (thus the cry that there's no reason to use ob_clean()), but still altering output buffers can be useful - I added a preface to my answer to that effect. I certainly use similar tricks to ensure that visitors aren't effected by unforeseeable errors and output. There's one other piece of information that will help eliminate possibilities, here - I'm interested in the results of print_r( ob_get_status( true ) ); This should give us an idea of your buffer environment.
Apr
15
revised Prevent wp_debug from polluting ajax within plugin
added 1876 characters in body
Apr
15
comment Prevent wp_debug from polluting ajax within plugin
Oops - yes you're right, that is the proper way to call esc_like()! I think you're saying that the unexpected output still suggests that ob_clean() is still getting called and returning an error? That's quite interesting, I know of a few situations where this might occur, but I didn't think we'd encounter them here. The Codex certainly needs some attention. Let's troubleshoot this - change if( ob_get_contents() ) to if( 0 < ob_get_level() && 0 < ob_get_contents() ), and then, if you could, add the full unexpected output to the bottom of your question.
Apr
14
revised Prevent wp_debug from polluting ajax within plugin
added 98 characters in body
Apr
14
comment Prevent wp_debug from polluting ajax within plugin
That deprecation notice is misleading - look again, you use the deprecated like_escape() function in your code ;) . Replace it with wpdb::esc_like(). This deprecation notice is also likely responsible for the headers already sent error you were receiving when your call to header() was properly located near the bottom of your script!
Apr
14
revised Prevent wp_debug from polluting ajax within plugin
added 911 characters in body
Apr
14
answered Prevent wp_debug from polluting ajax within plugin
Apr
14
comment Gravity Forms and GravityView query string URL with multiple parameters
Welcome to the WordPress Development community! "I'm sorry, Dave, I'm afraid I can't let you do that." Questions regarding 3rd-party plugins are considered off-topic for our site as they require very specific knowledge and experience to address, and tend to go unanswered as a result. Such questions are best and most swiftly served through the 3rd-party's official support channels. Please review the How to Ask section of our help center to learn more about which questions are a good fit for our community.
Apr
14
comment How to work around the bug which prevents custom menus from being deleted?
WP 403s are most frequently indicative of server misconfiguration; I'd recommend skimming your server's error and access logs to try and track down the source. Are you able to add new menus and add and remove menu items? A possible work-around would be to manually remove the menu from the database, but it would be better to rectify the source of the symptom as it may be causing other issues, as well.
Apr
14
revised WP Job Manger change jobs url (NOT slug)
added 2058 characters in body
Apr
14
revised WP Job Manger change jobs url (NOT slug)
added 2058 characters in body
Apr
14
revised WP Job Manger change jobs url (NOT slug)
added 145 characters in body
Apr
14
answered WP Job Manger change jobs url (NOT slug)
Apr
14
comment WP Job Manger change jobs url (NOT slug)
Please note that questions regarding 3rd-party plugins are considered off-topic within our community. The best place to receive support for such items is the 3rd-party's official support channels. Please review the How to Ask section of our help center to learn more about what questions are on-topic and a good fit at WPD. The question may be brought on-topic by asking it in a more generic, plugin-independent manner. Regardless, I believe I have provided a solution below.
Apr
14
comment Using the 'draft_to_publish' hook (post status transition)
Nice catch, @Eray! Updated with the proper parameter order and to use the same variables as the Codex.
Apr
14
revised Using the 'draft_to_publish' hook (post status transition)
Corrected parameter order; added Codex link; updated conventions
Feb
23
revised debugging js scripts
added 804 characters in body