You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An idea for a new feature that could prevent feed_display to show errors because the feed could not be fetched:
Create a scheduler task that parses and stores the feed items in a database table every x minutes.
If the plugin is called it can use the stored records and show them in the frontend, using regular TYPO3 caching.
In case the feed goes down for some reason, the plugin can still show the old records until the scheduler task can import new feed items again. There is no error visible in the frontend, ever.
The text was updated successfully, but these errors were encountered:
Thank you very much for your suggestion. That sounds like a useful addition. I will be happy to look into the topic when I find some time again (which is currently relatively limited). If you like and have time to spare, I would also be happy to receive a corresponding pull request.
An idea for a new feature that could prevent feed_display to show errors because the feed could not be fetched:
Create a scheduler task that parses and stores the feed items in a database table every x minutes.
If the plugin is called it can use the stored records and show them in the frontend, using regular TYPO3 caching.
In case the feed goes down for some reason, the plugin can still show the old records until the scheduler task can import new feed items again. There is no error visible in the frontend, ever.
The text was updated successfully, but these errors were encountered: