Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor yikesitskevin

    (@yikesitskevin)

    Hi Alex,

    Sorry we missed your ticket. It was not intentional!

    Can you try renaming one of your meta fields so they have underscores instead of dashes in the field names? (Rename the field via our plugin, not the actual Toolset field name). For example, change wpcf-duration to wpcf_duration.

    The plugin was not setup to handle dashes in field names and we haven’t gotten around to updating that.

    Let me know if that’s the issue. If it is, we’ll bump the priority on allowing dashes in field names.

    Thank you & apologies again for the delay,
    Kevin.

    Thread Starter avanlaningham

    (@avanlaningham)

    Hello Kevin luckily I have not been working on this and your response came just in time before I started some development on this and that worked perfectly.

    Plugin Contributor yikesitskevin

    (@yikesitskevin)

    Oh, great! When you say that it worked perfectly, do you mean using the underscores worked perfectly?

    Thread Starter avanlaningham

    (@avanlaningham)

    Yes underscores completely fixed the problem. Thanks again. I just submitted this on Toolset types site as well.

    Plugin Contributor yikesitskevin

    (@yikesitskevin)

    Okay great. I’d like to update the plugin so dashes are allowed but at least you have a feasible work-around for now.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Custom Properties not working’ is closed to new replies.