Custom fields options not saved?
9 years 4 months ago #271006
by renem
Custom fields options not saved? was created by renem
-- HikaShop version -- : 3.1.1
I made a new custom field.
This field is showing up when i edit a product. But when i chose a value of the custom field, and saving the product the value is not stored ????
(no error messages on maximum reporting)
Kind regards
I made a new custom field.
This field is showing up when i edit a product. But when i chose a value of the custom field, and saving the product the value is not stored ????
(no error messages on maximum reporting)
Kind regards
Please Log in or Create an account to join the conversation.
9 years 4 months ago #271007
by Jerome
Jerome - Obsidev.com
HikaMarket & HikaSerial developer / HikaShop core dev team.
Replied by Jerome on topic Custom fields options not saved?
Hello,
Please provide more details about the custom field and its configuration (using screenshot would be useful).
Regards,
Please provide more details about the custom field and its configuration (using screenshot would be useful).
Regards,
Jerome - Obsidev.com
HikaMarket & HikaSerial developer / HikaShop core dev team.
Please Log in or Create an account to join the conversation.
9 years 4 months ago - 9 years 4 months ago #271063
by renem
Replied by renem on topic Custom fields options not saved?
Sure Jerome,
Last edit: 9 years 4 months ago by renem.
Please Log in or Create an account to join the conversation.
9 years 4 months ago #271068
by Jerome
Jerome - Obsidev.com
HikaMarket & HikaSerial developer / HikaShop core dev team.
Replied by Jerome on topic Custom fields options not saved?
Hello,
I can see in your field configuration that you have a category selected with no name.
I think that you should fix that.
Afterwards, with checkbox fields, we generally recommend to use a number in the "value" and a text in the "title", not the opposite.
Regards,
I can see in your field configuration that you have a category selected with no name.
I think that you should fix that.
Afterwards, with checkbox fields, we generally recommend to use a number in the "value" and a text in the "title", not the opposite.
Regards,
Jerome - Obsidev.com
HikaMarket & HikaSerial developer / HikaShop core dev team.
Please Log in or Create an account to join the conversation.
9 years 3 months ago #271145
by renem
Replied by renem on topic Custom fields options not saved?
Hi Jerome,
I have assign a category tot the field and changed the value n title. Again the field is showing up in de product edit page, but the value isn't saved when i save the changes. Also this field isn't show in the frontend.
Kind regards.
I have assign a category tot the field and changed the value n title. Again the field is showing up in de product edit page, but the value isn't saved when i save the changes. Also this field isn't show in the frontend.
Kind regards.
Please Log in or Create an account to join the conversation.
9 years 3 months ago #271150
by Jerome
Jerome - Obsidev.com
HikaMarket & HikaSerial developer / HikaShop core dev team.
Replied by Jerome on topic Custom fields options not saved?
Hello,
I just saw something that I missed last time I check your screenshot.
Your custom field namekey is "tags" and unfortunately, that is an internal name used by HikaShop to handle the Joomla tags.
That namekey is not listed in the list of forbidden custom field ; but we will add a patch for the next release.
Right now, the only advice that I can give you is to delete that custom field and create a new one with a different namekey.
If you want ; you can also delete the column" tags" in your HikaShop product table because that column won't be used at all.
Regards,
I just saw something that I missed last time I check your screenshot.
Your custom field namekey is "tags" and unfortunately, that is an internal name used by HikaShop to handle the Joomla tags.
That namekey is not listed in the list of forbidden custom field ; but we will add a patch for the next release.
Right now, the only advice that I can give you is to delete that custom field and create a new one with a different namekey.
If you want ; you can also delete the column" tags" in your HikaShop product table because that column won't be used at all.
Regards,
Jerome - Obsidev.com
HikaMarket & HikaSerial developer / HikaShop core dev team.
Please Log in or Create an account to join the conversation.
- PolishedGeek
-
- Offline
- Official HikaShop Development Partner
9 years 3 months ago #271179
by PolishedGeek
~ Deb Cinkus, CEO
Polished Geek: more with monday․com
eCommerce Business Process Automation Experts
Replied by PolishedGeek on topic Custom fields options not saved?
Poking my head in on this thread because we currently use an Order Custom Field for one of our clients called "order_tags". A lot of integration work has been done around this custom tagging system for our client, including feeding the order tag values over to ShipStation.
Will the change you are making to forbid the use of a namekey of "tags" affect any custom field with the text "tags" in it, or will it restrict admins only from creating an exact match namekey of "tags"?
Will the change you are making to forbid the use of a namekey of "tags" affect any custom field with the text "tags" in it, or will it restrict admins only from creating an exact match namekey of "tags"?
~ Deb Cinkus, CEO
Polished Geek: more with monday․com
eCommerce Business Process Automation Experts
Please Log in or Create an account to join the conversation.
9 years 3 months ago - 9 years 3 months ago #271201
by renem
Replied by renem on topic Custom fields options not saved?
Hi Jerome,
It's working now thanks!
It's working now thanks!
Last edit: 9 years 3 months ago by renem.
Please Log in or Create an account to join the conversation.
9 years 3 months ago #271182
by nicolas
Replied by nicolas on topic Custom fields options not saved?
Hi,
That check will only match namekeys with the exact text "tags" so "order_tags" is fine and you won't be impacted.
That check will only match namekeys with the exact text "tags" so "order_tags" is fine and you won't be impacted.
The following user(s) said Thank You: PolishedGeek
Please Log in or Create an account to join the conversation.
Time to create page: 0.203 seconds