Install

Works with Drupal: ^9.3 || ^10

Using Composer to manage Drupal site dependencies

Alternative installation files

Download tar.gz 1.09 MB
MD5: 3cf44130d4410e3e9ba7131c2efb21c6
SHA-1: 7a3aad543bcbc426d1da227c126250a03cd147de
SHA-256: 941331c77b8a9211d9a924952c1ac8857b7df1902d8ac4e67e78f9163a9b4741
Download zip 1.39 MB
MD5: 1de1b5633acfaac0c8b9931fe0df3da3
SHA-1: 60e840f47b4cd13cc1f72381f64e81c1d7e60217
SHA-256: 028f200a8ee5c26a4d4f5098cc8c43cc5fc3383004dd8cac540f17bdd724a9f5

Release notes

Big changes: New Feeds Log module, Drupal 10 support

New Feeds Log module!

A module is added to Feeds with which you can track your imports. It lets you see in detail which items were created or updated and which one failed.
See the video for a quick introduction:
https://youtu.be/P3ipggf5Irs

Other notable additions and changes

  • Multiple feeds to update the same content

    Imported content can now be tracked by multiple feeds. This way Feeds can properly see if content by each feed has changed. Previously, when you used more than one feed to update the same content, Feeds would see all content updated by feed 1 as changed when importing these with feed 2. This caused that a lot of items that were not changed got reimported.

  • Locks gets automatically extended after 12 hours

    When an import starts, a feed gets locked - to prevent running an import for the same feed simultaneously. When an import finishes, the feed gets unlocked.
    By default, a lock expires after 12 hours. This was problematic for imports that take longer to complete as it could cause concurrent imports to happen. To mitigate that issue, a lock can now get automatically extended after 12 hours. The new Feeds Lock service checks if an import is still active and if so, it extends the lock with another 12 hours.

    This is how the Feeds Lock service determines if an import is still active:

    • It checks if there any queue items for the feed in question. If so, the import is considered active.
    • It checks if there was import activity within the last hour by checking the last_activity variable in the key/value table. If so, the import is considered active.

    One caution: You may need to regular check your imports, because an import that got stuck on the queue may remain to be stuck.

  • Feed objects are no longer serialized on the queue

    This saves memory and storage space in the database. Instead, a reference to the feed is saved on the queue.

    One caution for developers: if your module stores temporary data on a Feed object during an import, be sure to check if that still works as intended. That data could possibly get lost if an import takes multiple cron runs to complete.

  • Revision support

    On the feed type you can configure to let Feeds create a new revision on each import.

Contributors (33)

MegaChriz, lind101, coaston, Nila Hyalij, Manoj Raj.R, carolpettirossi, unstatu, PunamShelke, Anybody, danharper, trickfun, webdrips, bharata, devad, irinaz, Project Update Bot, hershy.k, joco_sp, andreyjan, themodularlab, nikathone, mikran, bibo, darvanen, joshua.boltz, ramil g, andypost, joelpittet, andileco, ptmkenny, sker101, pixiekat, immaculatexavier

Changelog

Issues: 15 issues resolved.

Changes since 8.x-3.0-beta2:

Bug

Feature

Task

Created by: megachriz
Created on: 8 Dec 2022 at 15:20 UTC
Last updated: 8 Dec 2022 at 15:20 UTC
Bug fixes
New features

Other releases