• Resolved burgerino

    (@burgerino)


    Hi, thanks for the new product editor. It seems promising. I noticed that it does not recognise my already created custom fields when I was testing it. It looks as if some of my custom fields start with the underscore “_”. Such as “Meta: _retailprice”. I was wondering if you might accommodate this detail in the future or if I should reupload all custom fields. If so, could you let me know the best way to do it?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support ckadenge (woo-hc)

    (@ckadenge)

    Hi @burgerino,

    Thank you for reaching out.

    Could you please confirm that you followed the correct steps when adding your custom field, as described here and here?

    Thread Starter burgerino

    (@burgerino)

    thanks for the response. I can confirm that when I use these steps, custom fields work. Howecer, I have custom fields that were created before the new editor. I would like that they would reappear. However, most of my names for custom fields start with the “_”. Because of that the new editor does not recognize the custom fields. I think other plugins like Yoast also create custom fields starting with “_”

    Plugin Support Shameem R. a11n

    (@shameemreza)

    Hi @burgerino

    Currently, the new product editor does not display custom fields that start with an underscore “_”. This is because fields starting with an underscore are considered private and are not typically displayed in the editor.

    However, we understand your concern and the need for compatibility with other plugins. It would be great to have you add your ideas as a feature request, which is where developers go to look for future plugin features and improvements.

    In the meantime, if you need to use these custom fields, you may consider renaming or recreating them without the underscore.

    Thank you for your patience and understanding. If you have any other questions or concerns, feel free to ask.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.