Forum Replies Created

Viewing 9 replies - 1 through 9 (of 9 total)
  • I’ve changed the jQuery selector as suggested, but it doesn’t solve the issue for me ( i’ve tried with another browser to be sure about cache and so on )

    My stripewoo.js is there:

    https://www.nexlab.net/wp-content/plugins/stripe-woocommerce-addon/assets/js/stripewoo.js

    Diego: i’m actually also an aelia paying customer (for other plugins) and also a business, so, i really get what you mean.

    Anyway, thanks to add this feature in the queue for future release.

    Diego: It is suggested to anyone writing plugin to add a filter anytime you add content, and it’s a great suggestion.

    I understand the scope of eu-vat-assistant, i understand what you are saying, but you are assuming one have a shop used only for a company and you don’t take that there are use case where you can have in the same shop a donation for free projects AND a company product, in this case having a way to activate and/or deactivate it only for specific products make totally sense, think about that for a future release please.

    Thread Starter nextime

    (@nextime)

    I don’t had (yet) the time to fully investigate it, but i will do for sure in the next few days, if i will find an easy solution i will send you a patch

    Diego: no, even using other plugins like woocheckout it cannot done cause eu-vat-assistant doesn’t add the field to the cart field array nor it offer an hook to filter it’s output, so, it doesn’t see it at all and it cannot hide it.

    so, i understand when you say “Hding checkout fields is outside the scope of the EU VAT Assistant”, but or you give this opportunity or at least move the eu-vat-assistant fields in the cart array to let other plugins do that.

    Actually the only way i have found is to hide it in functions.php of my theme by doing:

    add_filter('wc_aelia_eu_vat_assistant_location_evidence_countries', 'disable_eu_vat_countries');
    
    function disable_eu_vat_countries($countries)
    {
       global $wordpress, $woocommerce;
       $products = $woocommerce->cart->get_cart();
       foreach( $products as $product ) {
          if($product['product_id']==1264) {
             add_action( 'wp_footer', 'inline_hide_eu_vat' );
             return array('US','US');
          }
       }
       return $countries;
    }
    
    function inline_hide_eu_vat() {
    ?>
    <script type="text/javascript">
    jQuery(".aelia_eu_vat_assistant").hide();
    </script>
    <?php
    }

    Of course this isn’t an ideal way to do that, but eu-vat-assistant doesn’t offer a filer hook to remove it at all.

    The option to hide checkout fields should be there anyway. For example i use woocommerce both for my professional activity AND, with a separate (virtual) product list, for donations outside my businness.

    For donations i should NOT apply vat nor ask for anything related to it, and i cannot disable this annoying request

    The issue is in the line 65 in woocommerce-bulk-discount.php

    add_action( 'woocommerce_loaded', array( $this, 'woocommerce_loaded' ) );

    Here it happens that when woocommerce finish to load it call the woocommerce_loaded action, and only after that the woocommerce-bulk-discount plugin is loaded, so, it never get this action called and for this reason it doesn’t work.

    You can just change that line with:

    add_action( 'plugins_loaded', array( $this, 'woocommerce_loaded' ) );

    And it will work.

    Well, supercache plugin should already manage that. I was having the very same issue on my wordpress site, and it wasn’t caused by wp-supercache, but instead the cause was mod_spdy, maybe you are using that too.

    In this case, the cause is that where supercache used with mod_rewrite is rely on RewriteCond %{HTTPS} on variable to detect https requests, mod_spdy seems to not comply to set this variable, so, the rewrite condition doesn’t match.

    The workaround is to sobstitute in the .htaccess generated by supercache
    all the lines
    RewriteCond %{HTTPS} !on
    with:
    RewriteCond %{SERVER_PORT} ^80$

    and all the lines
    RewriteCond %{HTTPS} on
    with:
    RewriteCond %{SERVER_PORT} ^443$

    This way, assuming you are using standard ports for http and https, it should work.

    Also, when process shortcodes isn’t checked, should be a good thing to remove shortcodes from the pdf output, so, for example, if [tab id=1] content [/tab] isn’t processed cause process shortcodes option isn’t checked, the generated pdf doesn’t include the shortcodes but only the content

Viewing 9 replies - 1 through 9 (of 9 total)