Eldo – Another user with the same issue reported in the Woocommerce forum that it seems to be related to the button opening a new tab/window. I’m not sure if that helps, but thought I would pass the information along in case it does. Hopefully we can get this resolved soon!
The conflict is not with a plugin – when I switch to another theme, the issue resolves. The Tower theme is conflicting with iPhones, specifically (we believe) with the Safari browser. As I explained in my original post, I already went through significant troubleshooting steps with Automattic/Woocommerce, and we determined and they confirmed that the conflict is specifically with the Tower theme.
Are you saying that Codeless can’t figure out the issue? Or that you don’t have access to an iPhone to replicate the issue? Conflicts with iPhones seems like a significant error for a theme that markets itself for e-commerce. I don’t see how building a custom checkout page will help, since the conflict (Tower theme and Safari browser) will still exist. Can you explain how/why you think that plugin will help?
Yes – I said in my previous comment that I figured out how to make the footer re-appear: I had to disable/re-enable the footer settings in WordPress and Tower, and then rebuild the footer from scratch (all the widgets had disappeared from the footer columns). So yes, the footer now appears.
I just thought it might be something you would want to look into to figure out, so it doesn’t happen to anyone else. Since it seems to be something that caused the widgets to be deleted (rather than a plugin conflict where they reappear when the plugin is disabled) it seems like a significant bug in the template.
But again, I was able to rebuild the footer so I don’t need you to try and “fix” the footer for me.
I spent time looking into this today, and discovered that my footer widgets had disappeared. I was able to rebuild the footer, and it’s now showing; however, I’m still baffled how/why it was erased.
Ludjon -I’m not sure what to tell you. My customers are experiencing issues and I’ve had to put a notice up on the website about it. Are you using an emulator, or testing with a physical iPhone? Automattic didn’t experience the issue with the emulator, but *did* experience the issue when they used an actual iPhone.
Also: are you testing on the real site or the staging site? If you’ve been testing on the staging site, can you try testing on the real site? Maybe that can help us narrow down the issue.
Finally: Are you testing on Safari? That is the one similarity between all the iPhones.
I’m not sure what else to say, except that it is definitely still happening, so we need to find a device for you to use that replicates the conflict (not assume the conflict doesn’t exist.) Thanks!
Ludjon – I’ve cleared the cache and checked on two different devices (I’m checking the /wp-staging site, which is where I’m assuming you made the changes) and the lines are still broken up even when there’s not a lot of text. Can you send me a screenshot of what it looks like when you test it (and feel it looks great), so I can make sure I’m clearly communicating?
Ludjon – I’ve been testing this on my Pixel smartphone, so it’s’ definitely a small device. I definitely cleared the cache before testing. I tried adding !important and that didn’t help.
I’ve updated/refreshed the staging site so you should be able to login with the credentials now. Thank you!
