jordanwebdev

Thanks for the response. In your example, wouldn’t that delete all products with the “height” attribute? I want to delete products that contain a specific attribute value, not all products that simply have a certain attribute.

Let’s say, for example, there is a colour attribute, and values green, red, blue. In this example, I would want to delete all products of colour green.

Also, aren’t attributes technically taxonomies, and not custom fields?

I didn’t update to pro. Ended up creating my own custom functionality (see above). I created my own custom form for dimensions below the filters.

Sorry, I see there are settings in the SMTP plugin for this. This is resolved.

I think there should be an option for it in this plugin, though, rather than defaulting to the admin e-mail address.

I get the same issue, using the free version.

Any resolutions yet?

Awesome. Does that $49 1 site license plan include unlimited updates?

Got it working with the following. I added a form for this on the front end, which submits values that are retrieved here using $_GET.

Of course it would be nice if this was a part of the plugin :).

Note that I’m using decimal casting because sometimes a value of 0 was set for the height/width, which is incorrect. So I used 0.01 instead of 0 for the min.

add_filter('get_meta_sql','cast_decimal_precision');
function cast_decimal_precision( $array ) {
  $array['where'] = str_replace('DECIMAL','DECIMAL(10,3)',$array['where']);
  return $array;
}

// Width Query
    $min_width = $_GET['width_min'] ?? false;
    $max_width = $_GET['width_max'] ?? false;
    if ($min_width !== false && $max_width !== false) {
      $min = intval($min_width) === 0 ? 0.01 : $min_width;
      $width_query = array(
        'key' => '_width',
        'value' => array($min, intval($max_width)),
        'compare' => 'BETWEEN',
        'type' => 'DECIMAL',
      );
      $meta_query[] = $width_query;
    }

    // Height Query
    $min_height = $_GET['height_min'] ?? false;
    $max_height = $_GET['height_max'] ?? false;
    if ($min_height !== false && $max_height !== false) {
      $min = intval($min_height) === 0 ? 0.01 : $min_height;
      $height_query = array(
        'key' => '_height',
        'value' => array($min, intval($max_height)),
        'compare' => 'BETWEEN',
        'type' => 'DECIMAL',
      );
      $meta_query[] = $height_query;
    }

Not sure if this is related.

Undefined variable $keyData (woo-product-filter/modules/meta/models/meta.php:164). This error happens on the shop page even when no filters are selected.

I tried the following but it only works when there are no WooBeWoo filters selected. This is in a pre_get_posts action function I created.

$min_width = $_GET['width_min'] ?? false;
$max_width = $_GET['width_max'] ?? false;
if ($min_width !== false && $max_width !== false) {
  $width_query = array(
    'key' => '_width',
    'compare' => 'BETWEEN',
    'value' => array(intval($min_width), intval($max_width)),
    'type' => 'NUMERIC',
  );
  array_push($meta_query, $width_query);

  $query->set( 'meta_query', $meta_query );
}

• This reply was modified 3 years, 5 months ago by jordanwebdev.
• This reply was modified 3 years, 5 months ago by jordanwebdev.
• This reply was modified 3 years, 5 months ago by jordanwebdev.

That is the same problem that I noticed with 3.16. Reverting to 3.15 resolved the issue.

My idea is to replace line 121 of wp-scss/class/class-wp-scss.php with the following:

$unlink_file = $cache.$cache_file->getFilename();
              if (is_file($unlink_file)) {
                unlink($unlink_file); // Delete file on successful write
              }

If that doesn’t work, perhaps the following will:
https://stackoverflow.com/a/33913406/5644982

The problem is on lines 144 and 145 of functions/enqueue.php. Need to pass an array as the third parameter.

FA also says span is more semantically correct

We like the <i> tag for brevity and because most folks use for emphasized/italicized semantic text these days. If that’s not your cup of tea, using a <span> is more semantically correct.

WCAG 2.0 website compliance is law in some places, so it’s not really something that’s up for interpretation.

How about adding an option to use it, reverting to <i> by default?

Hey, just wondering if there’s anything I can do in the interim to pass this check?

1.10.1

It appears that logging was already off for me, too, and yes, we’re having a similar issue with another plugin regarding a WooCommerce function.