- Issue created by @IrtamDemha
- First commit to issue fork.
- Issue was unassigned.
- Status changed to Needs review
over 1 year ago 12:34pm 19 March 2023 - 🇮🇳India Ranjit1032002
Created a patch for the issue mentioned, please review.
Thank You. - Status changed to Needs work
over 1 year ago 6:29pm 20 March 2023 - 🇳🇱Netherlands ekes
I've not tested this against Drupal 10 yet - have you got it running, maybe run the test suite under Drupal 10? Or have you just changed the .info file? I can state with certainty that the module is not compatible with Drupal 8, so that clearly hasn't been checked.
Also please don't use critical for priority unless it actually is for the functioning as declared. Like the module creates a fatal error on installation on the versions it says it works with. That sort of thing.
- 🇳🇱Netherlands ekes
Related https://www.drupal.org/project/domain/issues/3287020 📌 Automated Drupal 10 compatibility fixes Needs review
- 🇳🇱Netherlands ekes
Optional but related https://www.drupal.org/project/domain_path/issues/3287037 📌 Automated Drupal 10 compatibility fixes Fixed
- 🇳🇱Netherlands ekes
The main module 3.x branch is now Drupal 10 compatible. The path submodule needs further testing with the domain_path branch on https://www.drupal.org/project/domain_path/issues/3287037#comment-14992837 📌 Automated Drupal 10 compatibility fixes Fixed
- 🇺🇸United States bsnodgrass
Per https://www.drupal.org/project/domain_path/issues/3287037#comment-14992837 📌 Automated Drupal 10 compatibility fixes Fixed it seems this is now fixed.
This should be checked again.