Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
migration system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
31 Aug 2015 at 19:40 UTC
Updated:
29 Dec 2016 at 22:04 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
webchickHere's a patch, and a screenshot.
Comment #3
webchickComment #4
phenaproximaPre-emptive RTBC from me.
Comment #5
catchI think we could do with a hook_requirements() warning for if there are any experimental modules enabled - for example you might have to uninstall before each core update then re-install again etc.
Comment #6
webchickLet's try this.
Comment #7
webchickNote the screenshot is slightly off, since the patch says "for testing purposes only." (adds the word only)
Comment #9
phenaproximaTwo thumbs up.
Comment #10
alexpottCommitted 496f553 and pushed to 8.0.x. Thanks!
I thought about asking for the comma separated item list for accessibility here - but it does not handle complete inline-ness that well atm so not doing that.
Comment #12
hass commentedThis issue introduced a bug. On my status page I now get told Experimental modules enabled, but these are NOT enabled. They are on the system, but not enabled!
Comment #13
webchickWhoops! Right you are! This is why no one should ever trust my code. ;)
Comment #14
hass commentedIsn't Core (Experimental) not a translatable string?
Comment #15
webchickGood question, I have no idea if module packages are translatable or not.
Comment #16
hass commentedIn D7 it is...
Comment #17
hass commentedYes, it is... but here in code it is still English and does not break. I hope that is still true, if someone may not use English on a site.
Comment #18
alexpottLooking at this again (oops), I don't think there is any need to rebuild the module data here. We can just call
system_get_info('module', $module);inside the loop.Comment #19
hass commentedAside... With marking this experimental we need to provide D6 security support until after a migration is stable + 3-6 months. Otherwise people cannot upgrade as they lose data what is really no option.
Comment #20
webchickI knew that was probably not right. Thanks, that feels much nicer. :) Also believe I verified that the t() around the 'Core - Experimental' is not needed; $this->t() is added dynamically in core/modules/system/src/Form/ModulesListForm.php:
#19 would be something to take up with security team, but AFAIK it's pretty much set in stone at 3 months past 8.0.0's ship date https://www.drupal.org/d6-lts-support FWIW though there are at least a few people who are running serious migrations against D6 and largely succeeding. The D6 -> D8 migration path has been in HEAD for a year or so; it's D7 => D8 that's still very much in progress.
Comment #21
phenaproximaI'm not sure if I'm the most qualified person to RTBC this, but it looks OK to me.
Comment #22
nerdcore commentedI have tested #20 and it works as advertised. The erroneous message indicating I have experimental modules enabled when I do not is now gone.
Comment #23
alexpottCommitted 72ed272 and pushed to 8.0.x. Thanks!
Comment #26
cilefen commentedThe committed patch does not test properly if the module package key is set, which leads to #2839844: Notice: Undefined index: package in system_requirements() (line 60 of core\modules\system\system.install). .