Hi @wordpressuser0012,
I tested this shortcode on my end but the error doesn’t go outside of the popup, it could use some styling adjustments but it does show in the proper place from what I can see, this is how it looks on my end:
https://monosnap.com/file/6WdU1NA8WuAor38541kpWSCFi92byv
Could you try testing with default WP theme and see if it could be theme related?
If the issue is still there with default theme it could be about something specific in your popup settings so in that case could you go to Hustle > Popups and click on the gear icon next to your popup to export it.
Upload the export file to any file sharing service like GDrive or Dropbox and share the download link here so we can check it further on our end.
Cheers,
Predrag
Changing the theme to a default one had changed nothing though.
After your comment i have come with an idea. i had this pop up duplicated to another page with different condition. So i went to test it out. The error message appeared as expected.
Could this have to do something with woocommerce pages?
Here are both pop ups.
https://drive.google.com/drive/folders/1rTgqVnowb_E41u0yOQoREnP5SbF_sbwi?usp=sharing
Please request an access to accept it.
Thank you
Hi @wordpressuser0012
It seems the Google drive is protected.
But I tested this on my end, I was able to replicate the issue the Woo pages.
The Woocommerce uses some hooks to trigger the errors, and it seems it is the problem here.
A workaround is using an extra plugin like https://ww.wp.xz.cn/plugins/popup-notices-for-woocommerce/ which creates a new PopUp for the error.
https://monosnap.com/file/3rQsiZFeDmJZaKE0WOBw9fvLsIqMsU
Best Regards
Patrick Freitas
Well the plugin seems to be a solution. But this one will be fixed? in order not to use an external plugin to do the job?
Thanks in advance.
Hi @wordpressuser0012,
I have forwarded this to our Plugin Team, so they can check this and consider what the possible adjustments would be needed(if applicable) to avoid this behavior with Woo pages.
Best,
Jonathan S
Hello @wordpressuser0012 ,
I want to confirm that this is reported as a bug in our system and our developers will be taking care if it.
However, at the moment there is no ETA.
kind regards,
Kasia