Support » Plugin: Wordbooker » Disable Logging Completely

  • Hey Steve,

    I have hopefully a simple request for you: could you (pretty please) provide a way to completely disable WP’s error logging (i.e. not just hide it from the admin panel, but prevent it from logging to the wp_wordbooker_errorlogs table at all)? I took a look at the code and I believe the function in question is wordbooker_debugger(), but there’s kindof a lot going on there so I was hesitant to just put a “return;” at the start of it – plus modifying the plugin obviously isn’t ideal since it’d get overwritten with each update.

    The reason is because I revision-control all my database backups, and an enormous percentage of the overall diffs come from just this one table – since it contains quite a few entries which change all the time. Obviously I see the merit to logging in general, but when I’m not trying to debug an issue it would save a tremendous amount of space in my repository if I could avoid all these changes getting committed each time. Manually going into the panel to click “Clear Diagnostics Message” before every backup is cumbersome, and calling wordbooker_clear_diagnosticlogs() i.e. on every page load (to make sure they’re always empty) would be very inefficient – it would be great if we could just prevent it from error_logging in the first place (and just enable them when actually needed).

    Much appreciated… 🙂
    J~

    http://wordpress.org/plugins/wordbooker/

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author Steve

    (@steveatty)

    You can put a return in immediately after the start of the procedure. I’ll add an option into the advanced settings to allow logging to be totally turned off.

    Thread Starter justin_k

    (@justin_k)

    Great! Thanks much 🙂

    Plugin Author Steve

    (@steveatty)

    Are you on 2.1.x or running 2.2? I’ve put the option (its in the logging level drop down) in both but I’m waiting for a couple of people to get back to me on a couple of other changes I’ve made before I push a new version of 2.1 to the repositories.

    Thread Starter justin_k

    (@justin_k)

    According to WordPress.org (and my sites’ update checkers), the highest available version is 2.1.38…

    Plugin Author Steve

    (@steveatty)

    OK – 2.2 is still in Beta – adds a lot of things like Category and Post Type filtering and support for Curl or WP_HTTP posting (for those who can’t use Curl).

    Thread Starter justin_k

    (@justin_k)

    Gotcha

    Plugin Author Steve

    (@steveatty)

    Oh and its the version that allows “Premium” use – which at the moment just means you can use your own FB AppID and not use Wordbooker’s servers to handle authorisation.. but I’m going to be adding Photo upload as a totally premium feature to it.

    Thread Starter justin_k

    (@justin_k)

    After updating from 2.1.36 to 2.1.39 (in order to get the ‘disable logging’ option), the “Disable Facebook API initialisation” option no longer works properly. Whether that’s checked or unchecked, it’s always initializing the API (and thus conflicting w/ other FB plugins).

    Plugin Author Steve

    (@steveatty)

    You’re right… I got it all working and then moved one of the if statements… and put it before I got the variable….

    Basically this code in the wordbooker_footer function:

    if (!isset($wordbooker_settings['wordbooker_fb_disable_api'])) {
    	$wplang=wordbooker_get_language();
    	$wordbooker_settings = wordbooker_options();

    Should look like this:

    $wordbooker_settings = wordbooker_options();
    	if (!isset($wordbooker_settings['wordbooker_fb_disable_api'])) {
    	$wplang=wordbooker_get_language();

    I’ll get that rolled into a new release.

    Thread Starter justin_k

    (@justin_k)

    Coo, I’ll just hang tight for that to test everything at once~

    Plugin Author Steve

    (@steveatty)

    OK I’ve just pushed the code to WordPress… serves me right for playing round with things that didn’t really need fixing 😉

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Disable Logging Completely’ is closed to new replies.