Our recent observation of … using this WordPress.org blog coming across some HTML iframe coded elements not showing always having src attributes starting with http: … which we wait for clientside means to fix for … mixed content errors that can occur … these HTML iframe element contents would often not show for the readers of the blog, and it is our theory that web browsers, within the last while, changed rules to the effect “one strike and you are out” and for us waiting for clientside means to change that “http:” to nothing (ie. get your protocol off the address bar protocol) was too late to help (avoid Mixed Content errors), and so we’re now fixing CMS WordPress blog content at the “server PHP side” in good ol’ header.php to improve the situation here at this blog … <?php if (isset($post->post_content)) { // iframe issue $ifrs=explode(‘</’ . ‘ifr’ . ‘ame’ . ‘>’, $post->post_content); $worryb=false; if (strpos($post->post_content, “</” . “ifr” . “ame>”) !== false) { $worryb=true; } for ($ichb=(-2 + sizeof($ifrs)); $ichb>=0; $ichb–) { $worryb=false; if (strpos($ifrs[$ichb], ‘<‘ . ‘ifr’ . ‘ame’ . ‘ ‘) !== false) { $bcontent=explode(‘<‘ . ‘ifr’ . ‘ame’ . ‘ ‘, $ifrs[$ichb])[-1 + sizeof(explode(‘<‘ . ‘ifr’ . ‘ame’ . ‘ ‘, $ifrs[$ichb]))]; $crlflines=explode(“src=’http:”, $bcontent); if (sizeof($crlflines) > 1) { $worryb=true; } else { $crlflines=explode(‘src=”http:’, $bcontent); if (sizeof($crlflines) > 1) { $worryb=true; } } if ($worryb && strpos($bcontent, ‘http://localhost’) === false) { $post->post_content=str_replace(‘<‘ . ‘ifr’ . ‘ame’ . ‘ ‘ . $bcontent, ‘<‘ . ‘ifr’ . ‘ame’ . ‘ ‘ . str_replace(‘http:’,”,$bcontent), $post->post_content); $ifrs=explode(‘</’ . ‘ifr’ . ‘ame’ . ‘>’, $post->post_content); } } } } ?> … to fix HTML iframe mixed content potential errors before they get presented and called, in any way, on a WordPress blog webpage. Stop Press Here we are at 12/11/2025 and realizing there is another PHP code change needed in header.php to fix this issue for more HTML iframe elements, that being … <?php if (strpos((isset($post->post_content) ? $post->post_content : ”), ‘<iframe src=”http’) !== false) { $post->post_content=str_replace(‘<iframe src=”http://www.rjmprogramming.com.au’, ‘<iframe src=”//www.rjmprogramming.com.au’, str_replace(‘<iframe src=”https://www.rjmprogramming.com.au’, ‘<iframe src=”//www.rjmprogramming.com.au’, $post->post_content)); } if (strpos((isset($post->post_content) ? $post->post_content : ”), “<hr”) !== false) { $xbitskw=explode(“>”, substr((isset($post->post_content) ? $post->post_content : ”),0,strpos((isset($post->post_content) ? $post->post_content : ”), “<hr”))); } else { $xbitskw=explode(“>”, (isset($post->post_content) ? $post->post_content : ”)); } // more of if follows } ?> … placed before in the PHP. If this was interesting you may be interested in this too.
WordPress Akismet Antispam Plugin Primer Tutorial
As we alluded to when we presented WordPress Upgrade Primer Tutorial, we use a great WordPress plugin called Akismet to … identify comment spam … place the detected spam into a Spam “folder” … and, as of recently, we’re going to see how we go, checking the Akismet plugin checkbox that reads … Silently discard the worst and most pervasive spam so I never see it … to, hopefully, lessen the “moderation load” at our end with the WordPress blog you are currently reading. We’ll see?! If this was interesting you may be interested in this too.