halfacre

Found it – there’s an option under Mega Menu > Advanced tab, unticking “Prefix Menu Item Classes.”

Thanks, Zafer. I’ve resolved the mixed content issues but am still getting 404s on these fonts and – notably – on the Smush lazy load map:

[Error] Failed to load resource: the server responded with a status of 404 () (smush-lazy-load.min.js.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 () (fa-brands-400.woff2, line 0)
[Error] Failed to load resource: the server responded with a status of 404 () (fa-brands-400.ttf, line 0)
[Error] Failed to load resource: the server responded with a status of 404 () (fa-solid-900.woff2, line 0)
[Error] Failed to load resource: the server responded with a status of 404 () (fa-solid-900.ttf, line 0)
[Error] Failed to load resource: the server responded with a status of 404 () (fontawesome-webfont.woff2, line 0)
[Error] Failed to load resource: the server responded with a status of 404 () (fontawesome-webfont.woff, line 0)
[Error] Failed to load resource: the server responded with a status of 404 () (fontawesome-webfont.ttf, line 0)
[Error] Failed to load resource: the server responded with a status of 404 () (fontawesome-webfont.svg, line 0)

Perfect, that’ll do it. Thanks for the assist.

Good call, Wayne –?thanks. Indeed, checked this sender’s original email and the image in the signature is broken there (as it is in the post, which I failed to mention), which makes me wonder if there’s a way to filter out broken images entirely.

For now I’ve activated the Support plug. It may take a bit for me to get a good snapshot of the logs, as this individual posts somewhat infrequently (though just frequently enough to keep the security consistently broken, it seems). Hopefully if I set the number of captures to ~5 or so I can catch her next post.

Thanks for the assistance and the killer plug, Wayne. I’ll be in touch once I get the necessary capture.

Thanks Wayne – went through the support plugin process as outlined. Everything seems to go as expected, but nothing is showing up in my Media Library yet. Does this take a while? It’s been about 45 minutes so far since the initial test.

I initially ran a single test, but when nothing was showing up I upped it to three and sent three more.

Emails are being sent to the address pretty regularly as it is, as alerts are actively being forwarded to the postie email address, but I figured something should show up.

Thanks again!

Ah, I see… Got it. Thanks Donncha. Is this a new feature for 1.5.2? I can’t recall for sure, but I thought in the prior version, when I had scheduled preload the button showed regardless. I could be wrong.

Sometimes I need to clear the cache and then preload it again on the spot, but still would like to keep the scheduled preload running. It’s a small thing to tick the box again (if even that’s necessary), so no big deal either way.

Thanks again!

I don’t want to cancel the preload, but I also was hoping not to wait 9 hours for the cache to preload, thus why the “preload now” button is useful.

So the button not showing up is expected behavior?

Thanks for the reply, Donncha.

Good to know, I’ve set it to Expert Mode. Made sure to update both .htaccess files just to be on the safe side. I’m guessing it didn’t help that at first I didn’t put these caching rules at the top, as the page tab states. Rectified that error as well.

Regarding the Preload tab, yes, caching is on:
https://snag.gy/UmfODp.jpg

But the Preload tab looks like this:
https://snag.gy/lFyKth.jpg

I keep looking again to see if I missed it somehow… it wouldn’t shock me at this point.

Thanks again!

Thanks for the reply, webaware. Is it necessary to set to run only as https even if it’s only needed on checkout pages? Will changing these settings affect the ability of users to reach the site via http (say, via a bookmark or from external links)? Thank you again!

Also, I put those conditional styles in the “if-not-any-version-of-IE” conditional comment. I am so embarrassed.

Okay, found the problem. You’ll notice that colon after the URL? Yeah, not supposed to be there. Jeez. Thanks, Firebug Lite.

Okay, in the codex it says not to use a custom template for a page of posts. It doesn’t say why, but clearly it’s ignored, so I guess that’s a good enough reason. So there’s no way to have a custom template on a [age of posts?

I’m not sure, but I guess it’s possible I really screwed things up somewhere along the line, because he page of posts remains the same template, even if I switch it from three to two columns (or to anything else for that matter, so for all I know it’s not reading those code snippets I added to the pageofposts.php template because it’s not actually using it (even though the pulldown idicates that it is).

@christogeretz – Thanks for the suggestions. I installed both the plugins, but I run into the same problem – I can not restrict access to the page. I mean, I can TELL it to do so, but it will not do it for the page of posts. It does work on the other non-post pages. This must still be due to a “page of posts” being considered an archive. I’m at a loss. The link esmi supplied seems to be the only one on the internet that addresses this issue, and I couldn’t get it to work. Heck, it even turns out that code on quirm.net is invalid syntax. Seemed so promising, too.

As far as plugins that require users to be logged-in (like Members Only or WordPress Access Control), “logged-in” means they need to be logged in to WordPress, which seems really counter-intuitive in practice… visitor tries to access page, is sent to a WordPress login requesting a username and password. Visitors to this site will not likely have a WP account, and there is no link there to register for WP. What’s a user to do? Does anyone else agree that this seems kinda non-user-friendly? Am I missing the forest for the trees? I *am* pretty green.

I’m not too picky… I don’t mind setting up a username if I have to. The big thing with Members Only is that it protects the whole site, rather than just a specific page (in my case, the page of posts). Am I wrong about that?