Let me know in the comments what issues you're facing!įinally, take a look at Lee's blog on some of the major changes in 8.4 for some more insight into what you might need to fix. It looks like it is not possible to add an alias, or use some other method to link drush to vendor/bin/drush by default in Drupal core. Thankfully, our project has a large suite of functional/end-to-end tests which really helped tease out the issues and gave us greater confidence that the site was still functioning well post-upgrade. Personally, I found the upgrade to be quite tedious for a minor version upgrade. $this->click('.ui-dialog button:contains("Save")') To get around that simply change your test to do something similar to the following: This span no longer exists, and attempting to "click" any other part of that button in a similar way will throw an error in PhantomJS. For example, in Linkit's LinkitDialogTest. This is a very edge case issue, but will hopefully help someone! In older versions of jQuery UI, the buttons that were added to the bottom of the modal form for submission had an inner span tag which could be clicked as part of a test. Tests that submit a modal dialog window will need to be altered When the uri is external, an error is thrown when it tries to get the route name " External URLs do not have an internal route name.". See this issue for more information.ģ. The menu_link_content module now has an entity_predelete hook that looks through an entities uri relationships and tries to find any menu links that link to that specific route, and if so deletes them. Custom entities with external uri relationships throw Fatal errors when delete while menu_link_content is installed Remove the field_dates field from the bundle field map for the page bundle. $node_map = $field_map_kv_store->get('node') Thats it You have successfully updated your Drupal 9 using Drush. However, if you are using Drush get('_field_map') composer update drupal/core drupal/core-with-all-dependencies. This will refresh the list of available updates so Drush knows there is a new release for Drupal. Note: If you are using Drush 8.1.15 you will not have these issues as it is now compatible with both Symfony 2.x and 3.x This means that when using composer to update Drupal core alone, composer will complain about conflicts in dependencies, since Drush depends on Symfony 2.x Updating your libraries The main conflict being that both Drush 8.1.x and Drupal 8.3 use the 2.x version of Symfony libraries, while Drupal 8.4 has been updated to use Symfony 3.x. The main issues with the upgrade to Drupal core 8.4 are dependency conflicts between Drush and Drupal core.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |