Issues with Custom Attribute Styling after the upgrades

PLEASE, its taking ages to get a response in return so please at least bother to read the messages carefully. I said the custom Attributes are being used for REQUIREMENTS, the screenshot you sent me and most likely what you are looking for on the pages I sent you is NOT requirements. Please see attached for where to see the custom attributes being used for REQUIREMENTS and where it appears on the page

Provided privately below:

Hi, in theme file editor: “Woodmart: product-attributes.php (woocommerce/single-product/product-attributes.php)” I cannot find the line of code tha you need me to change

I have NOT made any changes, if you read my message yu’ll note that I couldnt even find the code you are talking about. Please keep in mind this was never an issue as you’ll see in the staging site I already provided which runs an older version of your theme where everything appears perfectly fine.

Im not sure if Im talking to one person or many but its already been ages just trying to solve this simple thing, please read the whole thread properly so we can save ourselves from wasting even more time. Issue still not solved

The issue is only on the staging site now because I pulled changes from the live site andso all updates to theme are now applied on the staging site too. The issue did not exist when the them was the older verion.

I am more than happy to apply the changes you suggested to the live site but for the 3rd time, I cannot see where that code is on the file you are pointing out. PLease find yet again my previous message:

Hi, in theme file editor: “Woodmart: product-attributes.php (woocommerce/single-product/product-attributes.php)” I cannot find the line of code tha you need me to change

For many security, customer privacy and legal reasons I cannot provide access to the live site but I am perfectly capable of applying the change myself. Can you see if your fix works on the staging site now that it is using the latestest up to date theme and then provide a FULL PATH to the file that needs to be changed and on what line.

Thanks

Thank you very much for the video. So from what I can see the issue and reason I cannot find the code you are talking about is that it does not exist on the live site. That file in the live site is exactly as follows and does not contain any of the rest of the code vsible in your video towards the end:

<?php
/**
* Product attributes
*
* Used by list_attributes() in the products class.
*
* This template can be overridden by copying it to yourtheme/woocommerce/single-product/product-attributes.php.
*
* HOWEVER, on occasion WooCommerce will need to update template files and you
* (the theme developer) will need to copy the new files to your theme to
* maintain compatibility. We try to do this as little as possible, but it does
* happen. When this occurs the version of the template file will be bumped and
* the readme will list any important changes.
*
* @var array $product_attributes List of product attributes.
* @see https://docs.woocommerce.com/document/template-structure/
* @package WooCommerce\Templates
* @version 3.6.0
*/

use XTS\Modules\Layouts\Global_Data as Builder_Data;

defined( ‘ABSPATH’ ) || exit;

if ( ! $product_attributes ) {
return;
}
?>
<table class=”woocommerce-product-attributes shop_attributes”>
<?php foreach ( $product_attributes as $product_attribute_key => $product_attribute ) : ?>
<?php
$attribute_name = str_replace( ‘attribute_pa_’, ”, $product_attribute_key );
$thumb_id = get_option( ‘woodmart_pa_’ . $attribute_name . ‘_thumbnail’ );
$image_size = apply_filters( ‘woodmart_product_attributes_table_image_size’, ‘thumbnail’ );
$attribute_hint = get_option( ‘woodmart_pa_’ . $attribute_name . ‘_hint’ );

if ( ! empty( Builder_Data::get_instance()->get_data( ‘wd_product_attributes_include’ ) ) || ! empty( Builder_Data::get_instance()->get_data( ‘wd_product_attributes_exclude’ ) ) ) {
$attributes_include = Builder_Data::get_instance()->get_data( ‘wd_product_attributes_include’ );
$attributes_exclude = Builder_Data::get_instance()->get_data( ‘wd_product_attributes_exclude’ );
$current_attribute_name = str_replace( ‘attribute_pa_’, ‘pa_’, $product_attribute_key );

if ( $attributes_include && ! in_array( $current_attribute_name, $attributes_include, true ) ) {
continue;
}
if ( $attributes_exclude && in_array( $current_attribute_name, $attributes_exclude, true ) ) {
continue;
}
}
?>

<tr class=”woocommerce-product-attributes-item woocommerce-product-attributes-item–<?php echo esc_attr( $product_attribute_key ); ?>”>
<th class=”woocommerce-product-attributes-item__label”>
<span class=”wd-attr-name”>
<?php if ( ! empty( $thumb_id ) ) : ?>
<?php if ( woodmart_is_svg( wp_get_attachment_image_url( $thumb_id ) ) ) : ?>
<?php echo woodmart_get_svg_html( $thumb_id, $image_size, array( ‘class’ => ‘wd-attr-name-img’ ) ); //phpcs:ignore. ?>
<?php else : ?>
<?php echo wp_get_attachment_image( $thumb_id, $image_size, false, array( ‘class’ => ‘wd-attr-name-img’ ) ); ?>
<?php endif; ?>
<?php endif; ?>
<span class=”wd-attr-name-label”>
<?php echo wp_kses_post( $product_attribute[‘label’] ); ?>
</span>
<?php if ( $attribute_hint ) : ?>
<?php woodmart_enqueue_js_library( ‘tooltips’ ); ?>
<?php woodmart_enqueue_js_script( ‘btns-tooltips’ ); ?>
<span class=”wd-hint wd-tooltip”>
<?php echo wp_kses_post( $attribute_hint ); ?>
</span>
<?php endif; ?>
</span>
</th>
<td class=”woocommerce-product-attributes-item__value”>
<?php echo wp_kses_post( $product_attribute[‘value’] ); ?>
</td>
</tr>
<?php endforeach; ?>
</table>

OK the changes you sugested doesnt seem to be fixing the issue. I provided staging access and a product page link. Can you show me where on my staging site your code can be seen to fix the issue?

Once again can you please show me a page on the staging site where this fix is working. The attributes at the top are in line now but the Requirements text is STILL mixed up and not as entered in the admin area, i.e NOT correctly formatted. Please see the attachement. THere is no point copying changes to Live site while the issue is STILL not fixed.

Thank you, it took almost 30 messages back and forth but we finally got there in the end