• Resolved minerb

    (@minerb)


    It appears your plugin is not using <pubDate> to pull the published date off an episode, but its pulling another tag from our feed <castfire: date> .. the issue is the pubDate is what it should be looking at, but our other date field is in UTC and used elsewhere internally. Since its looking at the wrong tag, its showing the wrong published date when UTC is a a day a head of MST… example would be Hour 2: Mike Fader with a published date of 03/22/19 05:20 pm MST but shows 3/23 because its reading a the UTC date tag.

    pubDate is the official rss 2.0 tag.

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Veda

    (@vedathemes)

    Hi there,

    I have extensively tested the plugin as per your comment above. Here is what I have observed,

    1. The plugin is correctly using <pubDate> tag to pull published date.
    2. The problem seems to be caused by ‘-0700’ at the end of the <pubDate> string. In, Hour 2: Mike Fader episode in the feed above.
    3. Whenever this pubDate string is converted to equivalent timestamp, ‘-0700’ is causing the unexpected behavior.
    4. To test it,
    I. Go to https://coderstoolbox.net/unixtimestamp/
    II. Type ‘Fri, 22 Mar 2019 17:20:36’ (without quotes) in ‘RFC 2822 time’ and check time displayed in ‘ISO 8601 time’.
    III> Now type ‘Fri, 22 Mar 2019 17:20:36 -0700’ (without quotes) in ‘RFC 2822 time’ and check time displayed in ‘ISO 8601 time’. (It should be same as <castfire: date> )

    5. To test is further, you can place the feed url in WordPress default ‘RSS’ widget and it will show the same date (as my plugin).

    6. I suggest you please check why this -0700 is coming in the <pubDate> string.

    I think it should solve your problem. If not, please reply and I will try to help you.

    Thread Starter minerb

    (@minerb)

    thanks! the customer set their times back to compensate. I’ll create another test feed and do as you suggested. Thanks for your update.

    Brian

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Using wrong date tag’ is closed to new replies.