This issue tracks the status of the 8.8.0 beta testing program, the recommended testing procedure is described in the handbook page. An overview of the beta testing program status is available at the tracking spreadsheet.

Testing instructions

People and organizations that joined the program are listed in the tracking spreadsheet and are expected to keep the row referencing them up-to-date. Each row contains the following information:

  • Username of the reference person linking the drupal.org profile
  • The testing outcome: either passed if no significant regression was found, or failed otherwise
  • A link to the reported issues in the following form:
    =HYPERLINK("https://www.drupal.org/project/issues/search/drupal?issue_tags_op=%3D&issue_tags=8.8.0%20beta%20testing&submitted=USERNAME";"issues")
  • A brief description of the testing process.

Any regression found should be reported in the Drupal core issue queue, should reference this meta issue as parent, and should be tagged with the 8.8.0 beta testing tag. This does not apply to security issues, which should be reported privately following the standard procedure.

Comments

pameeela created an issue. See original summary.

plach’s picture

Issue summary: View changes

Added tracking spreadsheet

plach’s picture

Priority: Normal » Major

Promoting to major

plach credited kim.pepper.

plach’s picture

Crediting kim.pepper.

plach’s picture

@kim.pepper wrote a nice blog post documenting the update process at https://www.previousnext.com.au/blog/updating-drupal-880-beta-composer.

berdir’s picture

I've successfully updated both our install profiles and did run our behat and kernel tests against 8.8.0-beta1. That includes an automated upgrade path test on one install profile with a dump that is currently ~8.6-based, with a multilingual site and tons of contrib modules.

Results are looking good, beside the known pathauto issues that are fixed in the available 8.x-1.6-beta1 which is also documented in the blog post above, I only had to fix some minor update path things in webform, but they are only for the edge case of updating a rather old webform version directly to 8.8. That's also already committed.

Beside that, I only found a single regression in core which is already actively discussed and I believe can be fixed, will work on that: #2673980: RSS view with fields give wrong URL from path field.

plach’s picture

Thanks @Berdir, this sounds promising!

sokru’s picture

Tested with custom installation profile, multilingual + 40 contrib modules.
No issues when using the correct pattern:
1) Update pathauto & drush cr
2) Update core.

When updating pathauto + core in simultaneously, got stuck with system_update_8804. I think it should be documented how to proceed in that case, because I'm sure someone from 300k D8 sites will update without following the correct procedure.

plach’s picture

@sokru:

Thanks for reporting! Could you please open an issue with the details of the error you got? We can use that to track changes to the documentation or maybe even to improve system_update_8804() to be more defensive.

pameeela’s picture

Updated one site successfully, with no errors. Not a huge site but 50-odd contrib modules and about 10 custom modules.

Got a warning because I had an incompatible version of Claro installed but once that was resolved the update was smooth.

rosk0’s picture

Not sure how to report this but I found that Issue #3039026: Deprecate file_directory_temp() and move to FileSystem service is not mentioned in 8.8.0-alpha1 not in 8.8.0-beta1 release notes but it's quite significant change which requires developers attention. So while project (internal ref: MvwPG+Bjf4f9z14o) update was successful functionality was affected by a bit broken configuration. Should I still create a sub-issue for this? The obvious and most effective way of "fixing" it is actually update release notes for both (8.8.0-alpha1 & 8.8.0-beta1) releases to mention #3039026: Deprecate file_directory_temp() and move to FileSystem service and corresponding change record https://www.drupal.org/node/3039255 .

larowlan’s picture

I updated two large sites, with a lot of contrib modules. No major issues - just some composer dancing and a patch to menu_item_extras as updating it broke Drush.

larowlan’s picture

@RoSk0 agree, that does belong in the release notes - I'll add the tag

jibran’s picture

I updated a large client site to Drupal 8.8.0 beta, other than pathauto #3093401: Compatibility with Drupal 8.8.0-beta1, subpathauto issue #3093377: Fix the failing HEAD and rerolling some core patches everything worked fine without a glitch.

plach’s picture

Thanks @jibran! Could you please confirm that the "subpathauto" issue is fixed with 8.8.x HEAD?

larowlan’s picture

Currently stuck on #3095390: Drupal Core 8.8-beta1 update fails with Group 8.x-1.0-rc4 for one of my sites.

GroupViewsData in group module sub-classes EntityViewsData which uses DeprecatedServicePropertyTrait to provide BC support for $this->entityManager.

However it looks like route-rebuilding happens in a terminate event, and by that time the container doesn't have the service? So fails with

Call to a member function getDefinitions() on null

When it calls $this->entityManager->getDefinitions()

larowlan’s picture

Actually the issue there is that GroupViewsData defines an entityManager property so the magic __get doesn't fire

rosk0’s picture

Found and issue with updating one of client projects (int ref GPR4hICg7eWZSLT3) :
Drupal\Component\Plugin\Exception\MissingValueContextException: Required contexts without a value: view_mode in Drupal\Core\Plugin\Context\ContextHandler->applyContextMapping() (line 155 of core/lib/Drupal/Core/Plugin/Context/ContextHandler.php).

Not sure if it's coming from, panels or core, so not raising an issue for it yet.

Any tips welcome.

jibran’s picture

RE#16: Yes, the patch is working with 8.8 rc release.

Edit: Yes, subpathauto issue is fixed in 8.8 RC.

plach’s picture

edva3000’s picture

good morning
I get the same RoSk0 error someone knows how I can fix it. Thanks for the help

Drupal\Component\Plugin\Exception\MissingValueContextException: Required contexts without a value: view_mode in Drupal\Core\Plugin\Context\ContextHandler->applyContextMapping() (line 155 of core/lib/Drupal/Core/Plugin/Context/ContextHandler.php).

Drupal\panels\Plugin\DisplayBuilder\StandardDisplayBuilder->buildRegions(Array, Array) (Line: 176)
Drupal\panels\Plugin\DisplayBuilder\StandardDisplayBuilder->build(Object) (Line: 190)
Drupal\panels_ipe\Plugin\DisplayBuilder\InPlaceEditorDisplayBuilder->build(Object) (Line: 329)
Drupal\panels\Plugin\DisplayVariant\PanelsDisplayVariant->build() (Line: 396)
Drupal\panelizer\PanelizerEntityViewBuilder->buildPanelized(Object, Object, 'full', NULL) (Line: 356)
Drupal\panelizer\PanelizerEntityViewBuilder->buildMultiplePanelized(Array, Array, 'full', NULL) (Line: 274)
Drupal\panelizer\PanelizerEntityViewBuilder->view(Object, 'full') (Line: 105)
Drupal\Core\Entity\Controller\EntityViewController->view(Object, 'full', NULL) (Line: 71)
Drupal\node\Controller\NodeViewController->view(Object, 'full', NULL)
call_user_func_array(Array, Array) (Line: 123)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 573)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 124)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext(Array, Array) (Line: 97)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 151)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 68)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 57)
Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 47)
Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 106)
Drupal\page_cache\StackMiddleware\PageCache->pass(Object, 1, 1) (Line: 85)
Drupal\page_cache\StackMiddleware\PageCache->handle(Object, 1, 1) (Line: 47)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 52)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 23)
Stack\StackedHttpKernel->handle(Object, 1, 1) (Line: 694)
Drupal\Core\DrupalKernel->handle(Object) (Line: 19)

cilefen’s picture

Status: Active » Fixed

@edva3000 Please open a new issue and link it here.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.