This is searchable archive of our old support forums, which operated from 2012 - 2016. To find out how to get support for your current theme, please visit our support page.

Tagged: 

Error trying to remove theme debug info, Jump Start 2.0 RC1

  • Creator
    Topic
  • #21574
    cfunkyk
    Participant

    Thanks for all your hard work Jason!

    Just an FYI or question on this: The function you provide to remove the theme debug info in actually causes an error with woocommerce causing all woo admin pages to be white (blank). Also my server logs show that the error is in that function in my functions file.

    Please let me know what I am doing wrong.

    Thanks!

    Notes:
    Added theme debug info to output in of site, see here.
    http://dev.themeblvd.com/tutorial/remove-debug-info/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Author
    Replies
  • #21576
    Jason Bobich
    Keymaster

    Hello,

    Are you able to tell me specifically what error you’re getting?

    Conceptually, I’m just trying to think of how that code provided would have anything at all to do with WooCommerce or your wp admin.

    #21627
    cfunkyk
    Participant

    Fatal error: Class ‘Theme_Blvd_Frontend_Init’ not found in /nas/wp/www/staging/blahblah/wp-content/themes/blahblah-child/functions.php on line 18

    This shows up when I have the function in my functions file and I click on any of the WooCommerce tabs in wp-admin.
    Line 18 is the line starting with $init =

    /wp-admin/edit.php?post_type=shop_order
    /wp-admin/edit.php?post_type=product
    ^^these are urls that the error appears on with white screen. Well, it also appears in server logs too.

    Thanks for your help with this matter!

    #21629
    Jason Bobich
    Keymaster

    Aw, well that’s easy to fix. See updated code snippet in the article.

    https://gist.github.com/themeblvd/bc435c5052dd313d8c03

    … Does that work for you?

    #21634
    cfunkyk
    Participant

    Thanks Jason!
    I can confirm that it does not cause the error with Woo, and it looks like the debug information is not showing in

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.