The current Feeds release works great. There are a few bugs and features missing that are blocking a stable release.
We aim to create new Feeds releases every 3-4 months.
Feeds issues series
On this page:
- Feeds 8.x-3.x
- Feeds Tamper
- Tamper
- Feeds Extensible Parsers
- Feeds 7.x-2.x
- Feeds Migrate
- Commerce Feeds
8.x-3.x
This list groups issues that are either requested a lot in the issue queue or are features that are not yet ported from the D7 version of Feeds.
1. Beta blockers and beta targets DONE
8.x-3.0-beta1 was released on February 24, 2022. It contains the previously missing UI for managing custom sources - which was needed for Feeds Extensible Parsers to add options for their custom source types.
These issues were beta targets, but did not make it into the first beta:
#3126351: A translation already exists for the specified language
#2998037: Allow more field types to be used as reference filter fields
#3073275: Mapping to books
2. Drupal 10 support DONE
Before addressing the stable release blockers, we are first focusing on making Feeds compatible with Drupal 10. So hopefully that work is finished before the first release of Drupal 10.
This does mean Drupal 8 support will get dropped. Because I think that having a 8.x- prefix on a release that does not support Drupal 8 looks weird, we're opening a 4.x branch soon. The deprecated class "FeedsAnnotationFactory" will also be dropped in that branch:
#3136615: Remove deprecated FeedsAnnotationFactory class
Existing Feeds plugins that haven't been updated since FeedsAnnotationFactory was deprecated (which happened more than 2 years ago in 8.x-3.0-alpha6), may stop working. This is for example the case for the FeedsTarget plugin in the Paragraphs module.
Paragraphs FeedsTarget plugin would need to:
- Remove the "arguments" section from the annotation;
- Implement
Drupal\Core\Plugin\ContainerFactoryPluginInterface
and use thecreateInstance()
method to inject dependencies.
3. Stable release blockers
The following bugs are important to fix before releasing a stable version as they could introduce API changes or additions:
#2912130: Missing temporary files in load balanced environments
#3155929: Http Fetcher receiving 304s Do not clear out their queue items.
#3158678: FetcherResult::checkFile() throws \RuntimeException, which is never caught
#3136615: Remove deprecated FeedsAnnotationFactory class
4. File target issues
There are several issues reported for the File target.
Right now - if you want to import files - they need to come from a HTTP source.
We want to fix the following things for the file target:
- Support stream wrappers (like public:// and private://)
- Support relative server paths
- Support downloading files where the url doesn't specify an extension
- Properly cleaning up previously imported files (when replaced with an other file)
- New option to import by file url that has the current functionality and hide the reference by field if checked
- When reference by file ID, expect a file ID as input
- When reference by UUID, expect a UUID as input
- Repair “existing files” setting.
See issues tagged with Feeds file target
5. Media support
Feeds doesn't support the core Media module completely.
#2928904: Add a mapping target to media field
6. Append values workflow
When updating existing entities, Feeds always empty the fields first before writing new values to them. This way empty values can be imported properly.
In some cases you don't want Feeds to empty the values, but instead appending them.
Through out the history of Feeds, this feature has been requested many many times. For D7 we decided to not implement this as it would become too complicated to support. For D8 it might be doable to implement this, now that almost everything are classed objects.
#3136170: handy way of preparing the CSV source?
Historical D7 issues:
#2071095: Need a way to add values to multi-value fields if target entity exists (update existing)
#2059995: Where to access the original value of the entity field to be imported
#2273299: How to retain existing values and append new values in hook_feeds_set_target
#1871970: Getting all the values to the same field from different lines of CSV
#2490840: Multiple records in one import overwrite each other
#2581611: Adding field items (instead of replacing) on update of existing nodes
#1670230: Appending multiple values in one taxonomy reference field
#1789670: Update Node values without needing to include all values in Feed
#3012255: Mapping multiple variations to one product only creates one variation per product.
7. Feeds Import Preview
For the D7 version of Feeds we can see the parsed result with the Feeds Import Preview module, which is very useful for debugging imports. For D8 there's something like this in the sandbox module Feeds DEV, though it's less user friendly and when using it in combination with the HTTP Fetcher, it sometimes doesn't update due to the HTTP Fetcher aborting the fetch when the source returns a 304 status code.
#2141945: Simulate & preview a feed import
8. Multilingual support
In Feeds 8.x-3.0-alpha7 multilingual support was mostly done, but there are a few issues not fixed yet:
#3126351: A translation already exists for the specified language
#2835754: Add mapping target for config entity 'language'
#3139441: could not update term that is created by feeds
See also Feeds issues tagged with multilanguage.
9. Other
In 2017 we did a survey for Feeds. Based on that, the following features were also marked as important:
- Support for huge data files
- Chained imports
- Rollback imports
- Keep same content ids as in the source
- Analytic report of import process
Other interesting issues:
#3173024: Add a generic field target
Feeds Tamper
There is a fatal error when using a certain combination of Tamper plugins, blocking a stable release:
#2983197: Catch TamperException to prevent import from crashing
#3063055: Allow parsers and event subscribers to mark an item as invalid
Tamper
There are a few Tamper plugins left to port from Feeds Tamper 7.x-1.x:
#2958013: [META] port remaining feeds tamper plugins
Feeds Extensible Parsers
A few features are left to be ported from the D7 version:
- JMESPath parser support
- Source parsing options (like importing a field as raw XML)
See also Feeds beta blockers, more specifically #2938505: Add UI for editing and removing custom (CSV) sources
Feeds 7.x-2.x
It's been a while since the last D7 release for Feeds. It would be nice to get it compatible with recent PHP versions. The dev version also has some unfinished bug fixes: a somewhat larger bug was divided into chunks, but not all chunks were done yet.
- PHP 7.2+ compatibility
- Large file import
- Validation issues
For more information, see #2911291: Plan for Feeds 7.x-2.0-beta5 release
Feeds Migrate
Most important issue to fix first:
#3002362: Foundation: Feeds migrate Processors/Tamper UI
Next in line:
Migrate Preview
Core issues to be fixed:
#2852463: Create a trait and base class to implement \Drupal\Component\Plugin\ConfigurableInterface
#2937177: [PP-1] Migrate plugin base classes should implement ConfigurablePluginInterface
See also:
#2990289: [META] Feeds_migrate Road Map
#2903175: [Policy, No patch] Consider adopting parts of migrate system in the underlying parts of feeds
Commerce Feeds
#3074303: Automatically set default store for products if source doesn't provide a value
Feeds vs Feeds Migrate
Feeds 8.x-3.x actively being developed until at least the release of Drupal 10
The Feeds Migrate project is experimenting with bringing Feeds UI features to Migrate.
It will take a while before Feeds Migrate's feature set will reach the same level as Feeds 8.x-3.x.
Development of bug fixes and features will continue on the 8.x-3.x version of feeds for the next few years until Feeds Migrate is mature and feature development of feeds can stop.
Feeds will at least be ported to Drupal 10. If it will be ported to Drupal 11 is uncertain at this moment (March 30, 2021).
Feeds Migrate may eventually become the Feeds 4.x version. However, if Drupal 10 introduces any disruptive changes requiring Feeds to make backwards compatibility breaks, there could be a Feeds 4.x version that is 99% the same as the 8.x-3.x version, but with support for Drupal 10. In that case Feeds Migrate may become Feeds 5.x instead.
Comments
Comment #1
ar-jan CreditAttribution: ar-jan commentedSetting this to 8.x branch. Maybe this issue can be used for updates on the 8.x status.
Comment #2
andypostComment #3
miro_dietikerI see there's recent progress in the module.
Could you please provide some status summary about the port progress, stability and remaining tasks?
Comment #4
MegaChriz CreditAttribution: MegaChriz as a volunteer commented@miro_dietiker
There isn't a clear path forward yet as far as I know, though the first big issue to tackle is #2443471: Implement configurable parsers.. When that issue is done, CSV importing will work and the work could continue for the Feeds extensible parsers project. I can imagine that writing more tests and port features of the 7.x-2.x version will be next. We're currently more focussing on the 7.x-2.x version right now. As soon as #1183440: Multilingual Feeds - Make field import language-aware is done, I might have more space to think about the 8.x-3.x version.
I am thinking of maybe sprinting on Feeds during DrupalCon Barcelona, though I have no experience in leading a sprint. Are you coming to DrupalCon Barcelona and interested in helping out there?
Comment #5
miro_dietikerThank you for the update!
Not sure if i will be there. Some of our team will be at least, but Feeds port is currently not on our team priority to assign own resources. We are already involved in >20 other modules... ;-)
Comment #6
MegaChriz CreditAttribution: MegaChriz as a volunteer commented@miro_dietiker
I understand. It is easy to get involved in too many modules. :) You can't do everything. Great to let me know!
Comment #7
ysaid CreditAttribution: ysaid as a volunteer commentedCould you please provide some status summary about the port progress, stability and remaining tasks?
Comment #8
MegaChriz CreditAttribution: MegaChriz at WebCoo commentedI've added a roadmap in the issue summary. As I already said in #2604358: [feeds] Feeds my plan is to first finalize the 7.x-2.x version of Feeds so I can put my focus completely on the 8.x-3.x version. I will keep an eye though on provided patches that contain small changes (broken tests, fatal errors, etc.), but the big changes that are needed for a stable 8.x-3.x release will have to wait if they depend on me.
If someone is brave enough to step up and is committed to work on the big changes for a long time, I'm happy to guide him/her as far as I'm able to.
Comment #9
MegaChriz CreditAttribution: MegaChriz at WebCoo commentedText correction in issue summary.
Comment #10
FrancewhoaWe would be happy to contribute testing patch, quality assurance, documentation, and agile project management services if needed
Related pages
Comment #11
MegaChriz CreditAttribution: MegaChriz as a volunteer commentedGreat, Francewhoa :). Thanks for your offers.
At this point there isn't much work yet for testing patches and documentation, but I'm sure having someone in that area could be a great addition later in the process. In this phase Feeds for Drupal 8 can be helped most with:
Comment #12
No Sssweat CreditAttribution: No Sssweat commentedSounds like this port is going to take quite a while.
Comment #13
TomSherlock CreditAttribution: TomSherlock commentedHello, MegaChriz.
I realize 8.x-3.x version is still unstable. However, I would like to determine whether my experience with 8.x-3.x version is consistent with your current expectations of this version.
I Installed Feeds 8.x-3.x version on Drupal 8.0.1 on AWS.
What are the current ways of interfacing with Feeds on Drupal?
I am able to see it installed on Extend with links to Help, Permissions and Configuration
I can see Feeds on the Permissions page (currently set for Administrator only).
I can see the Help page for Feeds. But there is not content on the page. There is just a link to Feeds administration pages: Feed types, Configure Feeds permissions
The Configuration link points to Feed Types. I am able to add new Feed Types.
When creating a new Feed Type I add a name, set Fetcher to Download, set Parser to Rss/Atom and Content Type to Article.
Fetcher settings are set to auto detect feeds.
Processor settings are set to not updating existing content. Content is set to never expire. Owner setting says: "Admin". Advanced Settings is set to Authorize.
I set up several source-target pairs
Item URL (link) - Feeds item: Item URL
Item GUID - Feeds item: Item GUID
Title - Title
Author Name - Authored by
Published Date - Authored on
Description - Body: Text (Should this be 'Feed Description'?)
Feed Image - Image: File Id (Is this image per feed item or a single image per feed)
When I add a feed type the form is titled "Add feed feed type". Is this duplication intended?
On the Status page I get the Entity/field definitions message:
Mismatched entity and/or field definitions
The following changes were detected in the entity type and field definitions.
Content
Update the node.feeds_item field.
Not sure what this means.
Finally I sometimes get a 500 error on the mapping page. It seems to happen when I put the fields in an incorrect error (e.g. I put the title field before the feed item URL field or I attempt to map to fields which should not be mapped such as description and body: summary.
When I attempt to create a feed by going to /feed/add I am able to start importing feed items but it fails. E.g. with the url http://www.scoop.it/t/cannabis-industry/rss.xml, the feeds modules attempts to import 30 articles but it fails. The error messages are:
'' not found
Failed importing 30 Articles.
Is this the expected behavior? What needs to be done or present in order to be able to import article successfully?
Thanks,
Tom
Comment #14
MegaChriz CreditAttribution: MegaChriz as a volunteer commentedI've updated the issue summary to give an overview of the long term plan for Feeds. The first step to take now is explained further in #2917928: Plan for 8.x-3.0-alpha1 release and its child issues.
Comment #15
MegaChriz CreditAttribution: MegaChriz as a volunteer commentedFeeds 8.x-3.0-alpha1 and Feeds extensible parsers 8.x-1.0-alpha1 have been released!
I'll update this issue when an initial plan for the next release is made.
Comment #16
doncheks CreditAttribution: doncheks commentedThis is good news. Many thanks for the effort and hours put in. Will be testing it. I hope we get a stable release sometime soon.
Comment #17
TokiGreat news indeed, Feeds is an absolute must-have for any Drupal website involving large databases, thanks again for this long-term work. #D8NeedsFeeds!
Comment #18
MegaChriz CreditAttribution: MegaChriz as a volunteer commentedThanks for your nice comments, @doncheks and @Toki! They mean a lot to me. A few months ago I had thoughts about giving up on Feeds, because the road ahead still seems long. It are these kind of comments that help me wanting to go on.
Comment #19
Yoobie13 CreditAttribution: Yoobie13 commented@MegaChriz the organization I work for is also excited to be able to incorporate Feeds into our D8 site. Thank you for your work on this!
Comment #20
ar-jan CreditAttribution: ar-jan as a volunteer commentedI'm not using Drupal much these days, but I keep an eye on various D8-related threads including this one, to see if I can/should upgrade stuff or even use D8 for new (hobby) projects. Feeds is def an important one for me, so thanks for the continued efforts!
Comment #21
MegaChriz CreditAttribution: MegaChriz as a volunteer commentedPlan for the next alpha release: #2967626: Plan for 8.x-3.0-alpha2 release
Issues of interest:
#2951965: PHP 5.6: Fatal error during import: FormattableMarkup::__toString() must not throw an exception
#2772595: When mapping to File or Image fields, empty source for target_id causes Exception and breaks import process.
#2803057: Expire feature deletes all imported items
#2820548: Fatal error when triggering Feeds via cron
#2854914: Deleted Target Field Throws Fatal Error
#2954018: "Auto detect feeds" feature causes the validation error "Invalid feed URL" for certain urls
#2938505: Add UI for editing and removing custom (CSV) sources
#2911491: Provide feeds type fields as mapping sources
#2917925: Port remaining methods from test base class in D7
Comment #22
MegaChriz CreditAttribution: MegaChriz as a volunteer commented8.x-3.0-alpha2 has been released!
https://www.drupal.org/project/feeds/releases/8.x-3.0-alpha2
I hope in the next few months I can do more research on integration with Migrate. I still only know the basics of that module and I feel I need to dive in deeper to see how Feeds and Migrate can grow closer to each other.
Meanwhile I've also opened an issue with a plan for the next release: #2978642: Plan for 8.x-3.0-alpha3 release. Basically the focus will be to prepare for Drupal 8.6.0 and to fix test failures for PHP 7.1 and PHP 7.2. I have also some half-finished features from which I hope I can finish some (so that I have less patches on Feeds to apply for each client project!).
Comment #23
jcnventura CreditAttribution: jcnventura at Wunder commentedAny plans on adding an upgrade path so that d7 feed importers can be added to a d8 site during the upgrade path?
Comment #24
MegaChriz CreditAttribution: MegaChriz as a volunteer commented8.x-3.0-alpha3 has been released!
https://www.drupal.org/project/feeds/releases/8.x-3.0-alpha3
In the next few months we will put some more focus on the Feeds Migrate project, currently an experiment to see if we can bring Feeds UI elements to Migrate.
8.x-3.x won't be completely ignored though, see what is planned for the next release:
#2997770: Plan for 8.x-3.0-alpha7 release
@jcnventura
No, there are no plans currently for adding an upgrade path. It's appreciated if you would like to make one. :)
Comment #25
TokiAlways nice to get a notification about Feeds. Just for information, I have worked with Feeds 8.x recently and I have successfully imported more than 4000 contents. I have also added Feeds Tamper to explode multiple values and it worked like a charm. Many thanks for your work on Feeds D8!
Comment #26
jcnventura CreditAttribution: jcnventura at Wunder commented@MegaChriz, about my request in #23, done: #3008991: Migrate feeds content from Drupal 7
Or at least started it...
Comment #27
MegaChriz CreditAttribution: MegaChriz as a volunteer commented8.x-3.0-alpha4 has been released!
https://www.drupal.org/project/feeds/releases/8.x-3.0-alpha4
For the next few months, the plan is to continue putting time into the Feeds Migrate project. We are working on a plan to make that module minimally usable: #3020397: [META] Build a Feeds Migrate minimum viable product (MVP). We've not set a deadline yet for when we would reach that goal.
For Feeds 8.x-3.x we'll try to get in the following by March 2019: #2799225: The "hidden" plugin does not exist: Drupal\Component\Plugin\Exception\PluginNotFoundException: and at least minimal multilingual support (#2867761: Multilingual support). Minimal multilingual support could mean that you can select a language on the feed type processor settings form, which would allow you to import content for a single language. The other issue is important as it currently blocks #3008991: Migrate feeds content from Drupal 7 (which @jcnventura works on), which would be awesome to have!
See #2997770: Plan for 8.x-3.0-alpha7 release
Comment #28
MegaChriz CreditAttribution: MegaChriz as a volunteer commentedFeeds 8.x-3.0-alpha5 has been released!
That release includes a language target, feeds_item field formatters, a button to import feeds in the background and an ImportFinishedEvent.
For the next release we hope to get content translation in and we aim to get that done by August 2019. However, the Feeds team main focus will be the Feeds Migrate project. So it's quite possible that the next Feeds 8.x-3.x release will take longer.
Comment #29
Code2you CreditAttribution: Code2you commented@MegaChriz Thank you very much for your work on Feeds ! It's really a very usefull module.
Comment #30
MegaChriz CreditAttribution: MegaChriz as a volunteer commentedFeeds 8.x-3.0-alpha6 has been released!
Unfortunately, language support did not make it in that release. There was and is much work to be done to prepare this module for Drupal 9. Some of this work requires backwards incompatible changes. So far, I did this in a way to minimize disruption: in the alpha6 release I deprecated FeedsAnnotationFactory, which is used to declare service dependencies in the annotation of a Feeds plugin. This class remains in Feeds for a while, but you now have time to update your Feeds plugins to no longer use annotation for dependencies. One of the dependencies used in Feeds plugins is
@entity.query
which is deprecated since Drupal 8.3.0. Usage of this dependency will be removed before the next Feeds release and as a result, this could break Feeds plugins in contributed modules that extend\Drupal\feeds\Feeds\Processor\EntityProcessorBase
or\Drupal\feeds\Feeds\Target\File
(if these have@entity.query
declared in the annotation of their plugin). With the deprecation of FeedsAnnotationFactory now, these plugins can be updated in advance.I hope that the next release will be in February or March next year. Can't promise that as I'm also devoting time for Feeds Migrate.
See #2997770: Plan for 8.x-3.0-alpha7 release for plans for the next release.
Comment #31
liquidcms CreditAttribution: liquidcms commentedConfused by comments here of ongoing work as well as successful imports. I just tried to set up a CSV import to create a few user accounts and it doesn't seem like the UI is complete yet (https://www.drupal.org/project/feeds/issues/3115450). Wondering where the disjoint is. Possibly functionality has been lost through constant changes to D8 api (I am using with 8.8.1)?
Comment #32
MegaChriz CreditAttribution: MegaChriz as a volunteer commentedFeeds is working and usable. There are just only a few bugs left to be fixed and a few features from the D7 version left to be ported (from which multilingual support is the most important). The missing features are blocking the beta phase and some of the bugs will block a stable release.
I have tagged the beta blockers and nice to have before beta phase:
I haven’t tagged stable release blockers yet. First I’m focussing on the beta blockers.
Comment #33
MegaChriz CreditAttribution: MegaChriz as a volunteer commented8.x-3.0-alpha7 has been released! Its biggest addition is content translation support, but there are also some small BC breaks.
Comment #34
jcnventura CreditAttribution: jcnventura commentedAdded #3136615: Remove deprecated FeedsAnnotationFactory class to the list of remaining to-dos.
Comment #35
MegaChriz CreditAttribution: MegaChriz as a volunteer commentedCompletely changed the roadmap in the issue summary. Hopefully, this makes it more clear what work needs to be done to get it to a stable release. And also what issues are important to fix after the first stable release.
I also listed issues of Feeds related projects.
Comment #36
MegaChriz CreditAttribution: MegaChriz as a volunteer commentedRe-added #3136615: Remove deprecated FeedsAnnotationFactory class to the roadmap.
Comment #37
MegaChriz CreditAttribution: MegaChriz as a volunteer commentedAdded #3155929: Http Fetcher receiving 304s Do not clear out their queue items. and #3158678: FetcherResult::checkFile() throws \RuntimeException, which is never caught as stable release blockers.
Comment #38
MegaChriz CreditAttribution: MegaChriz as a volunteer commentedAdded link to the documentation issue in the issue summary: #3128379: Improving Feeds Documentation using information from solved issues
Comment #39
MegaChriz CreditAttribution: MegaChriz as a volunteer commentedPut #3173024: Add a generic field target on the roadmap.
Comment #40
MegaChriz CreditAttribution: MegaChriz as a volunteer commented8.x-3.0-alpha10 has been released! In that release the following things are added: Drush commands; targets for entity ID, user role and password; and other fixes.
Comment #41
dalemoore CreditAttribution: dalemoore commentedSo I am confused. Is the Migrate module now the path that we should be using to import all content, and Feeds will eventually be deprecated? And Feeds Migrate may become a UI for Migrate? I am setting up a Drupal 9 site and it will be importing podcasts via a feed. Trying to decide what to use that I won't have to change next year with Drupal 10.
Comment #42
MegaChriz CreditAttribution: MegaChriz as a volunteer commented@dalemoore
Feeds Migrate isn't anywhere near where Feeds is, so I say stick with Feeds right now. We're actually putting more time in Feeds lately, to get that one to a stable release. Depending on how well the development on Feeds Migrate goes, Feeds may eventually get deprecated. But I don't see that happen anytime soon. So I'm making the bold statement now that Feeds will be ported to Drupal 10. I don't know yet for Drupal 11 though.
Since I don't know yet if there would be any disruptive changes in Drupal 10, there is a chance backwards compatibility breaks are needed in order to support Drupal 10 - which would mean that Feeds plugins in contrib and custom modules may need to be updated in order to keep working with Feeds. So it is possible that we'll see a Feeds 4.x version that is 99% the same as the 8.x-3.x version, but with support for Drupal 10.
Comment #43
dalemoore CreditAttribution: dalemoore commented@MegaChriz Thanks for the clarification (and updating the description up top). I'll stick with Feeds!
Comment #44
jcnventura CreditAttribution: jcnventura commentedAnd there's always the option of doing what Webform did. At one point, someone decided YAML Form was better, than everyone thought the same, and then YAML Form became Webform 5.x.
Comment #45
thursday_bw CreditAttribution: thursday_bw as a volunteer commentedComment #46
thursday_bw CreditAttribution: thursday_bw as a volunteer commentedComment #47
thursday_bw CreditAttribution: thursday_bw as a volunteer commentedRemoved the documentation and drush commands sections as the related issues are fixed and closed.
Comment #48
thursday_bw CreditAttribution: thursday_bw as a volunteer commentedComment #49
Greg BoggsCan we switch from the alpha naming scheme? With the long release names, it didn't matter in Drush. But, with Composer, it's difficult to install Feeds because you have to type exactly this:
composer require 'drupal/feeds:^3.0@alpha'
If you type composer require drupal/feeds which works on almost every other module, you get this error:
[InvalidArgumentException]
Could not find a version of package drupal/feeds matching your minimum-stab
ility (stable). Require it with an explicit version constraint allowing its
desired stability.
Comment #50
irinaz CreditAttribution: irinaz as a volunteer and at Fibonacci Web Studio commentedComment #51
irinaz CreditAttribution: irinaz as a volunteer and at Fibonacci Web Studio commentedComment #52
MegaChriz CreditAttribution: MegaChriz as a volunteer commented8.x-3.0-beta1 has been released!
The next release will likely drop support for Drupal 8 and hopefully adds Drupal 10 support. Because I think that having a 8.x- prefix on a release that does not support Drupal 8 looks weird, we're opening a 4.x branch soon. The deprecated class "FeedsAnnotationFactory" will also be dropped in that branch:
#3136615: Remove deprecated FeedsAnnotationFactory class
Existing Feeds plugins that haven't been updated since FeedsAnnotationFactory was deprecated (which happened more than 2 years ago in 8.x-3.0-alpha6), may stop working. This is for example the case for the FeedsTarget plugin in the Paragraphs module.
Paragraphs FeedsTarget plugin would need to:
Drupal\Core\Plugin\ContainerFactoryPluginInterface
and use thecreateInstance()
method to inject dependencies.Comment #53
MegaChriz CreditAttribution: MegaChriz as a volunteer commentedUpdated numbers of the Feeds issues series in the issue summary.
Comment #54
solideogloria CreditAttribution: solideogloria commentedCould you opt into security coverage? That seems like a good idea to add to the roadmap.
Comment #55
irinaz CreditAttribution: irinaz as a volunteer and at Fibonacci Web Studio commented@solideogloria, only stable modules can opt into security coverage. We are planning sprint at BADCamp on Oct 6-7. Any help moving module towards stable release is greatly appreciated!
Comment #56
ecj CreditAttribution: ecj commentedLove to see row weights for mappings order, adjustment
Comment #57
ressa CreditAttribution: ressa at Ardea commentedThanks @irinaz and @MegaChriz, as well as the other maintainers for an incredible module, so useful and easy to use. @MegaChriz: "I had thoughts about giving up on Feeds, because the road ahead still seems long." I know this was in 2018, but don't forgot to look after yourself and not burn out. Feeds is important, but not that important :-)
Comment #58
MegaChriz CreditAttribution: MegaChriz as a volunteer commentedThanks, @ressa :)
These days I put less time in Feeds than a few years ago. I used to spend 7 hours a week on average on Feeds (besides my daytime job), now it is more like 2-3 hours a week. I try my best to look after myself, I do sometimes still fail in that, but the frequency of failures has been decreasing.
Comment #59
ummdorian CreditAttribution: ummdorian commentedComment #60
MegaChriz CreditAttribution: MegaChriz as a volunteer and at WebCoo commentedFeeds multilingual issues are now tagged with multilanguage.
Comment #61
tonytheferg CreditAttribution: tonytheferg commentedAny word on php 8.2 compatibility?
Comment #62
MegaChriz CreditAttribution: MegaChriz as a volunteer and at WebCoo commented@tonytheferg
The latest Feeds release is expected to be compatible with Drupal 10 + PHP 8.2. Tests are passing on that combination. Previously, there were issues installing Feeds on PHP 8.2 because a dependency was not declared compatible with PHP 8.2 yet. That issue has now been resolved in the dependency itself. No changes in Feeds were required afterwards, so that's why the current latest release should be PHP 8.2 compatible now. See #3325568: Add PHP 8.2 support for more information.
Comment #63
tonytheferg CreditAttribution: tonytheferg commentedHuh. I tried yesterday and got blocked by composer dependency.
Comment #64
Orkut Murat Yılmaz@tonytheferg, this is my composer output:
Also, output of my drush pml is:
Maybe it is about your composer configuration?
Comment #65
tonytheferg CreditAttribution: tonytheferg commentedComment #66
MegaChriz CreditAttribution: MegaChriz as a volunteer and at WebCoo commented@tonytheferg
Hm. At first glance that looks related to the dependency "laminas/laminas-servicemanager":
I don't know yet why you get the error while you try to require Feeds. Because laminas/laminas-feed does not require laminas/laminas-text and since v2.21.0 it no longer requires laminas/laminas-servicemanager either.
It would have made more sense that you weren't able to require drupal/upgrade_status on PHP 8.2. Or does this happen on a Drupal 9 install?
Comment #67
ressa CreditAttribution: ressa at Ardea commentedYou could try removing Upgrade Status, and see if that helps? #3328786: Upgrade status must be uninstalled before upgrading to Drupal 10
Comment #68
MegaChriz CreditAttribution: MegaChriz as a volunteer and at WebCoo commented@tonytheferg
Okay, when I try to require drupal/upgrade_status, it picks mathieuviossat/arraytotexttable 1.0.7 which still requires zendframework packages. zendframework packages have been replaced by laminas, so I would call zendframework packages to be "outdated".
So the possible solutions that I can think of right now are:
Comment #69
tonytheferg CreditAttribution: tonytheferg commentedDoh!! I'll try to remove upgrade status and report back
Comment #70
tonytheferg CreditAttribution: tonytheferg commentedThat was it:
Here are the results after removing upgrade status module.
Comment #71
Orkut Murat YılmazWell, we will be able to use the stable version of feeds 8.3.0 with php8.2, when it's released.
Thank you @MegaChriz and the others too:)