-- HikaShop version -- : latest
-- Joomla version -- : latest
-- PHP version -- : latest
Hey guys,
I created some custom fields, set them to display on 'backend list' and 'backend form' and added a specific category to them (ie. Category 1). I then imported a csv with those fields' columns name.
The problem is... when you have a category that is outside the defined (ie. Category 2) and try to edit an imported product. On the backend list, the product shows the custom field even if the product is in a category outside the defined above. If you edit that product, the fields won't show because this is the only 'check' for when to show those fields, thus you cannot change them.
Ie.
You create Custom field 1, text, restricted to Category 1
You import "Product 1, Category 2, ABC as the custom field 1"
You view the backend product list, it shows the column header "Custom Field 1" and at the row with Product 1, you see "ABC" shown under the custom field 1
You click Product 1 to edit it, but Custom field 1 is hidden / not shown because Product 1 is in category "Category 2", even though it has a value for the custom field.
Thus you either add Category 2 to the category list for the custom field. Or remove the field restriction on the custom field.
1) This isn't so much of a problem when importing. I rather not have the import process check active custom field rules as this could create undesired data truncation.
2) However what I would desire to see in future versions is an option like "If custom field value exist but category is restricted, then allow editing of the field on the backend anyways."
3) AKA the category restriction should only restrict on product creation the normal way via the backend, but if a product has the custom field filled, it should be editable in the backend when editng a pre-existing product with the custom field filled.
4) I haven't tested but what happens to the value if you change the category from an allowed category to a restricted category - does the script delete the value from the db or does it just ignore displaying it?
You could add an option to the custom field screen "Allow editing of field outside of restricted categories".