• Resolved MMW

    (@moneymakewise)


    Hello,

    I guess we are facing the same issue that i’ve read here: https://www.ads-software.com/support/topic/fatal-error-500-site-caiu/

    In our case, we receive the Fatal Error message when we enabled Woo commerce Add To Cart Behaviour (i)Redirect to the cart page… and (ii) Enable Ajax…

    We are using Rigid Theme by Althemist.

    (I cannot copy here the exact error we received since we disabled immedialty WC ‘Add To Cart Behavior’ tick boxes hence to get rid of the error, BUT its the same error principle we’ve read in topic above.

    Could you please help us by contacting RIGID THEME author to fix the them? We have no means to contact them.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Hey?@moneymakewise,

    Thanks for writing to us about our plugin! I apologize for the delay in getting back to you. I’m sorry to hear that you are running into a conflict here. I’m happy to help out here. ??

    I’m afraid that we aren’t able to reach out to this theme author as it looks like a theme purchase is required. It looks like this theme is posted on ThemeForest and that comments are open there. I would recommend logging into your ThemeForest account and heading to the comments page where you will be able to reach the authors.

    I would recommend sending over a link to the following topic we posted on the OceanWP’s support forum as it includes the full technical details of this issue:

    https://www.ads-software.com/support/topic/incorrect-usage-of-woocommerce-filter-causing-fatal-error-with-facebook-for-wc/

    Would you please reach out to the theme authors through this system and let me know if they are able to address the issue for you?

    Thanks,

    Tamara

    Thread Starter MMW

    (@moneymakewise)

    Hello,

    Thanks for your response to our problem.
    The Theme we are using is RIGID THEME (not OceansWP). This is the theme page: https://themeforest.net/item/rigid-responsive-woocommerce-theme/20421310.

    Yes its a bought theme and we have contacted the Author and below is their response:

    Actually, your case and the one on www.ads-software.com are not related. In your case it looks like wrong facebook configuration. Unfortunately, we can’t provide help with this, as it’s not theme related. We have a lot of clients using Facebook for WooCommerce and no one ever reported such an error. May be you should consult with the plugin support team.

    Regards,
    Dimitar Koev

    Co-founder & CEO
    Althemist Ltd.
    https://althemist.com

    Now, how can we send you screen shot of the error we encountered so you can investigate whats wrong with the FB For WC plugin and help us fix it please?

    Thanks in advance for your help.

    Hey @moneymakewise,

    Thanks so much for checking that with their team. It would indeed be great if we could take a look at the exception that’s being thrown in case we need to fix something in the plugin.

    The easiest way to share a screenshot with us would be to use a service such as https://snipboard.io/. Alternatively, you can get in touch with us directly via our support form which would allow to attach the image to the email once we reply. The benefit of contacting us directly is we would be able to request credentials and other sensitive information if need be.

    Could you let me know which method you’ll use, and when you have a moment to pass on this extra information?

    Cheers!

    Simon.

    Thread Starter MMW

    (@moneymakewise)

    Hi Simon,

    Thanks, i have just filled the form at the link you gave, and ive made a reference to our discussion here.
    Could we please now speed this up. It already took a few days talking about it here and we need to fix it asap.
    I will wait for your return email so i can attach the screen shot with the error.

    Thanks
    Yiannos

    Hi Yiannos,

    Thanks for reaching out directly! Let me close this issue and we can follow up on the email thread directly.

    Cheers,

    Simon.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘FATAL ERROR: Uncaught ArgumentCoutnError’ is closed to new replies.