mouli a11n

Backup files can be deleted under the backups menu.
Closing as solved

I understand that you are setting up the Unsubscribe Confirmation and and Success pages using the [mailpoet_page] shortcode.

However, looking at your link it appears that the shortcode is not getting parsed and is showing as plain text.

Please can you confirm that you are using a custom page for these pages and that you have set these pages as appropriate under Mailpoet ? Settings ? Basics ? Unsubscribe page.

The custom page needs to be selected from the dropdown.

Thank you for confirming that 4.34 fixed the issue ??

Of course we try really hard to avoid this kind of scenario and we test a lot before releasing a new version but sometimes issues are not picked up prior to release. In these cases the community is really good at informing us so we can fix it in a timely manner so we thank you for your patience.
While we obviously cannot promise that this will not happen again, we do try hard to make it very infrequent and we move to fix it fast.

@postudiio

I see from your site that you appear to have managed to add the MailPoet sign up form to the bottom of the page content using an Elementor section, and that you have a second form placed below the content using the MailPoet settings that appears to have it’s width set to 100%.

Have you tried adjusting the form width in the form settings:

Link to image: https://d.pr/i/o8ocCN

That should center it and restrict the width.

@bignevola

I checked the bug report and it appears that a fix has been developed and is currently in testing prior to a release so watch out for an update.

Note that these deprecation messages are PHP Warnings and are not critical for the current functionality of your site. They are aimed at developers to improve the code and ensure compatibility with the latest version of PHP.

You can safely disable these warnings as described here:
https://www.wpbeginner.com/wp-tutorials/how-to-turn-off-php-errors-in-wordpress/
or you can ask your host to disable them on your account.

@costasergio

Apologies for the confusion here.
It appears that my colleague was indeed referring to a separate report.

I tried replicating the issue you describe above on my staging site and could not do so.

If I exclude the post code I get the error as you describe, however when I add the post code there is an AJAX call that refreshes the shipping rates which are returned correctly.

This leads me to suspect that this is an issue caused by something on your site, most likely a conflict, so I suggest that you try the following test.

Conflict test

You can read more about plugin and theme conflicts here:
https://woocommerce.com/document/how-to-test-for-conflicts/

The best way to determine if the issue is being caused by a theme and/or plugin is to do the following:

1. Temporarily switch your theme back to the Storefront (https://www.woocommerce.com/storefront/) or TwentyNineteen (https://www.ads-software.com/themes/twentynineteen/) Theme.
2. Disable all plugins except for WooCommerce and a simple flat rate shipping method.
3. Test to see if the issue has been resolved.

If that resolves the issue, then one-by-one you can switch back your theme and re-enable your plugins, testing in between, until you find the one causing the conflict.

If doing this on your live site is not possible, can you create a duplicate site? We suggest using WP Staging (https://www.ads-software.com/plugins/wp-staging/) if your hosting provider does not offer a staging server as an option.

I hope that helps you to figure it out.
Feel free to get back to us if you have further questions.

@nothin7
The repo is Private so you won’t have access to the bug report itself.

My suggestion of you opening a support request on WooCommerce.com and referencing the report by URL was that we can then add the ticket number to the report and you will be informed of updates. Apologies that I didn’t explain that better.

@nothin7
The developers have opened a bug report regarding this issue so thank you for bringing it to our attention.

If you want to get updates I suggest that you open a support ticket on WooCommerce.com and reference the following report:
https://github.com/woocommerce/woocommerce-gateway-paypal-powered-by-braintree/issues/492

@nothin7

Many thanks for bringing this to our attention.
I will pass your comments on to the developers and will update this thread with their response.

@radicalwebs

Accounts are sometimes restricted after being initially set up due to missing information and documentation.

You can check the information associated with your acccount by going to Payments ? Settings ? Deposits ? Manage in Stripe.

If that doesn’t clarify the issue I suggest that you open a support ticket with WooCommerce.com support and include your System Status Report which will give us enough information to access your account and identify the exact reason it is flagged for restriction soon.

@megankay

Nice work!

I will close this thread as solved for now, but if you ever need further assistance, feel free to get back to us.

@minsuwai
Interesting question however I am not a developer so I’m not the best person to help you. Hopefully someone with more coding experience can offer some help.

From what I see it looks like if the product is a variable product it simply runs that woocommerce_variable_add_to_cart(); function which would simply add it to the cart. This is where I suggest you start looking for the reason it isn’t allowing multiples to be added.

I hope that helps you to figure it out.
Feel free to get back to us if you have further questions.

@bavya
I have just answered your support request in our internal system but I thought it may be useful to copy it here to make it more visible.

Logs

Web hook activity is logged under  WooCommerce ? Status ? Logs. 

Look for logs with webhook-delivery-YYYY-MM-DD in the title.

These should confirm that the webhooks are being sent correctly, and the response received.

Webhook test service

You can also use a service such as https://webhook.site to test the receipt of a test webhook triggered by the same action as your main webhook.

The site gives you a unique delivery address that you use to set up the test webhook. You then perform the order action that triggers the webhook and the site receives it and displays the content etc.

These two methods will confirm whether WooCommerce is sending the webhooks correctly.

If they are but are not being received by your API there maybe a firewall, or similar security feature, blocking receipt of them on your server. I have seen this happen with Mod_Sec for instance, so you may need to white list the IP address and/or URL of your test store.

@rehanmohd409

Many thanks for the clarification. WooCommerce is set up by default to only use a single checkout page, this being defined in the Advanced settings ( WooCommerce ? Settings ? Advanced. I searched for plugins that might do the job but found none, so it is likely to require custom coding to achieve what you describe.

For example you might get close by setting up conditional fields that depend on the products in the cart as described in this article:
https://remicorson.com/customise-woocommerce-checkout-fields-based-on-products-in-cart/

Note that the above is a couple of years old and I have not tried it myself so treat it as inspiration rather then a solution.

Maybe if you gave us a bit more detail about what you are trying to achieve, and why, we can get closer to a solution.

@narmeen1it
Shortcodes available in WooCommerce are listed here:
https://woocommerce.com/document/woocommerce-shortcodes/
and I see no mention of the shortcodes you suggest.
I’d be interested to learn about them though so any information would be appreciated as I can see that they could be useful.
Perhaps they are generated by a plugin?