Change variant name

Hello,

We understand that this kind of configuration can sometimes seem disorienting but on the other hand it makes sense, and let me explain why:
1° You add a product (product as an option to your main product (product A), then you edit product B name
=> the option selector present the product name

2 ° You associated a characteristic to generate variant products from the main product A, and it leads to product Ab, product Ac etc...
Then, you modified the name of one of the product variant name, let's say product Ab for product Ab0 BUT when you are on the product page, this isn't the variant product name that you see in the selector, this is the characteristic value (set in Products dropdown => Characteristics).

The best demonstration is that if you choose the value relative of your changed name variant, it change the name on the product page, and you will see Product Ab0 as page title.

Hope this will be more clear in your mind anyway, we remain at your disposal for any further information.
Regards

Hello,

By a custom development almost everything is possible, but we didn't get why this will be more flexible.
If really you want have a different name in your selector, then you can edit your characteristic value (in order to modify the name).
And maybe you can have several characteristic (per product group or per product) in order to have always required name value for each product.

Regards

Hi,

Ok, now I can see why you want to do this.
So I see two ways to do this:
- it would be to have a specific ACL in HikaMarket to allow vendors to add their own values to characteristics without allowing them to modify the default values or the values of other vendors.
- it would be to develop a custom plugin implementing the onAfterVariantChecked(&$variant, &$element) event of HikaShop to modify the characteristics values to use the name of the corresponding variant.

The first approach will require extra checks to be implemented here and there and the interface to be adapted on the frontend characteristic edition. An extra column will also need to be added in the characteristic table to link values added by vendors to the corresponding vendor entry in the vendor table. The backend characteristic edit interface would also have to be modified to take this vendor link into account. And even an extra check in the backend product edition would be necessary to check that you're not using the value of a vendor for a product or variant linked to another vendor etc.
The second approach is simpler as it will only require a small plugin to be developed (so it would cost less and be faster to implement). However, the drawback is that this can only work for when products always only have one characteristic. If they have more than one characteristic, then you will have several variants which will match for the same value of a characteristic in each product and thus it's a logical problem since on one side we have one characteristic value text to replace, and on the other side we have several variants' name usable for that replacement.

Hi,

In the file product / form that you can edit via the menu Display>Views, you have this code to display the options selector:

	if(hikashop_acl('product/edit/options')) { ?>
			<dt class="hikashop_product_options"><label for="data_product_options_text"><?php echo JText::_('OPTIONS'); ?></label></dt>
			<dd class="hikashop_product_options"><?php
				if(hikashop_level(1)) {
					echo $this->nameboxType->display(
						'data[product][options]',
						@$this->product->options,
						hikashopNameboxType::NAMEBOX_MULTIPLE,
						'product',
						array(
							'delete' => true,
							'sort' => true,
							'default_text' => '<em>'.JText::_('HIKA_NONE').'</em>',
						)
					);
				} else
					echo hikashop_getUpgradeLink('essential');
			?></dd>
<?php
	}

'default_text' => '<em>'.JText::_('HIKA_NONE').'</em>',

'displayFormat' => '[{product_id}] {product_name} {xxx}',