SH
Forum Replies Created
-
Forum: Themes and Templates
In reply to: [OceanWP] Theme Panel Changes: “Skip to Content”Works perfectly now, thank you!
Forum: Themes and Templates
In reply to: [OceanWP] Simple Line Icons Load Time IssueSame Problem. Fixing the problem would be nice.
Hi!, Thank you for catching up. I designed it from start, and this script is now not showing. I think, though I did not used pre-designed contetn, I watched it how it would look like, before I deleted it. Could be that this AD-script, once loaded, sticks, without the chance to remove it without going directly into the code.
But now, with the re.design without loading pre-desing content, no AD.
Thank you! (Great design!)
No, not possible to give you access at the moment. In the backend (with the gutenberg) there is nothing to see. This is the code of the section on the live-site:
<img alt="" src="https://raw.githubusercontent.com/wpxpo/ultp-api/master/layouts/ads/ads10.png" />
But I had to remove the site, because I cannot leave it online with the ad.
I will give it another try and re-design it from start. but if the problem remains, I have to find another solution. With adblocker, you see a broken image tumbnail, without adblocker you see the image (code above). than you anyways.
- This reply was modified 4 years, 10 months ago by SH.
I even did remove this section under which it was showing, but it is still there.
Thanks for the reply. It is exactly this demo ad, but I did not import a demo layout, I started fresh and made my own. So I can not find a way to delet it. It does not show as a section in the backend.
Hi, thanks for catching up.
it is exactly this red ultimate post Ad which also shows in a sreenshot at your plug-in page. It do not show when creating the side in the backend with you plug-in, but do appear when the side is online.
Forum: Plugins
In reply to: [Nimble Page Builder] New behavior since 2.0.0 release for NimbleI must confirm the problem. I did everything, but the pictures in the post-grid module will not display. I thought the latest update would fix that, but didn’t. I had to roll-back to 1.10.12, which is working fine.