BugWP logo BugWP
Back to Community
Home / Community / Plugin → Code snippets

Troubleshooting Common Code Snippets Errors in WooCommerce

34 threads Sep 10, 2025 Plugin → Code snippets

Content

Why Do These Errors Happen?

The 'Code Snippets' plugin executes custom PHP code you add to your site. When an error occurs, it's almost always due to an issue within the specific snippet's code, not the plugin itself. The error is simply reported from the file where the code is executed (snippet-ops.php). Common triggers include:

  • PHP Version Upgrades: Code that worked in PHP 7.4 may use deprecated functions or syntax that causes warnings or fatal errors in PHP 8.2+.
  • WooCommerce Updates: Snippets that interact with WooCommerce may break after an update if they rely on functions, methods, or properties that have been changed or deprecated.
  • Logical Errors in Code: This includes trying to use a variable before it's defined, calling a method on a null value, or attempting to access an array element that doesn't exist.
  • Function Name Conflicts: Declaring a function with the same name as one already existing in your theme or another plugin.

How to Identify the Problematic Snippet

The first and most crucial step is to find which snippet is causing the issue. The error message itself often provides the best clue.

  1. Check the Error Log: Your server's PHP error log or WordPress debug log is the primary source of truth. Look for lines that reference .../code-snippets/php/snippet-ops.php(...) : eval()'d code.
    • Line Number: The error will include a line number (e.g., on line 39). This refers to a line within your snippet's code.
    • Error Text: The error description (e.g., Call to a member function get_attribute() on null) tells you what went wrong.
  2. Use Safe Mode: The 'Code Snippets' plugin includes a Safe Mode feature. Activating it will temporarily deactivate all snippets, allowing you to confirm that the error disappears. You can then reactivate your snippets one by one until the error returns, pinpointing the culprit.
  3. Search Your Snippets: Use the search function in the Snippets admin page. Search for unique variable names, function names, or WooCommerce hooks mentioned in the error.

Common Errors and Their Solutions

1. "Call to a member function ... on null" or "on bool"

What it means: Your code is trying to run a method (e.g., ->get_attribute()) on a variable that is not an object; it's null or false.

How to fix it: You must check if the variable is a valid object before using it.

// Incorrect - could cause an error if $product is null
return $product->get_description();

// Correct - safe check before using the method
if ( is_a( $product, 'WC_Product' ) ) {
    return $product->get_description();
} else {
    return ''; // Or handle the error appropriately
}

2. "Cannot redeclare function..."

What it means: You have two snippets (or a snippet and your theme) trying to declare a function with the exact same name.

How to fix it: Give your function a unique name. Using a prefix is a best practice.

// Change this generic function name...
function custom_override_checkout_fields($fields) { ... }

// ...to something unique
function myprefix_custom_override_checkout_fields($fields) { ... }

3. "Undefined variable" Warning

What it means: Your code is using a variable that has not been assigned a value first.

How to fix it: Initialize the variable with a default value before the conditional logic that might set it.

// Incorrect - $increaseby_sam may not be defined
if ( $chosen_payment_method == 'samipg' ) {
    $increaseby_sam = 3;
}
$new_price = $price * $increaseby_sam; // Error if condition wasn't met

// Correct - define a default value first
$increaseby_sam = 0; // Default value
if ( $chosen_payment_method == 'samipg' ) {
    $increaseby_sam = 3;
}
$new_price = $price * $increaseby_sam; // Always works

4. PHP 8.2+ Deprecation and Property Warnings

What it means: PHP 8.2 is stricter. A common issue is trying to read a property (like ->slug) on a value that is not an object.

How to fix it: Check that the item in a loop is an object before accessing its properties.

// Before PHP 8.2, this might have worked silently
foreach ( $terms as $term ) {
    if ( ! in_array( $term->slug, [ 'category-a' ] ) ) { ... }
}

// For PHP 8.2+, add a check
foreach ( $terms as $term ) {
    if ( is_object( $term ) && ! in_array( $term->slug, [ 'category-a' ] ) ) { ... }
}

5. WooCommerce Deprecated Function Warnings

What it means: Your snippet uses a WooCommerce function or property that has been replaced by a newer method.

How to fix it: Update your code to use the modern equivalent. The error message often tells you what to use instead.

// Deprecated (causes warning)
$cart->tax_display_cart;

// Modern solution
$cart->get_tax_price_display_mode();

Best Practices for Managing Snippets

  • Test in a Staging Environment: Always test new snippets or updates on a staging site before applying them to your live site.
  • Add Error Handling: Use try/catch blocks or conditional checks (if ( is_a( $var, 'Class' ) )) to make your snippets more robust and prevent fatal errors.
  • Comment Your Code: Leave notes on what each snippet does. This will help you or another developer identify and fix it later.
  • Keep Snippets Updated: Periodically review your snippets, especially after core WordPress, WooCommerce, or PHP updates, to ensure they are still compatible.

By following this guide, you can systematically diagnose and resolve most errors that originate from code snippets on your WooCommerce site. Remember, the 'Code Snippets' plugin is a tool for executing your custom code—the key to stability lies in writing and maintaining that code properly.

Related Support Threads Support