Forum Replies Created

Viewing 15 replies - 1 through 15 (of 18 total)
  • Thread Starter bash88

    (@bash88)

    That solved it. Thanks @vishabjeet!

    Hi @shresthauzwal,

    Could you maybe fix this in the translation file or in the plugin code? It’s getting really annoying to have to change the translation every time I need to edit a form.

    Thank you!

    Hi @shresthauzwal,

    Could you please make sure this is fixed in all translation files for your plugin? This bug returns every time the plugin is updated. So then I have to edit the translation manually every time (NL translation).

    Maybe just remove the plugin name translation string from the plugin code? It’s clearly causing problems.

    Regards,
    Bas

    Thread Starter bash88

    (@bash88)

    Hi Alex,

    The problem is resolved. It was a CSS conflict that caused the year input to be hidden.

    So for clarity and future visitors: this wasn’t caused by the github issue I linked to in my starting post.

    Hi guys,

    I’m experiencing the same problem as Floris. There is no way to alter the year in the Flatpickr datepicker. I traced it down to this github issue. I tried implementing the mentioned solution myself but couldn’t get it to work.

    Could you please get a developer to look at and fix this?

    Regards,
    Bas

    Thread Starter bash88

    (@bash88)

    Hi @davdebcom

    Thanks for pointing me in the right direction. For anyone else looking for this, here’s a short explanation.

    add_filter( 'woocommerce_mollie_wc_gateway_creditcard_args', 'filter_mollie_payment_data', 10, 2 );
    
    function filter_mollie_payment_data($data, $order) {
    ...
    get custom housenumber field and add to $data
    ...
    return $data;
    }

    Note that you have to add a filter for each payment gateway you use. Above is for creditcard. Other gateway filters would look like: ‘woocommerce_mollie_wc_gateway_[gateway]_args’.

    Regards,
    Bas

    Thread Starter bash88

    (@bash88)

    Hi @pressmaximum,

    Well, your screen recording shows you aren’t using the Ajax product filering plugin I’m using. Even with the latest 0.2.8 version of Customify the product info duplication is still happening.

    Zould you please help me with this?

    Thread Starter bash88

    (@bash88)

    Hi Guys,

    Me again. When I activate the twenty seventeen theme the plugin works fine, so the plugin author is referring me back to you.

    When I ajax filter products with Customify being active the results show with some duplicate product content (image, price, add-to-cart button) printed in .wc-product__part.wc-product__title.

    Could you maybe point me in the right direction? Is your html structure different from the standard Woocommerce product loop?

    Screenshot here, code sample in previous post.

    Thread Starter bash88

    (@bash88)

    Hi @pressmaximum,

    Thanks for your reply!

    I’m on my local dev environment so I can’t show you online. How can I best provide you with what you need to look into this? Screenshot? Rendered code:

    <li class="post-1567 type-product status-publish has-post-thumbnail product_cat-music product first instock downloadable virtual purchasable product-type-simple customify-col" style="opacity: 1;">
    	<div class="wc-product-inner">
    	<div class="wc-product-media"><a href="http://localhost/product/album/" class="woocommerce-LoopProduct-link woocommerce-loop-product__link"><img width="300" height="300" src="http://localhost/wp-content/uploads/2018/11/album-1-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="" srcset="http://localhost/wp-content/uploads/2018/11/album-1-300x300.jpg 300w, http://localhost/wp-content/uploads/2018/11/album-1-150x150.jpg 150w, http://localhost/wp-content/uploads/2018/11/album-1-768x768.jpg 768w, http://localhost/wp-content/uploads/2018/11/album-1-600x600.jpg 600w, http://localhost/wp-content/uploads/2018/11/album-1-100x100.jpg 100w, http://localhost/wp-content/uploads/2018/11/album-1.jpg 800w" sizes="(max-width: 300px) 100vw, 300px"></a></div><div class="wc-product-contents"><a href="http://localhost/product/album/" class="woocommerce-LoopProduct-link woocommerce-loop-product__link"></a><div class="wc-product__part wc-product__category show-in-grid show-in-list"><a href="http://localhost/product/album/" class="woocommerce-LoopProduct-link woocommerce-loop-product__link"></a><a class="text-uppercase text-xsmall link-meta" href="http://localhost/product-categorie/music/" rel="tag">Music</a></div><div class="wc-product__part wc-product__title show-in-grid show-in-list"><img width="300" height="300" src="http://localhost/wp-content/uploads/2018/11/album-1-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="" srcset="http://localhost/wp-content/uploads/2018/11/album-1-300x300.jpg 300w, http://localhost/wp-content/uploads/2018/11/album-1-150x150.jpg 150w, http://localhost/wp-content/uploads/2018/11/album-1-768x768.jpg 768w, http://localhost/wp-content/uploads/2018/11/album-1-600x600.jpg 600w, http://localhost/wp-content/uploads/2018/11/album-1-100x100.jpg 100w, http://localhost/wp-content/uploads/2018/11/album-1.jpg 800w" sizes="(max-width: 300px) 100vw, 300px"><h2 class="woocommerce-loop-product__title"><a href="http://localhost/product/album/" class="woocommerce-LoopProduct-link woocommerce-loop-product__link">Album</a></h2>
    	<span class="price"><span class="woocommerce-Price-amount amount"><span class="woocommerce-Price-currencySymbol">€</span>15.00</span></span>
    </div><div class="wc-product__part wc-product__price show-in-grid show-in-list">
    	<span class="price"><span class="woocommerce-Price-amount amount"><span class="woocommerce-Price-currencySymbol">€</span>15.00</span></span>
    </div><div class="wc-product__part wc-product__description hide-in-grid show-in-list"><div class="woocommerce-loop-product__desc"><p>This is a simple, virtual product.</p>
    </div></div><div class="wc-product__part wc-product__add_to_cart show-in-grid show-in-list"><a href="http://localhost/product/album/?add-to-cart=1567" data-quantity="1" class="button product_type_simple add_to_cart_button ajax_add_to_cart" data-product_id="1567" data-product_sku="woo-album" aria-label="Voeg 'Album' toe aan je winkelmand" rel="nofollow"><span class="button-label">In winkelmand</span></a></div><a href="http://localhost/product/album/?add-to-cart=1567" data-quantity="1" class="button product_type_simple add_to_cart_button ajax_add_to_cart" data-product_id="1567" data-product_sku="woo-album" aria-label="Voeg 'Album' toe aan je winkelmand" rel="nofollow"><span class="button-label">In winkelmand</span></a></div>	</div>
    </li>
    Thread Starter bash88

    (@bash88)

    Hi Takayuki,

    Just a little bump on this thread. Today I updated to 5.0.1 and I had to do this fix again. Could you let me know when you will be able to fix this or, if you’re not going to so, why?

    Thanks.

    Thread Starter bash88

    (@bash88)

    A custom plugin by a supplier. Not really worth mentioning the name here.

    I guess it’s going to turn out to be something like this (found this in another thread):

    “It was caused by an extra space after the closing ?> in a plugin file…”

    Thread Starter bash88

    (@bash88)

    Ben,

    Thank you very much for taking the time to help.

    In the end it turns out it’s another plugin unrelated to both WP Super Cache and the minifying plugin causing the issue.

    Thread Starter bash88

    (@bash88)

    Do you know if the compression is done through a WP function?

    Thread Starter bash88

    (@bash88)

    Yes, the minifying plugin has always worked as expected.

    I disabled both WP super cache and the minifying plugin when I noticed the issue last week.

    WP super cache is now active without compression. When I activate the minifying plugin the minified files generate the same ERR_CONTENT_DECODING_FAILED error in the console the page compression in WP Super cache did.

    Thread Starter bash88

    (@bash88)

    The issue was completely persistent for all pages. First time page load after clearing the cache = error. After that, fine. So based on your info I don’t think it’s the memory.

    I see now that the files compressed by my minifying plugin generate the same error. Completely unrelated to WP super cache, but then maybe the WP 4.8 update changed something in compression which affects both plugins?

    Is the compression done through a WP function or something?

Viewing 15 replies - 1 through 15 (of 18 total)