Thank you all for your input here guys! really appreciated! I'm using Radix and a sub-theme generated from it so probably the error i'm facing comes from there, i'll keep testing and keep you posted.
Thanks @siramsay! good to know! as i mentioned, V. 1.1.2/dev of this module current release on a D-10.2/10.3 fresh install is not a working version, so ideally for the sake of having a Drupal working workflow, we might need to provide a tested patch (through composer) here on this issue and/or wait 'till the MR goes into the main line asap.
Hi @ DamienMcKenna, thank so much for your response.! So in order to make the picture clearer, this is what I'm using to get migrations work from an old D.8.5 to D.10.x in this case, hoping we can improve the documentation.
1.- Install: Migrate
2.- Install: Migrate Plus
3.- Install: Migrate Tools
4.- Install: Drupal 8+ migration (source) - (Which is supposed to connect content from external databases at this time)
Technically speaking "migrate_drupal_d8" does offer a plugin (d8_entity) to import any entities from D8+ (Tried it before with migrations from D8 to D9 https://antrecu.com/blog/how-migrate-drupal-8-drupal-9 ) when creating .yml files and it works great. But when it comes to ECK migrations from D.8.x, D.9.X to D.10.x it just won't recognize any of the available options for ECK apparently.
Thanks @TheTomatoFarmerReturns, just quick question here, i dont see a patch attached + not sure if you are using the dev version of the module or a custom patch ( or git repo code )? if you can provide more instructions on how to make this module usable for the time being, it'll be great. Changing the issue to Critical since the module is unusable as it is on v 1.1.2.
Hi all,
I'm trying this module for the first time on a fresh Drupal 10.2.7 install, followed the instructions on the documentation, but seems the issue is still present on v 1.1.2 of the module. See screenshots for reference, Chrome/Firefox Dev tools pretty much shows the same error described here for all the snippets supported by ckeditor 5 code snippets in Core (php, xml, bash, etc etc) also it doesn't seem to apply the hljs theme.
andres.torres → created an issue.
andres.torres → created an issue.
Issue still present on Drupal 10.2.6 see related issue: https://www.drupal.org/project/migrate_drupal_d8/issues/3296374 🐛 Taxonomy Migration won't work since taxonomy_term_hierarchy table does not exists anymore - follow up Active
Still an ugly issue when the source database is from a Drupal 8 database. Im running a fresh D 10.2.6 install with migrate, migrate_plus, migrate_tools (latest stable versions) and tried with the current stable version of this module and the dev version as well, applied patch #6 provided on
https://www.drupal.org/project/migrate_drupal_d8/issues/3026875 →
but the issue is still present, also tried the multiple combinations for the yml definition migrate file but no luck. See attached screenshot.
If you can provide any guidance on how to make this work Id really appreciate it. I think we should change the priority of the issue to Major since its a key factor to have Taxonomies imported.
+1 for #26, Working on Drupal 10.2.6 fresh install.
The issue is not fixed! Using Claro-Gin under PHP 8X is triggering these errors, lets please work together to fix them on Drupal 9.5+, Since when turning back to Seven there is no issue.
Moving to critical since Seven has been deprecated as the admin theme and so far is either Claro or Gin the way to go on the adming themes side, i consider this to be a blocker.
Please let's also test on non-deprecated project themes. GIN is a good-to-go now.
Hi All, still not sure if this issue is related to https://www.drupal.org/project/field_group/issues/2969051 🐛 HTML5 Validation Prevents Submission in Tabs Postponed: needs info but in order to make sure it gets fixed im reporting it also here. Any help is very appreciated.
Moving things around, having this module to support nested accaccordiongs has become important!
Hi All,
I'm reopening this since it still an issue when using the Multistep option. We have a contentype with 3 multi-groups under this scenario but unfortunately after upgrading to x.3.4 they stop working on the Admin side (not even user 1 can create content). I've applied the patch on #87 successfully but the issue persists, I have also disabled the HTML5 validation on ALL forms $form['#attributes']['novalidate'] = 'novalidate'; on a custom module. There are no permission implemented, as i mentioned not even user 1 can go through the second step (we have 3 steps using field group ) Works OK on the front end theme. Gin works ok for other contentypes without Field Group. Dont see any Javascript errors on console or any other php errors either.
@saschaeggi,
Sorry, might be my bad, i was expecting the gin_toolbar to show the dropdown menus when hovering over the main menus. I was missing apparently the admin_toolbar contrib module ( https://www.drupal.org/project/admin_toolbar → ) as well, just added it and all seems to work as expected. Maybe we want to make this part of the documentation, still a bit confusing. Thanks so much again for your time and contribution!
Tried uninstalling both, here the screenshot when hovering over any of the menu items
No, is a small porting form a D8 to a D9 site, Gin is working fine, the modules you mention are both enabled. I've been using Gin + Gin Toolbar for a while now on other bigger/complex projects with no issues thats why this is calling my attention. Pls see screenshots attached.
Hi saschaeggi,
Yes followed the normal process, Gin is set as the only admin theme, made sure all regions are ok in the block layout for the Gin theme, the gin_admin tool bar module is enabled but it just wont show up on the admin theme.
@Greg Boggs, I totally understand your point, but having migrations from Drupal 8 to 9+ 10 or so on, doesn't mean you must have a step by step upgrade, and its - btw NOT NECESSARILY ( depends even on the platform and the solution ) The fix provided on #11 does provide a path to a full upgrade in/or some/many cases (which btw was recommend by Pantheon ). A config upgrade is key but when moving from older to newer version doesn't mean you have to go through the whole process if all goes Ok - under a full QA IMHO. The ability to manually edit a config file is what i consider a big plus! Oh, and once the site is consistent you can always export "drush cex" any new updates without compromising the existing configuration system.
Just a quick question on #16 you mention "6. Run drush deploy" - what version of drush are you using?
Thanks!
#11 worked for me when upgrading a d8 to d9 on Pantheon, thanks @Drumanuel