Simon

Hey there!

Thank you for contacting us about our WooCommerce Customizer plugin. I’m happy to help!

I gave this a quick go on my local test site and both options seem to be working okay so far, so I’d love to take a closer look at what might be going on here. Can you confirm for me that you’ve set new values for both options in the settings page at WooCommerce > Settings > Customizer?

IF so, would it be possible to let me know what you’re using so I can use those in my local testing, and would it also be possible to share a screenshot or URL of the pages that are working, and an example of a simple product that isn’t?

Cheers!

Simon.

Hey @lands23!

Thanks for getting back to us. The best place to start with your custom snippet would be to add a shortcode that receives a product_id or retrieves the post/product_id of the page it’s used on.

This is because our custom tab data is stored as product metadata, so you will need to grab the produce first. The meta key in question is then: “frs_woo_product_tabs” and this will contain an array with ‘title‘, ‘id‘, and ‘content‘ values.

Hopefully this puts you on the right track to being to integrate into Elementor! If you need further assistance with the custom development, I’d be happy to recommend some developers experienced with WooCommerce, just let me know.

Is there anything else I can help out with today?

Cheers,

Simon.

Hey @des79,

Fantastic work! Thanks so much for raising this issue to us, and solving it in one go!

You are right, it looks like with our latest release when we upgraded the Braintree SDK, we did not update the paymentMethods() function which was changed to be accessed as an attribute in the new SDK versions.

I’ve gone ahead and raised this as an issue for our developers who will look to get a fix out as soon as possible.

Thanks so much again for taking the time to report this to us, it’s very much appreciated! Is there anything else I can help out with in the meantime?

Cheers,

Simon.

Hey @keithhill1968,

Great stuff! Thanks for keeping me in the loop. If there’s anything else I can help with, or if they have any suggestions for us, please don’t hesitate to reach out!

Cheers,

Simon.

Hey @keithhill1968,

Thanks for confirming! Even without Apple Pay enabled, these functions would still be run by our plugin, as they check to see if Apple Pay should be added as an available gateway (in case it was enabled!).

Thanks for confirming you are running AfterPay on your site and that it was recently updated. I would recommend reaching out to their support team and sharing the stack trace you’ve shared with us. Hopefully, they’ll be able to add some preventative code to stop the error from being logged!

I’m sorry I can’t help directly, though I hope this was useful nonetheless. Is there anything else I can help out with today?

Cheers!

Simon.

Hi @keithhill1968,

Thanks for reaching out and thanks so much for sharing that log snippet, that’s very useful!

It looks like our Braintree Gateway is checking if Apple Pay should be initiated on ‘init’, which eventually works it’s way through the code to the External_Checkout code. Here it’s confirming what payment gateways are available by calling ‘woocommerce_available_payment_gateways‘ which the WC_Gateway_Afterpay then seems to jump onto.

Here, the Afterpay gateway looks to be calling the get_cart() function which is generating the error.

To confirm I’m reading this correctly, can you let me know if you’re also running the Afterpay gateway on your site? If so, has this only occurred since upgrading either Braintree or have you also upgraded Afterpay recently too?

Cheers!

Simon.

Hey @casalepress,

Apologies! I’m not sure what happened to the snippet, I’ve managed to duplicate the functionality, however, and am happy to share this with you.

As mentioned above, please make sure you understand how to add the snippets to your site (I personally like Code Snippets too!) and then you should be able to use: https://gist.github.com/199c785b5ef93c5091b7163aa9117a15#file-sv_braintree_credit_card_adjust_font_size_for_inputs-php

Could you give that a go and let me know if it does the trick?

Cheers!

Simon.

Hey @oxhey,

It has been a while since we heard from you, so I’m going to mark this topic as resolved.

If you’re still experiencing issues please take a look at our documentation for more information and create a new thread if you have further questions.

Thanks,
Simon.

Hey @develooperr,

It has been a long time since we heard from you, so I’m going to mark this topic as resolved.

If you’re still experiencing issues please take a look at our documentation for more information and create a new thread if you have further questions.

Cheers,

Simon

Hey @wordpressdharma, thanks for coming back to us!

The Braintree Vault is a way for customers to store their credit card information against their user profile within your WooCommerce store.

For security reasons, we don’t want to actually store the raw card details in your database, so we use the libraries provided by Braintree to request the card to be stored in their Vault. Braintree then passes back a unique token for the customer that we can store, and then use for future payments. This process of storing the card and receiving back just a token is called tokenization – and a lot of other payment gateways support this feature too!

It does mean that customers can then use the card again without having to input their full card details. I’m not sure where your previous comment came from (was it from technical support?) or if this is what you are seeing on your store, but certainly, I wouldn’t expect customers to only be able to use their card once if it is Vaulted. That’s the opposite of the functionality of the Vault!

Unfortunately, the error message you’ve mentioned in your original post is a generic error message provided by WooCommerce when something goes wrong. This could be anything from incorrect credentials, to incorrect account configuration, or even a general decline from Braintree. We would need the log file that Pit mentioned previously to be able to look into this further for you.

Would it be possible to run through another test and provide us the file for further investigation?

Cheers!

Simon.

Hey @preiffer,

It has been a while since we heard from you, so I’m going to mark this topic as resolved. I hope you were able to reach out to us directly and receive assistance!

If you’re still experiencing issues or have further questions, please create a new thread.

Thanks,
Simon.

Thanks so much for checking that @preiffer.

I’m still having trouble replicating this locally, so it would be great if I could take a closer look at the error on your site. Please could you raise a support request via our support form, so that we could investigate this more closely?

It would also be great if you could confirm that no new SKU is being generated when the error message is shown, is that right?

Cheers!

Simon.

Hey @preiffer,

Thanks for reaching out to us about this notice! Our plugin contains some version checking to make sure that it’s always running on the last two major versions of WooCommerce, or it will display the notice you’ve mentioned to suggest an upgrade. That shouldn’t, however, have an effect on the actual running of the plugin unless there were breaking changes in a latest release.

I’m running the latest version (2.4.5) of SKU Generator, and WooCommerce 4.7.1 on my test site okay and don’t see any issue generating product SKU’s or the error notice. It’s certainly strange you’re seeing this after the WooCommerce update!

Could you please confirm for me that you’re running the latest version of product sku generator too, and if you have a moment, do you still see the same error when updating WooCommerce to 4.7.1?

Cheers!

Simon.

Hey @anasiqbalkhan,

Thanks so much for taking the time to leave a review, we greatly appreciate it! I’m also so glad to hear that the plugin was a good fit for your store and that it worked as you’d hoped. That’s great stuff ??

I hope we can continue to add new features and improvements for you in the future!

Cheers,

Simon.

Hey @delibob,

Thanks for taking the time to leave us a review, we really appreciate it! I’m sorry that the plugin didn’t meet the expectations we set this time around.

I’d love to take some feedback for our product team so we can continue working on improving the connection to your Facebook catalog. Did you reach out to the support team for support during your connection attempts? I could take a look at that topic and see if I had any suggestions, or gather feedback on the problems encountered if so.

No worries if you have moved on now and no longer require the plugin. I hope that we can continue work on the plugin and perhaps you can give us a try again in the future!

Thanks again for your time.

Cheers,

Simon.