Highlight Tag bug?

[lesliekirk]

I may have discovered an issue between the default Custom Fields usage of the HighlightTag and the Tool Kit Custom Fields. The store owner updated the products using flat file import to update the field and used a tag that wasn't in the highlightTag list of values. What the import did was to then insert the "non-existent" tag into the Tool Kit Custom Fields and the drop down select for the Custom Fields was at <Select One>. The Tool Kit Custom Field "tag" is triggering the conditional.

Leslie

[Brennan]

Re: Highlight Tag bug?

Hi Leslie -

I don't think this has anything to do with the toolkit custom fields. All that is doing is reading the values of the custom fields and displaying it.

The way the select custom field work when doing an import like that, is it will import any value you have in your spreadsheet even if it is not contained in the select list. In the admin, it is displaying select one because the value does not match any available values in the drop down.

On the front end it is displaying because the conditional is checking for NOT ISNULL which it is, because it has the value imported from the spreadsheet.

If the customer is going to be importing these values via a custom field, they need to make sure they match the pre-defined select values. Either way it is going to import the data into the custom field.

[lesliekirk]

Re: Highlight Tag bug?

If the customer is going to be importing these values via a custom field, they need to make sure they match the pre-defined select values. Either way it is going to import the data into the custom field.

So there is no way to prevent it from importing an incorrect value?

[Brennan]

Re: Highlight Tag bug?

Correct, we don't have any data limitations on the import at this point. It will be up to the client to make sure the values for that field match one setup for the select.