• Resolved transformedbytrials

    (@transformedbytrials)


    For some reason, subscribers aren’t receiving my blog posts. I have them set up to send out on WordPress, but also have a few going out on mail chimp. Neither list is receiving their posts. When i tried to validate my feed on mail chimp, it says, “This feed does not validate – parsing error.”

    I was wondering if anyone has an idea of how I can fix this. My blog is https://barbraveling.com and i think my feed is https://barbraveling.com/feed. Any help would be greatly appreciated!

Viewing 15 replies - 1 through 15 (of 20 total)
  • Moderator James Huff

    (@macmanx)

    https://barbraveling.com/feed/ is indeed your feed, but it’s not validating: https://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fbarbraveling.com%2Ffeed%2F

    The big issue is the error on line 59. Something is really off with the apostrophes at https://barbraveling.com/2015/09/24/i-deserve-a-donut-iphone-app-update-read-before-updating/

    Try editing the post and just retyping them, don’t copy/paste.

    Thread Starter transformedbytrials

    (@transformedbytrials)

    Thanks so much, James. I just looked at that link and it looks like WordPress thinks this blog post is a podcast as right before line 59 there’s all kinds of info about my podcast and then also about my app (the pix on this post is of my app). I wonder if that’s part of the problem. Do you think using a png file for the picture somehow brought up all my podcast stuff since it’s a picture I took from the iTunes store?

    Thread Starter transformedbytrials

    (@transformedbytrials)

    Also, thanks so much for your help! Just knowing that that’s the problem makes me feel better as it feels like it’s solvable! ??

    Moderator James Huff

    (@macmanx)

    Don’t worry about that, it’s not why your feed is broken (or at least it’s a very slim chance).

    I do recommend following up with support for your podcast plugin when this is done though. ??

    Did re-typing those apostrophes make any difference?

    Thread Starter transformedbytrials

    (@transformedbytrials)

    No, I tried retyping it and then taking out the apostrophes altogether and it didn’t make a difference. That’s a good idea to check with support of the podcast plugin as well.

    Thread Starter transformedbytrials

    (@transformedbytrials)

    I also tried disabling the podcast plugin but that didn’t help either.

    Moderator James Huff

    (@macmanx)

    Ok, something else is getting in the way then.

    Try deactivating all plugins. If that resolves the issue, reactivate each one individually until you find the cause.

    If that does not resolve the issue, try switching to the Twenty Fifteen theme to rule-out a theme-specific issue (theme functions can interfere like plugins).

    Thread Starter transformedbytrials

    (@transformedbytrials)

    just tried it and neither of those things worked either, although I was glad to try it just to know i could do it! Am going to switch back to Genesis theme now. Hopefully I can do that as well!

    Moderator James Huff

    (@macmanx)

    Are you using any sort of caching plugin, or do you see a “Clear/Purge Cache” button in your Dashboard or admin bar? If so, would you please try clearing the cache?

    Note: You do not need to install a caching plugin at this point just to clear a cache you don’t have. If you don’t have a caching plugin or a way to clear a server-level cache, just say so. ??

    Thread Starter transformedbytrials

    (@transformedbytrials)

    Is it odd that the same paragraph is in line 59 and 62 – and in 59 it’s listed as a description?

    Thread Starter transformedbytrials

    (@transformedbytrials)

    oops didn’t see your last comment, I’ll try that.

    Thread Starter transformedbytrials

    (@transformedbytrials)

    The cache was disabled. When I enabled it, this message came up:

    “WP Super Cache Warning!
    Your server is configured to show files and directories which may expose sensitive data such as login cookies to attackers in the cache directories. That has been fixed by adding a file named index.html to each directory. If you use PHP or legacy caching consider moving the location of the cache directory on the Advanced Settings page.
    If you just installed WP Super Cache for the first time you can dismiss this message. Otherwise you should probably refresh the login cookies of all logged in WordPress users here by clicking the logout link below.
    The logout link will log out all WordPress users on this site except you. Your authentication cookie will be updated but you will not be logged out”

    Should I hit the “delete cache” button?

    Thread Starter transformedbytrials

    (@transformedbytrials)

    Maybe i should also hit the logout link?

    Moderator James Huff

    (@macmanx)

    Yes, delete the cache, then disable it, and then check the validator again.

    Thread Starter transformedbytrials

    (@transformedbytrials)

    Did that and same problem on the validator.

Viewing 15 replies - 1 through 15 (of 20 total)
  • The topic ‘Subscribers aren't receiving blog posts – invalid feed?’ is closed to new replies.