• Resolved tregothnan

    (@tregothnan)


    Hi,

    We use software called BPA Platform (previously known as Taskcentre) to integrate WooCommerce and Sage 200.

    We have some requirements where we need to link to additional non standard fields created by plugins. I understand in newer versions of WooCommerce any additional field name must now be prefixed with ‘Meta:’.

    The issue we’re having is that within BPA Platform you define additional WooCommerce fields using an XML schema. However the schema won’t allow the character : (as in ‘Meta: blah blah’) to be used in the field name.

    Is there a workaround that can be used in WooCommerce where the Meta: prefix isn’t needed or can be coded around to appear differently? Perhaps a code snippet that can be put into the functions file of the website?

    We’ve recently upgraded our site and WooCommerce (was previously on v2 versions), and back then additional fields didn’t have the Meta: prefix, hence how we’ve only just run into this issue with the character ‘:’.

    Many thanks in advance

Viewing 2 replies - 1 through 2 (of 2 total)
  • Phil

    (@fullysupportedphil)

    Automattic Happiness Engineer

    I would recommend contacting the developer of this integration that you are using (Taskcentre). It sounds like they need to update their integration to make sure that it’s still compatible.

    While you certainly could customize the code on your site to have to continue to work, I wouldn’t recommend it. We don’t have any code snippets in our documentation that would change the database information structure to support this third-party integration. Additionally, if the developer of that integration hasn’t kept their integration up to date to keep working, this will likely just be a band-aid fix, with other problems to come in the future.

    Instead, if that developer isn’t going to update their integration I would recommend spending your time looking for a replacment integration where the developer has kept it up to date. I haven’t checked specifically for Sage, but there are many similar cloud connection services such as Zapier.com

    Plugin Support Tseten a11n

    (@tibetanitech)

    We haven’t heard back from you in a while, so I’m going to mark this as resolved – if you have any further questions, you can start a new thread.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Meta: prefix on custom fields’ is closed to new replies.