Closed (outdated)
Project:
Thunder
Version:
8.x-2.16
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Apr 2018 at 04:29 UTC
Updated:
15 Mar 2019 at 12:30 UTC
Jump to comment: Most recent
Verion 1.x of the emvideo module does not define the source_module property, which is now required and throw an error if running a migration
See #2953339: "The emvideo plugin must define the source_module property."
Comments
Comment #2
ergophobe commentedThis probably needs to be a meta issue. It's a problem with multiple modules as a result of this change record
Use 'source_module' and 'destination_module' annotation to indicate module responsible for migration
It affects field group as well and there is a patch that works
#2951335: Getting d6_field_group plugin must define the source_module property Error When Using migrate-upgrade
It affects redirect and the relevant issues have been closed and the fixes committed to the current dev version
#2947642: d6_path_redirect plugin must define the source_module property
#2955400: d6_path_redirect has to define the *correct* source_module annotation
Comment #3
chr.fritschI don't get it. What do we have to change in Thunder?
Comment #4
ergophobe commentedThunder components are, or at least at the time were, out of date. That meant that you could not do a migration from a D7 site to D8 Thunder because, for the newer versions of the Migrate module to function, the source_module property *must* be defined.
In the versions that Thunder was using, it was not, so the migrations fail.
The change record I link to describes the architectural change.
The issues I link to are for that issue for individual modules that are packaged with Thunder. So for path_redirect, it's fixed in the dev version. In field_group the patch is RTBC and I'm not sure for emvideo
Comment #5
chr.fritsch