Problem/Motivation
Our needs are quite simple - "if you a 'associated' with 'this', 'that' or 'the other' then you can view this node" .
We recognise that that kind of scenario can be covered by the well-known Group module but we are finding that it just doesn't afford the level of flexibility that we need right now plus the issue queue is too large and to make it a viable candidate
What we need is something simple, robust and flexible for Drupal 10.
This module seems absolutely right for easily enabling such 'group' access functionality BUT, what about Drupal 10?
Do you have plans to test/adjust/release for Drupal 10?
Thank you
| Comment | File | Size | Author |
|---|---|---|---|
| #27 | pbf-drupal_10_combatibility-3348426-27.patch | 11.86 KB | chrissnyder |
| #23 | pbf-drupal_10_combatibility-3348426-23.patch | 11.54 KB | chrissnyder |
| #15 | 3348426-15.patch | 318 bytes | flocondetoile |
| #11 | Screenshot from 2023-07-06 11-28-27.png | 18.1 KB | dineshkumarbollu |
| #8 | pbf-drupal_10_combatibility-3348426-8.patch | 84.25 KB | chrissnyder |
Issue fork pbf-3348426
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
flocondetoileI should release a Drupal 10 compatible version this year (before the end of life of D9). As soon as I have some times to work on. Or sooner if someone provides a working patch.
Comment #3
flocondetoileComment #5
chrissnyderThis is one of the few modules we need to update our site to D10.
Any update on any work done to support Drupal 10? I may have some time in a few weeks to help work on a patch. If something has already been started I can pick up from that.
Comment #6
flocondetoileYou can start from and work on #3289037: Automated Drupal 10 compatibility fixes
Comment #7
jjmackow commentedWe are depending on this module in our update. Will look into issues.
Comment #8
chrissnyderThe attached patch provides D10 compatibility.
Ahead of a new release of this module, you can apply this patch using composer-drupal-lenient to allow you to upgrade to Drupal 10.
Comment #9
chrissnyderComment #10
chrissnyderComment #11
dineshkumarbollu commentedHi
Tested the module no D10 compatible issues found, i am attaching D10 report.
Thanks
Comment #12
flocondetoileAdded automated tests for D10.
Anybody have manually tested the module with the patch on D10 ?
Comment #14
flocondetoileCommitted only to be able to run the D10 tests.
Comment #15
flocondetoileDrop support of Drupal 8, and run tests on the -dev version.
Comment #17
flocondetoiletests needs to be refactored. Optionnal parameters must be placed at the end (no required parameters placed after them)
Comment #18
flocondetoileComment #19
flocondetoileIncoming patchs should be easier to review now. Keeping patch #8 in -dev branch
Comment #20
flocondetoileComment #21
chrissnyderComment #22
chrissnyderThis patch attempts to get the tests running on PHP 8.0 by refactoring the method signature for a couple of the methods, placing the optional parameters last.
See https://php.watch/versions/8.0/deprecate-required-param-after-optional
Comment #23
chrissnyderThis patch to get the tests running on PHP 8.0 by refactoring the method signatures in the test, and adds Drupal 10 compatibility by removing use of deprecated core theme, classy.
Comment #24
chrissnyderThe last patch, #23, fixes some of the issues with the tests. However, it does look like a few tests are still failing because they are unable to count the number of results on the search page. My suspicion is that \Drupal\Tests\pbf\Functional\PbfBaseTest::checkSearchResults relies on classes provided by the classy theme that is no longer available and it needs to be updated with a new XPath.
@flocondetoile Do you have any idea what that xpath selector should be changed to?
Comment #25
flocondetoileI guess we should change first the $defautTheme in PbfBaseTest.php, as classy doesn't exists anymore as a core theme in D10
We check this xpath
//ol[contains(@class, 'search-results')]/liOlivero has the same markup because of web/core/themes/olivero/templates/dataset/item-list--search-results.html.twig. So Tests should pass with Olivero.
Stable9 has only this template web/core/themes/stable9/templates/dataset/item-list.html.twig. So with stable9 the xpath should be
//ol/liI guessComment #26
flocondetoileSwitching to Olivero looks the best way to get green testss
Comment #27
chrissnyderThis patch includes an update to the theme used when testing and drops support for Drupal 8 which is EOL.
Comment #28
chrissnyderTests pass latest patch.
Comment #30
flocondetoileCommitted. A new release 8.x-1.4 has been published. Thanks everyone.