Forum Replies Created

Viewing 15 replies - 16 through 30 (of 813 total)
  • Thread Starter Kahil

    (@kahil)

    Yes, but still…that is just a page. As I mentioned, if I put it under /shop/ directly, it will load just fine. This is only happening when I nest it under /shop/business-cards/ specifically does it do this.

    Thread Starter Kahil

    (@kahil)

    No offense, but if the plugin isn’t working correctly or as expected, people aren’t going to use it.

    Thread Starter Kahil

    (@kahil)

    @jamestav If you look at the source of a published product with add-ons, you’ll see that each addon will have a class that matches what you named it. Each variable in there, like each checkbox, will also have a unique class based on the add-on name…will be something like.. addon-name-0, addon-name-1…and so on. That’s how I am currently able to apply custom CSS. So…that’s why I think it would be easier for this plugin to harness that info to make it more flexible with some IF logic applied. Like… IF no options have been selected for the product, show no addons. If option 1 and option 2 have a specific variable selected, show only these add-ons, etc. Could turn this plugin into a very robust one. The only thing that would be the challenge here are add-ons that you mark as required and then being able to add to your cart of a required add-on is hidden because it wasn’t needed for a specific variation.

    Thread Starter Kahil

    (@kahil)

    Will try it out. But as a dev myself, I know that it isn’t my user’s responsibility to remind us to release an update to fix a known issue…especially since you knew of the issue and already had a fix. Beta or not.

    Will update my review once I’ve had a chance to test it out fully.

    Thread Starter Kahil

    (@kahil)

    Actually, I think that there might be a way. Now the Product Addons plugin adds an additional class that is based on what you named the addon section. You could add a simply text field option in there that shows when the checkbox is ticked that allows us to put in that added detail. Right now you have the .js file set to hide the .product-addon sections if ticked. By adding the text box, you could plug that in to add specific sections only. For instance… IF the box is ticked and IF “your name” is put in the text field, then the part that gets blocked will only be .product-addon-your-name and so on. Seems pretty easy to do…I actually did so to test with a custom field. So that’s something you can consider in order to take it to the next level.

    On a related note…I just left a review…this plugin simply isn’t working, at least for me. I have specific variations set to hide, but they don’t.

    Thread Starter Kahil

    (@kahil)

    The most recent version of each.

    Thread Starter Kahil

    (@kahil)

    I figured it out…wasn’t actually that difficult of code in the end, but took a bit of tinkering and testing to get right. I had trouble at first with just getting the current date because the server time for my site tends to vary. It’s a large host and on a shared server. To make things consistent I had to set the timezone. Being that the physical products are by default only sold in the U.S., I set it to the New York time zone since that would be the first U.S. time zone to hit midnight and start the new day. To account for the time zones that haven’t hit midnight of the sale end date, you have to tell it to get yesterday’s date stamp.

    So in the end, if the sale end date is in the future, it will display a date string. If the sale end date is today, it will display “Today”.

    If anyone knows of a more elegant way that pulls the set sale end date from Woocommerce, please do share. I haven’t been able to find a reliable means of doing so that fits my stated logic in the OP.

    Here is the code I used… It uses the datepicker option in ACF and also takes into account a specific time of day my time.

    // adds sale end date
    add_action( 'woocommerce_single_product_summary', 'sale_end_date', 6 );
    function sale_end_date () {
    date_default_timezone_set("America/New_York");
    $saledate = get_field('sale_end_date');
    $saletime = get_field('sale_end_time');
    $y = substr($saledate, 0, 4);
    $m = substr($saledate, 4, 2);
    $d = substr($saledate, 6, 2);
    $time = strtotime("{$d}-{$m}-{$y}");
    $saleenddate = date('F d, Y', $time);
    $yesterday = date("F j, Y", strtotime("yesterday"));
    $today = date('F d, Y');
    global $product;
    if ($product->is_on_sale() && get_field('sale_end_date') ){
        echo '<div style="margin-top:5px;margin-bottom:5px;"><div class="iconbox_icon heading-color" aria-hidden="true" data-av_icon="" data-av_iconfont="entypo-fontello" style="color:#d54e21;margin-right:5px!important;"></div><strong style="color:#d54e21;font-size:13pt;line-height:22px;text-transform:uppercase;">Sale ends: ';
    	if ( ($saleenddate == $today) || ($saleenddate == $yesterday) ) {
    		echo "Today!";
    	} else {
    		echo $saleenddate;
    	}
    	if (get_field('sale_end_time')) {
    		echo ' @ '. $saletime .' PST';
    	}
    	echo '</strong></div>';
    }}

    Thread Starter Kahil

    (@kahil)

    Nothing like that is a factor. I’m not a noob. All I know is that this started happening moments after the update was applied.

    Thread Starter Kahil

    (@kahil)

    Dong that only allows you to set a specific price or change an existing sale price. It doesn’t allow you to set the sale price based on a percentage of whatever the regular price is for variation.

    Thread Starter Kahil

    (@kahil)

    First, no need to be rude. If you’re just going to talk down to users, then why bother commenting? Nothing was expected in terms of having a special plugin made. The only thing that would be expected is hopes of making variable products easier to manage. Things like filters, being able to bulk set sale prices based on the regular price (can only do so if something is already entered into a variation’s sale price), etc.

    It isn’t that variations are inherently difficult to manage. It is that the product itself loads slower the more variations you add, especially because the number you can manage at once is limited to what…25?

    The idea here is to give a discount if a user buys three specific combinations of a product. Neither the coupons nor dynamic pricing plugins offer that flexibility…even if they all were broken out into separate variations.

    Creating simple products for over 100 variations just to combine them with a bundle or composite plugin, which aren’t cheap plugins, would be even more unmanageable. Can’t imagine that’d help keep the store running fast….besides needing countless hours just to set up.

    The only thing I can think of is to break the product up into sets of variable products, each having the separate variables. Then I could use the dynamic pricing plugin to apply that discount based on specific variables.

    Alternatively, it would be a LOT easier if the dynamic pricing plugin didn’t list variables by ID. Or at least have a mouse over on the ID numbers that displays the variation options.

    Thread Starter Kahil

    (@kahil)

    Upon further review, that plugin doesn’t do what I particularly need…as in on the product specific level. :/

    Thread Starter Kahil

    (@kahil)

    This plugin appears to do the bulk editing of prices based on a percentage…but haven’t tried it. Not a fan of paying for plugins just to test them. :/

    http://codecanyon.net/item/woocommerce-bulk-edit-variable-products-prices/6822726

    Thread Starter Kahil

    (@kahil)

    I still haven’t found a solution. :/

    I personally feel that this should be part of the Woocommerce plugin. Programmatically, it isn’t difficult to take the value of one field and set another field using math. Here it would just be setting the sale price of all variations by reducing it by a specific percentage.

    As it is, it’s difficult to manage products with a lot of variations…even if the variations all have the same price or just two different prices. Variable products need some work in that respect. For instance, I have one product that has a LOT of variable options, but only two different prices set based on the first option. I want to give discounts for getting specific sets of available options, but to do so, I have to create all possible variations when only two are really needed.

    Just wish variable products were easier to manage all around…

    Thread Starter Kahil

    (@kahil)

    It definitely wasn’t a theme issue as neither woocommerce nor the theme been updated or modified in any way when this happened. I think it was just a random bug where something in the database got stuck as marking products on sale. The moment it happened was when I deleted variations while they had sale prices and date ranges set. I updated the theme, Enfold, tonight first, then checked…issue was still there. Only after I updated woocommerce and did the database update it requested did the problem go away.

    Thread Starter Kahil

    (@kahil)

    Ok….after I tried all that…the theme I was using finally updated so I could update WooCommerce to the new major update. If I go in and save the items it clears the issue. I’ll leave this open for a couple more days to make sure the issue is gone before marking it as resolved. Looks like the update cleared whatever was stuck in the database when it did the optimization after updating.

Viewing 15 replies - 16 through 30 (of 813 total)