JJulien

Ok here’s the answer:

add_action( ‘wp_enqueue_scripts’, ‘dequeue_woocommerce_flexslider’, 99 );?

function dequeue_woocommerce_flexslider(){ 
wp_dequeue_script( ‘flexslider’ ); 
}

Hello,
I saw that in the headers too, and it is not 604800000, so this Cache-Control must not be the origin. There are many different cache settings, within the server, within the plugin, and none that I could find matched 604800000 except for in the Lighthouse results. This is why I reported it to my host, and to Litespeed. My host responded similarly, that this is not a server side setting, this is LSCache’s default setting.

I would like to ask you and other people here to test other sites which use LSCache, using Lighthouse, and check the same Performance heading ‘Serve static assets with an efficient cache policy’, TTL column to see if other servers are also reporting the same 604800000. This would help narrow down where the issue is coming from.
Thank you,
Julien

• This reply was modified 1 year, 9 months ago by JJulien.
• This reply was modified 1 year, 9 months ago by JJulien.
• This reply was modified 1 year, 9 months ago by JJulien.

Hello,
No, nothing has changed. The same results are still there. If you follow the example in the screenshot link, with heading ‘Serve static assets with an efficient cache policy’, you will see there under the TTL column 604800000. If you look in the Lighthouse report link for the same heading, you will see the same results.
Where exactly are you seeing 604800?
Thank you,
Julien

• This reply was modified 1 year, 9 months ago by JJulien.

I came back here to give an update.
Andrea has been helping me with the issue.
The support is excellent, he resolved all concerns.
Thank you again.

Hello,
I will email you.
Thank you

Resolved because i disables the wordpress and yoast sitemaps.
It seemed more feasible to generate a correct one than to fix the existing ones.

Hello May,
Thank you for your kind reply.
I have already seen the examples which you sent.
Yes I am very comfortable with adding code, but not code thats over one year old as in the first link; or 5 years old as in the second example; the third example, they dont mention how old it is.
Its my opinion that its not safe for woocommerce to make suggestions for code thats not written by themselves, or outdated suggestions either, because not only could it break a website or shopping cart, there could be security vulnerabilities.

Woocommerce has its own plugin for generating postage, which bills the store owner.

Let me outline the issues:
If you’ve been charging postage based on woocommerce’s failure to calculate true weight, then you’ve been undercharging or overcharging, based on the quantity ordered. Which translates into unhappy me, and USPS and UPS will delay the shipment if they find out the postage is insufficient.

If you’ve been overcharging because of this oversight, which you have been, then you are open to being sued by everyone using your cart, your postage plugin, and all of the other postage vendors that integrate with woocommerce, and all of their customers as well, for all the overages that you owe to them.

The fundamental issue is simple:
`Imagine you’re selling one product, and it weighs 10 lbs.
You enter that into woocommerce under Products > Said product > Shipping > Weight field.
Now think it forward. If a customer buys 1 of these, woo will calculate the weight as product weight x quantity = 10 lbs.
So seller sends PirateShip the order details, and pays PirateShip for postage on 10 lbs.
But it doesn’t work that way – its never the case.
Because that weight you entered, is the product weight, not the product + packaging. And in this example of 1 qty, the weight will be over 10 lbs for not including the packaging, meaning the postage will technically be insufficient.
Lets say you try to compensate for this, and in woocommerce you enter the true weight for that item, one number that combines packaging + 1 qty. Then if customer buys 2 qty, it will calculate the packaging 2x, and postage will be over what is actually necessary.

Its very simple for woocommerce to fix this. Simply expand the product weight rule, or the shipping rule, to include 2 entries instead of 1: One for packaging weight, and one for product weight.

The bottom line is, woocommerce generates order details, to be sent to postage vendors, and it should be the correct weight.

Thank you,
JJ

Hello Igor,
Thank you for chiming in.
Actually, you didnt understand me at all.

Thank you,
Jesse

Hello Margaret,
Thank you for your kind reply.
Unfortunately, these suggested plugins will not work for my needs.
1) WooCommerce Measurement Price Calculator
This is not in the woocommerce.org listing
There is no information about what version of wordpress it is compatible with.
There is no information about when it was updated.
All other SkyView plugins were updated 5 months ago, and are not compatible with the current version of wordpress.
They charge money.
They charge a lot of money.
They want a subscription.
2) Weight-based Shipping for WooCommerce
I have tried it.
This is as the other plugins, it is using weight to affect price. My price is fixed.
Also, I am not selling by weight.

When I find a solution I will post it here.
I continue to marvel at how companies that contract together, WooCommerce/ShipStation or WooCommerce/PirateShip, do not make sure, demand, that their services work together.

Best,
JJ