Josh Habdas

WP Cerber has a solution that covers all possible situations.

I looked at the instructions and already checked the “behind reverse proxy” option in the plug-in options. I’ve also inspected the HTTP_X_REAL_IP I get from the Cerber diagnostics and it’s 10.42.2.2 which is the same as the REMOTE_ADDR and that’s incorrect as that’s internal DNS stuff and not the actual IP address of my connecting client. In my case I’m not using a CDN at the moment. I’m running Cerber inside a Kubernetes cluster. What should I try next?

Now, I guess that someone more geeky could fork the repository and continue the good work. Anyone?

Here’s a fork. Feel free to sign-in with GitHub and maintain it. I have no intention of submitting it back to WordPress. But now that the code is there it’s possible to zip it up and use it in your own WordPress installation.

https://code.habd.as/comfusion/advanced-gutenberg-blocks

Nur, I’m not sure why plug-in support suggested you should disable a core feature so their plug-in works. I can assure you you almost certainly do not want to do that. Instead, you want to make sure the native lazy-loading added in WordPress 5.5 is working as best you can which means adding a width and height to the images on your site. I’m not certain but I believe Force Regenerate Thumbnails may help you accomplish the addition of the width and height. Keep in mind browser support for native lazy-loading still isn’t perfect. Right now if you’re primary users are on iOS using Safari, for example, native lazy-loading still doesn’t work so you’re going to need to figure out a way to find a solid middle ground with any lazy-loading plug-in that you do use. With a good plug-in we can expect the plug-in authors will balance things out to provide the best experience.

• This reply was modified 3 years, 10 months ago by Josh Habdas.

No problem. Thanks to both of you. This is being used with Septera, so I wanted to ensure it was keeping up to date. Septera is AMAZEBALLS. And so are you guys. Cheers.

Many thanks, Pascale! Very happy to have this plugin and thanks for incorporating the feedback and suggestions and implementing this great new feature.

Took a quick look at the update and feedback would be to remove any spaces from the comment to disable for parity with SpeedSense. Other than that looking forward to seeing this update pushed up to wp.org so I can drop it into my pages! Cheers to you good sir!

Sorry, Jim. Invested more time than I could afford. If and when I come back to this I have a great source for continuing the investigation. Marked as resolved. Cheers.

I’m a bit more confused now, actually. Perhaps this is more of a Google thing—I’m not sure. But giving the following user flows:

Landing page 1 > Landing page 2
Landing page 1 > About page
Landing page 2 > Contact page

I desire some control to prevent the second two scenarios which may have conversion goals associated with them from popping an ad. Kinda like you wouldn’t display ads on a Privacy Policy or Terms of Use page, you know?

Perhaps this is more of a Google thing than anything else —?I imagine I’m not the first person who’s wanted this and it seems like something they should somehow manage in AdSense through a white or blacklist.

I don’t know. Either way thanks for your help. Very happy to have my page-level vignettes displaying even if it’s not perfect.

The Site Title and Tagline can be disabled from Customizing ? Site Identity
Site Identity. Beyond that I’m not sure how to get the custom logo in. Did you look on the Septera How To forum on the Cryout Creations website?

Thanks, man. I’m give it a try soon. Never really understood how the page-level ads popped up –?I always thought it was probably on an unload event. But if not the comment approach should work great!

Been using this for a while now without issue and it’s working excellently and my eCPM is up over 500%. Wooooooo. Back up to 5 stars. This thing is awesome.

Hi @pascalebeier! Thanks for your response. In my case I’m thinking of hiding the page-level ads when users transition to pages like the contact page, or the about page. Seems like they’d get annoyed if a full-screen takeover popped when I was trying to send them down a conversion funnel towards some end goal.

Would it be more extensible to do something like Speed Sense does and create a little comment snippet like <!–OffDef–> or whatever to prevent it? Not sure exactly how AdSense makes its determinations and how much flexibility it offers — just don’t want to bite off my nose to spite my face when advancing users towards a specific goal.

Here’s the site I’m working with. It uses Pods. I basically only want page-level ads on certain custom pods post types (e.g. Gangs, Hoods), and to disable them everywhere else kinda a whitelist type thing if that helps at all with the use case: https://chicagoganghistory.com.

Thanks for the plug-in and your help. So far it’s working great!

Closing this since it’s not Septera-specific, but a general issue with many WordPress themes as of late using external fonts from Google which do not work well worldwide. These fonts should be included in themes and not rely on a third party so they can be served from their own CDNs.

@mickeseise, such a general quesiton without screenshots is unlikely to result in a valuable answer. Could you provide more information and share what you’ve already tried including screenshots? Thanks!

Here’s the last site I built with Septera to give you some ideas of what it can do: https://chicagoganghistory.com

Septera is built using a framework Cryout is creating. You can also find a How To section on their website specifically for Septera. IMO it’s better not to create documentation so they can focus on improving themes.

That said, there’s the FAQs and DOC:
https://www.cryoutcreations.eu/documentation