Error with max_age and max_posts #67

New issue

Closed

opened 2025-11-29 12:53:39 +00:00 by Sebastian_Berlin · 3 comments

Sebastian_Berlin commented

2025-11-29 12:53:39 +00:00

(Migrated from codeberg.org)

I actually don't know why, because other feeds work with the new max_age and max_posts, but parsing this feed with

"max_age": "PT72h",
"max_posts": 3

won't work and a lot of errors appear. The last message was:

'NoneType' object is not subscriptable

Without them, everything works and the newest article was posted.

Than I've edited again the config.json and added back max_age and max_posts without problems.

This is really weird and I doubt this issue won't disappear in the future. But why, was has happened? 🤔

I actually don't know why, because other feeds work with the new `max_age` and `max_posts`, but parsing [this feed](https://www.rbb-online.de/exporte/NUR-DER-BSC.xml/feed=tsrss.xml) with ``` "max_age": "PT72h", "max_posts": 3 ``` won't work and a lot of errors appear. The last message was: `'NoneType' object is not subscriptable` Without them, everything works and the newest article was posted. Than I've edited again the `config.json` and added back `max_age` and `max_posts` without problems. This is really weird and I doubt this issue won't disappear in the future. But why, was has happened? 🤔

marvin8 commented

2025-11-29 23:39:00 +00:00

(Migrated from codeberg.org)

Had a look and found the issue. The way feedparser parses this feed it provides no published date but an updated date...
It's the max_age check that is bombing out because of the "missing" date. I have already got a fix ready for the next release.

Had a look and found the issue. The way feedparser parses this feed it provides no `published` date but an `updated` date... It's the max_age check that is bombing out because of the "missing" date. I have already got a fix ready for the next release.

Sebastian_Berlin commented

2025-11-30 07:45:46 +00:00

(Migrated from codeberg.org)

@marvin8 wrote in https://codeberg.org/marvinsmastodontools/feed2fedi/issues/67#issuecomment-8597811:

Had a look and found the issue. The way feedparser parses this feed it provides no published date but an updated date... It's the max_age check that is bombing out because of the "missing" date. I have already got a fix ready for the next release.

Awesome, thanks a lot!

@marvin8 wrote in https://codeberg.org/marvinsmastodontools/feed2fedi/issues/67#issuecomment-8597811: > Had a look and found the issue. The way feedparser parses this feed it provides no `published` date but an `updated` date... It's the max_age check that is bombing out because of the "missing" date. I have already got a fix ready for the next release. Awesome, thanks a lot!

marvin8 commented

2025-12-18 00:24:25 +00:00

(Migrated from codeberg.org)

Fix in release 3.4.1

Fix in [release 3.4.1](https://codeberg.org/marvinsmastodontools/feed2fedi/releases/tag/3.4.1)