Big Bagel

SQL is the language, MySQL is the specific SQL database. Unless you’re running on a VPS or dedicated server where you get to do/install whatever you want, you’re probably using MySQL.

To list all your authors, it’s probably easier to use wp_list_authors unless you’re looking to do something beyond that.

Function Reference/wp list authors

Bumping is frowned upon…especially after only 10 minutes.

I can’t access your site. Looks like a DNS issue.

https://www.intodns.com/ryanmwhite.co.uk
https://www.dnssy.com/report.php?q=ryanmwhite.co.uk

Awesome sauce. ??

Right now, Feedburner isn’t showing anything except a blank page for my main feed, it is also failing to be read by any feed reader at the moment as I can see, and the comment feed is not showing the proper page for Feedburner, only a list of data.

That’s weird. It was working 15 minutes ago.

One problem with trying to troubleshoot the feed is that FeedBurning automatically pings your feed only every 30 minutes. If you temporarily disabled the redirect on your site’s actual feed, you can check for changes in real-time.

@rev. Voodoo:

From what I can tell, all it does is back-up the original wp-blog-header.php then replace it with it’s own version. It may have run through every file in the past though. For version 3.0 it has this changelog item:

2010-09-19 release v3.0, need not to modify error in php files directly, it will use a good and simple way, it just modify wp-blog-header.php in blog directory.

Was the original error before adding ob_clean(); the same as the one now?

This feed does not validate.
line 1, column 1: Blank line before XML declaration

Like it says in that trac issue, this is caused by a plugin or theme. The best thing to do would be to disable your plugins then, if the problem clears up, reactivate them one by one until you narrow down which one is causing the problem. If it’s not a plugin, you can then check the theme by temporarily switching over the Twenty Eleven.

If adding ob_clean; works for you, there’s nothing saying you can’t use it. Just be aware that future updates can/will overwrite your change and that the underlying problem in one of your plugins or your theme still exists.

The text/html issue is actually fairly minor. While it’s best to try and find out what’s causing that specific problem, it won’t keep your feed from working or validating. Actually, even the whitespace problem, while it does prevent validation, is such a common problem that most feed readers will overlook it. For example, FeedBurner doesn’t seem to have an issue with your feed as it’s still properly updating.

You can certainly try that plugin. However, looking at the code of it, all it seems to do is replace wp-blog-header.php with it’s own version. And the only difference between its version and the core version is the addition of ob_start(); and ob_end_clean();. The code is also a bit funky in places. For example, it doesn’t use nonces for the form on its admin page. Also, like with your current solution, the underlying cause of the problem would still exist.

Okay, they seem to work but occasionally stop working – I cannot recognize the reason for this.

Are you doing anything at all that might affect it? It could be that the issue is in a part of a plugin’s code that only runs under certain circumstances.

No, your permissions are fine.

I was going to suggest something but, after reloading your site, it looks like you’ve fixed whatever was causing the problem. ??

@swansonphotos:

As I pointed out in my last post, the image code was not being output correctly. The code I posted is an exact copy from the site’s source.

@swansonphotos:

What? I don’t know what you’re saying.

The OP’s problem is that something is adding an extra bit of whitespace to the top of the RSS which causes validation failure. The OP is using the W3C feed validator which is the appropriate validator when checking an RSS feed. The errors shown just say that there is a blank space above the opening <?xml... declaration (the main issue) and that the media type was incorrectly set to text/html (a secondary issue that wouldn’t cause validation failure).

If you’re referring to my second link, that was for peapodgrrl (as I indicated) who was looking for a way to show RSS feeds in Chrome. The link contains a list of several Chrome extensions that do just that.

That extra space at the beginning of your feed seems to be the only problem. Was that the same problem you were having before you edited those two core files? I doubt the problem is directly related to any core code. It’s most likely a plugin or your theme doing something silly.

My suggestion would be to first replace those two files you edited with fresh copies. Then disable all your plugins and switch to the default theme (Twenty Eleven) and see if the problem clears. It might also be good to temporarily disable the redirect to FeedBurner so we can see the actual feed.

W3C has a help page that relates to this exact thing:

https://validator.w3.org/feed/docs/error/WPBlankLine.html

@swansonphotos:

XML-RPC doesn’t really have anything to do with this. The validator being used is for RSS feeds (not HTML) which is appropriate.

@peapodgrrl:

This may be useful:

https://maketecheasier.com/12-google-chrome-extensions-for-the-rss-addicted/2010/02/03

It appears that something is filtering the HTML for the images. Here’s the current code for one of them:

<img alt="See more about the sponsor"<br />
title=& #8221;ELITE CHI& #8221;<br />
src=& #8221;https://www.chicagonyeball.com/wp-content/uploads/sponsors_img/965a31f8e5a4a8d3bfbcee420cb3e096.png& #8221; />

Unfortunately, I’m not familiar with the plugin. How are these created? Through shortcodes? A custom plugin page?

It may be best to ask the plugin author directly. You can add “wp-sponsor-flip-wall” to this topic’s tags if you want it to show on the plugin’s repository page.

Edit:

Just to note, I added a space in each instance of the HTML code for quotation marks (& #8221;) in order to show it as it actually exists in the source code.

If this is your exact code, then your parentheses are a bit off and you either need to echo your HTML <script> tags or break out of/into PHP. Also, if you’re going to use brackets, you shouldn’t use endif;.

Here’s an example that should work (didn’t actually test it of course):

<?php if ( is_page( 3 ) ) { ?>
    <script type="text/javascript" charset="utf-8" src="<?php bloginfo( 'template_directory' ); ?>/script1.js"></script>
<?php } elseif ( is_page( 18 ) ) { ?>
    <script type="text/javascript" charset="utf-8" src="<?php bloginfo( 'template_directory' ); ?>/script18.js"></script>
<?php } ?>

Yup, everything’s nice and propagated now. ??

Your theme’s style sheet adds borders for all images. Do you want to remove the border for just the one image or for all of them? Perhaps just the ones that aren’t links?

Here’s a bit of CSS that would remove the border for all images:

img,
a img {
    border: none;
}

For what it’s worth, I can’t access your site either. Checked with:

https://www.whatsmydns.net/#A/dustcatchers.org
https://www.intodns.com/dustcatchers.org
https://gsitecrawler.com/tools/Server-Status.aspx
https://www.seoconsultants.com/tools/check-server-headers-tool/

Appears to be a DNS problem.

If your theme supports it, you can use a custom menu:

Appearance Menus Screen

What file were you editing? You can use an FTP client to access the files of your site and remove the code you added or replace the entire file/theme with a fresh copy.

The “Allow” directive technically isn’t part of the standard and thus doesn’t validate in that tool. However, every major search engine (Google, Yahoo, Bing, Baidu) supports “Allow” in some way. For the goal of allowing all bots, Google’s suggested robots.txt file is perfectly fine; any bot that doesn’t understand “Allow” will simply skip it, not find any “Disallow” rules, and assume the entire site can be crawled. Of course, all this applies only to nice bots that actually follow what’s in robots.txt. ??

For what it’s worth, WordPress dynamically generates this for sites not set to private:

User-agent: *
Disallow: