linux4me2

Hi @spiderman7894

That’s great! Good work!

You can comment out all the error_log() lines so the snippet doesn’t fill up your error logs with unnecessary messages once you have it working to your satisfaction instead of deleting those lines so you have them there in case there are issues you need to troubleshoot going forward.

Mark this thread resolved once you’re happy with the results.

Hi @spiderman7894, sure, I’ll try to help you figure out what’s wrong. Here’s were the error_log comes into play. This may seem complicated, but once you see how it works, it’s pretty straightforward, and makes figuring these things out much easier.

It looks like you have the filename in the order meta, so the first step is to identify where your error_log is, and if it is being written to due to a problem with the snippet. There are a couple of places where the snippet in your functions.php may write to the error_log. It may be in /home/<username>/public_html/wp-admin, since you’re (hopefully) triggering the snippet when you mark the order “completed” in Admin, or it may be in the site root; e.g., /home/<username>/public_html. I guess it could potentially be in the same folder where your functions.php is, but I haven’t seen that happen with errors in functions.php.

I would take a look and see if you have any error_log files in these locations, and if so, see if there are any errors thrown in functions.php for the snippet.

Normally, when troubleshooting something like this, I would do one step at a time, but in this case, I’ll give you a modified snippet designed to write the results at all the points of potential failure:

add_filter('woocommerce_email_attachments', 'webroom_attach_to_wc_emails', 10, 3);
function webroom_attach_to_wc_emails($attachments, $email_id, $order) 
{

    error_log('The webroom_attach_to_wc_emails function was triggered on line '. __LINE__ . ' of ' . __FILE__);

    // Avoiding errors and problems
    if (! is_a($order, 'WC_Order') || ! isset($email_id)) {
        error_log('Either the order is not an order, or email_id is not set on line ' . __LINE__ . ' of ' . __FILE__);
        return $attachments;
    }
    
    error_log('Email ID is ' . $email_id . ' on line ' . __LINE__ . ' of ' . __FILE__);
    
    // Attach the file only to the customer completed order email.
    if ($email_id == 'customer_completed_order') {
        // This gets the order ID
        $order_id = $order->get_id();
        
        error_log('Email ID is ' . $email_id . ' and order_id is ' . $order_id . __LINE__ . ' of ' . __FILE__);
        
        /*
            This constructs the path/filename to the attachment, assuming you put 
            the files in /home/<username>/customer_logos/<order_id>/<file>.
            Make sure to replace "<username>" below with the actual username for 
            your server, and that the path is correct for you.
        */
        $file_path = '/home/<username>/customer_logos/' . $order_id . '/';
        $filename = get_post_meta($order_id, 'order_files', true);
        if ($filename != '') {
            $attachment = $file_path . $filename;
            error_log('The attachment is ' . $attachment . ' on line ' . __LINE__ . ' of ' . __FILE__);
            if (file_exists($attachment)) {
                $attachments[] = $attachment;
            } else {
                error_log('The file ' . $attachment . ' was not found on line ' . __LINE__ . ' of ' . __FILE__);
            }
        }
        
    }
    
    return $attachments;
}

What I’ve done in the snippet above–in which you’ll need to add your username, just as you did before–is to use the PHP function error_log() to write information to the error log to tell us if the snippet is being triggered at all, if the error code is stopping it from running, if the $email_id is correct, if the conditional to attach the file to the completed order email is firing with the correct $email_id and $order_id, if the file path ($attachment) is correct for your server, and finally, if the file was actually found.

If all that shows that the snippet is working, and the file is still not attached to the email, we’ve got some other problem. For example, you may have noticed that I suggested you put the “customer_logos” folder outside the public_html folder on your server in order to prevent anyone from browsing directly to those files. That might be running into a permissions issue on your server, but that should show up in the error_log.

Whether/how your error_log is written to will depend on your server software and settings, so you may need to check with your web host if you don’t know where they are. If our snippet is not being triggered at all, none of my added error code will be executed either, so you may want to try testing your error log by adding the following line outside of any function in your functions.php, which will make it fire every time functions.php is run:

error_log(__FILE__ . ' was run. Delete line ' . __LINE__ . ' from functions.php.');

Another time-saver when debugging is to “tail” the error_log instead of downloading it to read it every time you test a change. If you have SSH access to your server, either through a local application or through your hosting control panel and you’re on a Linux server, you can use the following command to watch the error log. First use the cd command to change into the appropriate folder. For example, if you find the error_log we need is in /home/<username>/public_html/wp-admin, you’d use the following commands:

cd /home/<username>/public_html/wp-admin

Hit Enter to execute the command, then:

tail -f error_log

When you’re done, use Ctrl+c to exit tail.

Hi @spiderman7894, I’m not sure this would work, but I think I would try using WooCommerce’s built-in custom fields in the order for the file name and/or path.

For example, once you receive the order for the logo and complete the file(s) you need to attach to the order, go Admin > WooCommerce > Orders, select the order, and scroll down to Custom Fields.

Add a custom field named whatever you want for your attachment; e.g., “order_files”, and put the path and/or name of the file in the value field. Save the change.

In your code snippet to do the attachment, you can access the value (file name or path) as meta data for the order, and use it to specify the exact file path specific to the order. When you mark the order completed, your code will grab the file path from the order meta data, and attach the file to your email.

I believe the code you’d use in one of the snippets to get the custom field value, if your custom field is called “order_files” would be something like:


$filename = get_post_meta($order->get_id(), 'order_files', true);


That gets you the filename or path, which you can then incorporate into the code snippet. You’re probably not going to use the template directory as in those snippets. You’ll need to come up with a suitable path on your server for such files, and protect the directory from direct access.

That sounds like an opportunity to write a little PHP script to convert the attributes to the HTML you want and save it to the products’ Short Description.

If it were me, I’d do one manually, then look in the database to get the HTML WooCommerce created to use in the script.

With the script, you could also remove the attributes as you go.

Have you taken a look at WooCommerce Shipping Classes?

It seems like you could add the small products to one shipping class linked to your normal (flat rate?) shipping option, and the freight-quoted products can be in a separate “freight quote” class.

I’m not sure if Shipping Classes will lead you to a complete solution, but it’s the place I’d start.

My understanding is that if there are fewer than 30 variations, WooCommerce does an AJAX call to adjust the options available so that only the available options are shown, but if your have more than 30 possible variations (multiply the number of flavors by the number of strength options), the AJAX adjustments are not made, and it will be possible to select variation combinations that don’t exist, resulting in a message that the product is not available.

If that’s the problem you’re encountering (I got a 404 when I tried to look at the page, so I couldn’t tell) you can increase the AJAX variation threshold using the following filter in your child theme’s functions.php:

add_filter('woocommerce_ajax_variation_threshold', 'wc_ajax_variations_threshold' );
function wc_ajax_variations_threshold() {
    return X;
}

Replace the X with the number you want to increase the threshold to; e.g., if you have 40 variations, give it a little padding and use 45; the line would be:

return 45;

@mrclayton The issue just looked a little Elementor-ey to me, but I see you’re right.

Thanks again for creating the issue with WooCommerce. That’s above and beyond the call since it’s not even a problem with your plugin.