I have the impression that the Notice element doesn’t work on the Woocommerce checkout page.
There is always the notice: woocommerce-NoticeGroup woocommerce-NoticeGroup-checkout, which is located at the very top of the template (cannot be modified).
Unfortunately, this notice was created by WooCommerce checkout.js Script whenever there is an error while checkout submission. It always add a new div inside the checkout form.
1.Having the same issue with the checkout page specifically.
When there are no notices the div still exists (on checkout page). I’ve tried adding conditions but there are none that exist for this, unless I’m mistaken?
I’m experiencing the same issue with the checkout page.
I have the Bricks WooCommerce “Notice” element enabled in the settings and added the notice element to the templates. It seems to work fine on the cart page but does not work on the checkout page.
Thanks for the feedback.
Please be rest assured as we already found a way to overwrite this native WooCommerce behavior when using the Bricks Woo Notice element.
However, I am not able to confirm it will be included in which release yet.
Thanks for your time and support Bricks.
Hi Jenn,
Thank you for the last update! The error notices are displayed in the right place now.
Unfortunately the coupon code element is still at the top of the page. Is there a way to change the position of this aswell?
Thank you very much!
Kind regards,
Simone
Hi Jolia,
I did not add an element for the coupon code. It just appears on the page. It is in a div with the class .before-checkout, so I guess it gets added dynamically.
If logged out the “returning customers” box also appears.
I think it was the ‘Have a coupon?’ bar that was making me think the notices were not appearing in the correct place. Shouldn’t ‘Have a coupon?’ be with the notices? If not, how do we set the position of the '‘Have a coupon?’ notification?
Hello! This issue significantly impacts the checkout process, making it visually unappealing and unresponsive. I attempted to resolve it using CSS, but it seems that JavaScript elements are involved, which are beyond my current understanding.
Could you please share if there are any planned updates in the upcoming patches to address this?
Hi Mario,
As already mentioned: the original problem with this report was already solved in Bricks 1.8.4.
The coupon/returning customer “notice” is something completely different and there is no separate report for it yet, which is why the topic has unfortunately gone somewhat unnoticed. However, I have addressed it again within the team so that we have it on the radar.
I apologize for not being more specific earlier. My concern is regarding the lack of styling options for the coupon/returning customer notice. This limitation is causing significant difficulties, as it disrupts the overall design and flow of the checkout process.
I appreciate you discussing this issue with the team.