Karen

Glad you were able to adjust the modifiers through the API! I’m not sure if there will be a dashboard announcement when the change is live in your store, but if you’re in the control panel frequently, you’ll definitely see it ??

For adjusting the WP product template, this customization guide is a good place to start:
https://developer.bigcommerce.com/bigcommerce-for-wordpress/extending-the-plugin/customization-guide

If you have any questions beyond that, let’s start a new thread. Thanks!

Thanks, @scottxtensive ! We really appreciate this feedback. We look forward to iterating on the Ajax add to cart feature in future releases.

Hi there,

Apologies for the late response. Checkboxes and text fields are commonly modifiers (meaning they aren’t used to build out SKUs), so it looks like both are being created correctly as modifiers through the control panel. Dropdowns on the other hand can be a modifier type, but are more often associated with variant options (used to build out SKUs)–I think that’s why your dropdown choices aren’t coming over. The system thinks they should be variant options because of the display type, and variant options need to be associated with SKUs to import to WP.

We have a couple of options:

• Soon, we’ll be rolling out a new BigCommerce UI for creating products that will make it much easier to control whether product choices are variants or modifiers. If you’re able to wait for this update, this should resolve the issue. I don’t have an exact ETA for when the new UI will be available across all stores, but it should be soon.
• For now, a developer could use the v3 API to create the product with the correct configuration of variants and modifiers. Links to documentation here:
  https://developer.bigcommerce.com/api-reference/catalog/catalog-api/products/createproduct
  https://developer.bigcommerce.com/api-reference/catalog/catalog-api/product-modifiers/createmodifier
  https://developer.bigcommerce.com/api-reference/catalog/catalog-api/product-variants/createvariant

Glad to help! The developer documentation you’ve linked is the correct article–remaking the options as modifiers through the API would definitely work although I understand that may not be an option for you.

We may be able to convert the options through the UI though. It’s possible that remaking the product would cause it to save the choices as modifiers. Could we have you try recreating the options/option set/product to see if it comes through intact on WordPress?

Hey @medcline,
Thanks for giving the plugin a try! It’s correct that the plugin is designed to bring over product data on the SKU level, but the plugin also supports an option type that isn’t used to build out SKUs (called modifiers). Modifiers are any choices that are attached to a product that don’t affect the way the physical product is stocked in the warehouse. So for example, Size would be an option associated with a SKU (or variant), but something like Primary Reason for Purchase would be considered a modifier.

It looks like the Primary Reason for Purchase and How you heard about Medcline choices are being recognized as variant options (the kind used to build out SKUs) rather than modifier options, the way they should be.

If you don’t have SKUs built for the size options already, could we have you try creating them in your BigCommerce store? This would be worth a try to refresh the data in our system get the Reason for Purchase and How you Heard about us options converted to modifiers.

Hi Kashif, we haven’t seen this vulnerability on any of the test sites we’ve scanned, but our Security team can check it out if you can provide the WordPress site URL.

If you’d prefer to work one-on-one with a support agent, 24/7 tech support is included with BigCommerce through phone, chat, or email.

Hi Kashif, We haven’t seen this vulnerability on any of our test sites that we’ve scanned, but we can have our Security team check it out if you can provide the WordPress site URL.

If you’d prefer to work one-on-one with a support agent, we also have 24/7 phone, chat and email support.

• This reply was modified 6 years, 2 months ago by Karen.

Hey Adonya, it looks like you may have already switched back but I wanted to follow up here. We’ll take it as an action item to reach out to the Divi team to see what we need to do to make the plugin compatible. In the meantime, we’d welcome any other feedback!

Hey there, it’s difficult to say what the issue might be without access to your store. Could you open a support case so our tech support team can take a look? You can open a support case via phone, email or chat through https://support.bigcommerce.com/s/

What version of PHP are you using? You’ll need to be sure that you’re on at lease 5.6+