Forum Replies Created

Viewing 15 replies - 376 through 390 (of 801 total)
  • Plugin Support Ryan Ray

    (@ryanr14)

    Hi @maxim12344,

    It looks like your product data area isn’t working when editing a product. Could you start by sending us your system status report?

    You can find it via WooCommerce > Status. Select “Get system report” and then “Copy for support”.  Once you’ve done that, paste it here in your response. That’ll give us some helpful additional information to work from.

    Plugin Support Ryan Ray

    (@ryanr14)

    Hi @cbhurji,

    Sorry for any confusion caused by our initial answer. To help clarify you will need to create a custom function where you can then use this filter. That function is a PHP snippet, so you’d can add that to your site in a few ways.

    If your child theme is custom, I would then add your function to the child themes functions.php file. If that child theme is made by another developer and it might get updated and overwrite your changes I would then use a plugin like Code Snippets to store your custom code. The following snippet then just slightly modifies the text output for what you were after.

    function custom_cart_totals_order_total_html( $value ){
        $value = '<strong>' . WC()->cart->get_total() . '</strong> ';
    
    // If prices are tax inclusive, show taxes here.
    	if ( wc_tax_enabled() && WC()->cart->display_prices_including_tax() ) {
    		$tax_string_array = array();
    		$cart_tax_totals  = WC()->cart->get_tax_totals();
    		if ( get_option( 'woocommerce_tax_total_display' ) === 'itemized' ) {
    			foreach ( $cart_tax_totals as $code => $tax ) {
    				$tax_string_array[] = sprintf( '%s %s', $tax->formatted_amount, $tax->label );
    			}
    		} elseif ( ! empty( $cart_tax_totals ) ) {
    			$tax_string_array[] = sprintf( '%s %s', wc_price( WC()->cart->get_taxes_total( true, true ) ), WC()->countries->tax_or_vat() );
    		}
    
            if ( ! empty( $tax_string_array ) ) {
                $taxable_address = WC()->customer->get_taxable_address();
                $estimated_text  = '';
                $value .= '<small class="includes_tax">' . sprintf( __( '(incl. VAT & delivery)', 'woocommerce' ), implode( ', ', $tax_string_array ) . $estimated_text ) . '</small>';
            }
        }
        return $value;
    }
    
    add_filter( 'woocommerce_cart_totals_order_total_html', 'custom_cart_totals_order_total_html', 20, 1 );

    The important part here being the text inside these parenthesis, which looks like this in Storefront.


    Link to image: https://cld.wthms.co/jV0kBT

    &


    Link to image: https://cld.wthms.co/lud7e6

    • This reply was modified 7 years ago by Ryan Ray.
    Plugin Support Ryan Ray

    (@ryanr14)

    Hi @philipatnedi,

    My first question is just about how base WooCommerce processes orders – if it saves the SKUs with the order or if it just retrieves it based on product. I can’t find any meta or any other field to indicate that the SKU is actually saved with the order.

    I’m not 100% certain, but I believe the order pulls in the SKU based on the product(s) in the order. So it’s likely not something that is saved as ordermeta, rather pulled in with something like the snippet below.

    foreach ($order->get_items() as $item) {
        $product = wc_get_product($item->get_product_id());
        $item_sku[] = $product->get_sku();

    That then says to me it’s likely the Autoship extension gets a product for the next recurring order but doesn’t also use get_sku() in that order for said product(s).

    Plugin Support Ryan Ray

    (@ryanr14)

    Hi @kreativjul,

    Looking through your system status I didn’t spot a few lookup tables that may be important to the issue here. Or could be a sign of something off in the reports due to a database issue. Would you also know why different tables use different prefixes in your database, they should all be using the one defined in the wp-config.php file.

    Normal lookup tables
    Link to image: https://cld.wthms.co/aL0MSo

    The above are the missing lookup tables that should be in your database. Could you try regenerating those under the WooCommerce > Status > Tools tab. There you’ll find a button to regenerate those. 🙂


    Link to image: https://cld.wthms.co/EKXE2f

    Plugin Support Ryan Ray

    (@ryanr14)

    Howdy all,

    It looks like this is now solve and due to a WPML issue. I’ll mark as resolved. Thanks! 🙂

    Ryan Ray

    (@ryanr14)

    Hi @michelgr1969,

    Would you be willing to post your system status here for us? You can find it via WooCommerce > Status. Select “Get system report” and then “Copy for support”.  Once you’ve done that, paste it here in your response.

    Thanks!

    Plugin Support Ryan Ray

    (@ryanr14)

    Hi all,

    It looks like at this point any database issues have been mostly solved, or at least a way found to get the look-up tables and more populating. I’ll mark it solved for the time being, but please do create any new threads needed if we can help further. Thanks!

    Plugin Support Ryan Ray

    (@ryanr14)

    Hi @wooworld,

    At this point that ufile link expired, unfortunately. Nonetheless, it looks like you’re using the The7 theme. I would then assume the theme likely needs updating to go along with the WooCommerce update that seems to have thrown your product page for a loop.

    It may have out of date template overrides or otherwise, but making sure everything is up to date should help big time. Thanks!

    Ryan Ray

    (@ryanr14)

    Hi @lionelbachelart,

    Hmm, that is odd indeed. When I tested your site in Firefox I have the same issue. The good news is that I don’t see the same thing on my own test site in Firefox.

    Test site Firefox
    Link to image: https://cld.wthms.co/c8Acm3

    That at least means it’s not a wider Storefront problem, and is happening in your specific setup. Inspecting your site further and looking at the Console in Firefox I do see this issue related to the FontAwesome font file.

    fontawesome error
    Link to image: https://cld.wthms.co/0BXxGS

    It seems to say that the font file is trying to be loaded from https://rampageous-tax.000webhostapp.com, but not allowed because a CORS header hasn’t been added to the site to add ‘Access-Control-Allow-Origin’ for the https://rampageous-tax.000webhostapp.com URL.

    You would likely want to look at any potential security plugins you have to tweak these settings, or take it up with your host if it is perhaps handled by them. The font file either needs loaded from your current domain (https://vovino.tk/) or there needs to be a ‘Access-Control-Allow-Origin’ CORS header added that allows the font file to be loaded from https://rampageous-tax.000webhostapp.com.

    I hope that makes sense. 🙂

    Plugin Support Ryan Ray

    (@ryanr14)

    Hi @alfalinkdev,

    This could be very theme dependent and also potentially dependent on the original size of those images that appear off compared to the others. Is there a live page/URL you can send us and we can inspect those images further.

    Also, can you tell me what you see when you open the customizer and head to WooCommerce > Product Images?


    Link to image: https://cld.wthms.co/O8pSLb

    • This reply was modified 7 years ago by Ryan Ray.
    Plugin Support Ryan Ray

    (@ryanr14)

    Hi @subrat4php,

    I assume you are wanting to create more than 50 variations at a time when using the option here?


    Link to image: https://cld.wthms.co/MPwtXX

    That constant won’t work in the functions.php file, but with that added to your wp-config.php file what issue did you see when trying to create variations? Just one clarifying point, even though it still says (Max 50 per run) as the image below shows it will do 250. If you do get it to run does it not make 250 variations for you?


    Link to image: https://cld.wthms.co/gxnEiA

    Thanks for helping confirm and clarify further.

    Plugin Support Ryan Ray

    (@ryanr14)

    Hi @frand001,

    Not a problem at all, we’re all here awaiting a public view of a product page to potentially advice some CSS tweaks. 🙂

    Plugin Support Ryan Ray

    (@ryanr14)

    Hi @telebarn,

    Did a temporary theme switch help anything here and let you start creating products? 🙂

    Plugin Support Ryan Ray

    (@ryanr14)

    Hi @jakiti,

    If it helps clarify, the forums here on WordPress.org are monitored via some of us here at WooCommerce/Automattic, but is mostly a community moderated resource for help. That may mean waiting a little longer than say our premium support resources, nonetheless I apologize for the wait currently. 🙂

    Regarding your issue, could you start by sending your system status here? You can find it via WooCommerce > Status. Select “Get system report” and then “Copy for support”. Once you’ve done that, paste it here in your response. That’ll help us see if there could be anything there to update or change at first.

    Beyond that can you also explain and add more info about your tax settings. What are the other settings for your GST rate. The same for the product in question, what are its tax settings? Thanks, this info will help us get a complete picture to try and recreate and better troubleshoot!

    Plugin Support Ryan Ray

    (@ryanr14)

    Hi @laura182,

    Thanks for patiently awaiting a reply. I’m glad you could get the Site Info sent our way, but unfortunately from that I can’t see any issues that would be causing WooCommerce to cause the fatal error or why checkout would be having that Country field issue.

    I can currently see WooCommerce is still up and running on the site with the existing Country field issue, of course. If you are still having trouble logging in or accessing other parts of the site or WooCommerce it might be worth first contacting your host. They would have access to more in depth, hopefully, error logos to help see what part of WooCommerce could be triggering a fatal error.

Viewing 15 replies - 376 through 390 (of 801 total)