crystalge
Forum Replies Created
-
Hi Nithin,
Thank you for your reply. Please find attached the requested export and screenshot here:
I’ve had to draft the popup for now, so that it’s not visible until this is resolved.
Looking forward to your reply!
Crystal
Hi Adam,
Further update, the limiting to USA only feature is completely broken, in that it does not work. I can set a VPN to Canada, USA, Shanghai and it will showcase this popup in all 3 locations.
Please advise how to fix this.
Hi Adam,
Thank you very much for your prompt reply! I was running some further tests after making this post, and it seems that the front page pop-up only works when the visibility rules have it noted as a static page, with no other potential static page or regular page options. This seems to be the case even when “Any” is the choice selected as opposed to “All”.
It also seems to be the case that the only certain countries field only works one time, meaning if I make two rules on the pop-up where rule#1 is only visible in the USA on the static front page, and rule#2 is only visible in the USA on the other page, the rule#1’s country limited visibility breaks. This is why the country limited visibility wasn’t working for your viewing purposes.
I had wanted this pop up to appear on the front page as well as one other page. Since it seems to be unable to handle this request, I’ll be making a second pop-up just for that page as a work around.
Thank you very much for your time and attention into this matter.
Best, Crystal
@anghelemanuel99 I’m writing again to notify you that this error continues to persist with update 2.6.9
Error still happens. I believe it’s to do with one of the following:
- Divi 4.14.7
- WooCommerce 7.0.0
- WordPress 6.3.2
This issue began with one of your updates a few months back, I typically do not update plugins/themes unless they state a security reason to do so. So with that in mind, I’d say it’s one of your updates that’s conflicting.
I’ve waited a month without a reply, so no this has not in anyway been resolved. I simply gave up on asking for help.
As I said in my last update, this happens when the WooCommerce shopping cart is set to a value of 0.
I also asked if you thought the troubleshooting area would be of use to me, to which I also received no reply. I decided not to wait and try them anyways, and I can confirm to you that the troubleshooting area did not resolve the issue.
I won’t be removing WooCommerce from my site, nor will I be removing the Divi theme, so if there isn’t a solution I guess I’ll be switching translation providers sometime in the future. Your plugin was great until one of the updates caused this issue, but it must be causing a big conflict with either woo commerce or divi if it’s still not resolved.
Hi There,
To update this issue, I can tell you now that the error string is only generated when the woo commerce shopping cart has a value of 0 Items.
Please advise.
I’ll need some time to set up a staging environment to test that, but if it helps you look into this in the meantime the theme I’m using is Divi 4.14.7.
Update: I was reading through some other support topics, would the advanced troubleshooting or debug areas be of interest to me in?
Specifically:
Troubleshooting – Filter Gettext wrapping from post content and title
Troubleshooting – Filter Gettext wrapping from post meta
Debug – Disable translation for gettext strings
I don’t have any of these selected currently.- This reply was modified 1 year ago by crystalge.