Viewing 1 replies (of 1 total)
  • Hello @webgardengeek,

    Thank you for reaching out to us.

    That doesn’t work due to how WCK stores data. Basically, in the backend you manage a serialized array that after that same it then saves information in non-serialized post meta, with what you’re working with. So if you modify just the non-serialized post meta, WCK doesn’t take those changes into account. Basically it’s double saving the information. It’s bad from a programming p.o.v. but it’s due to the fact that adding support for non-serialized post meta was more important then this inconsistency.
    You can still make changes as long as you make them in both the serialized and non-serialized post meta.

    Kind regards,

Viewing 1 replies (of 1 total)

The topic ‘Custom Meta Fields’ is closed to new replies.