baltas

Yes, I did it like this:

//Show Regular/Sale Price or Eligible Products @ WooCommerce Cart Table
add_filter( 'woocommerce_cart_item_price', 'My_change_cart_table_price_display', 30, 3 );
  
function My_change_cart_table_price_display( $price, $values, $cart_item_key ) {
   $slashed_price = $values['data']->get_price_html();
   $is_on_sale = $values['data']->is_on_sale();
   if ( $is_on_sale ) {
      //Striked Price
      //$price = $slashed_price;
      //Mark products eligible for the discount maintaining regular Price
      $price = $price . "<br>(Eligible for Discount Coupon)";
   }
   return $price;
}
// ##############################

No, that is not the issue.
The problem is I have on settings to see strikeout prices on cart for products, but they are not showing.

It shows normal prices on cart for the products, them normal subtotal, them under the -value for coupon and in the end the total with correct calculated value.

Solve it.
The problem was the apostrophes since you say on the CPT field:
“CPT slugs in apostrophes, comma separated”

but using this after saving the system escapes them with \ and doesn’t work.
As soon I entered the post type names without the apostrophes all started working!

Sorry. maybe I choose wrongly the words parent and child as what I’m talking is nothing related with a theme.

Just face this scenario, I have a pluging that on it’s starting initialize this:

load_plugin_textdomain( ‘xpto-text-domain’, false, basename( ‘my-plugin’ ) . ‘/lang’ );

a few parts of the code this plugin uses this initialized text domain, but other uses something totally different like “abcd-text-domain”, so what I was saying is if I want to translate this plugin using Loco I’ll creat the language file for the first text domain “xpto-text-domain” and a subset for the other (“abcd-text-domain”).

What happens right now?
if the plugin does not load the second domain or I don’t do it myself on functions.php I’m not going to have any kind of translations for all the plugin areas that is using this second text domain.

So my idea is what about all the defined subsets being auto load since the first/main one is a valid and working ok, like this all the translation operation is more easier for the normal user?

The substs now only make sense for me as a way of organizing and knowing that this plugin as other text domains since also is not possible to create separated text domains for the same plugin.

Off course this happens because sometimes the plugin developers they don’t do things right, but it helps bypassing that problem for the translations.

Ok here is a link with the image capture from a review edit:

https://ibb.co/v3YP9BR

Humm… even in the standard “Comments” page I can’t see any option to do that, can you explain?