@La558

la558 → created an issue.

Patch @#9 worked perfect for allowing bulk operations.
Thanks
However, although I have it set to "Create new revision when publising/unpublishing a node" when performing bulk operations it does not create a new revision.

Are you aware of any workaround for this?

Hello,

Drupal: 10.4.1
PHP: 8.2.24
MySQL: 8.0.36

I just installed this module and after saving the configuration file, i got this error
Deprecated function: Creation of dynamic property Drupal\linkchecker\Form\LinkCheckerAdminSettingsForm::$moduleHandler is deprecated in Drupal\linkchecker\Form\LinkCheckerAdminSettingsForm->__construct() (line 96 of modules/contrib/linkchecker/src/Form/LinkCheckerAdminSettingsForm.php).

I have applied the patch shared by post #2
a) downloaded and added to my 'patches' folder

b) adjusted the composer.json file to add the entry under "extra"

            "drupal/linkchecker": {
                "Fixes Error: Deprecated function: Creation of dynamic property": "patches/linkchecker--creation-of-dynamic-property-module-handler--3464481.patch"
            }

c) after that, run composer install

, but I'm still having the same issue

Drupal\linkchecker\Form\LinkCheckerAdminSettingsForm->__construct() (Line: 104)
Drupal\linkchecker\Form\LinkCheckerAdminSettingsForm::create() (Line: 41)
Drupal\Core\DependencyInjection\ClassResolver->getInstanceFromDefinition() (Line: 48)
Drupal\Core\Controller\HtmlFormController->getFormObject() (Line: 58)
Drupal\Core\Controller\FormController->getContentResult()
call_user_func_array() (Line: 123)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 638)
Drupal\Core\Render\Renderer->executeInRenderContext() (Line: 121)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext() (Line: 97)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 181)
Symfony\Component\HttpKernel\HttpKernel->handleRaw() (Line: 76)
Symfony\Component\HttpKernel\HttpKernel->handle() (Line: 53)
Drupal\Core\StackMiddleware\Session->handle() (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle() (Line: 28)
Drupal\Core\StackMiddleware\ContentLength->handle() (Line: 32)
Drupal\big_pipe\StackMiddleware\ContentLength->handle() (Line: 116)
Drupal\page_cache\StackMiddleware\PageCache->pass() (Line: 90)
Drupal\page_cache\StackMiddleware\PageCache->handle() (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle() (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle() (Line: 36)
Drupal\Core\StackMiddleware\AjaxPageState->handle() (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle() (Line: 741)
Drupal\Core\DrupalKernel->handle() (Line: 19)

Am I missing something?

I'm also getting this issue,
For me was after updating the taxonomy manager module.
As the original post, stated also deleted the "vendor" directory and re-run the composer install command, but it didn't work.

My only way to get out of this issue was to reimport the database from previous backup.

Excellent!
Thank you @almadorand and @elc.
The combination of both patches solved the issue.
Thanks!

la558 → created an issue.

Hello,

I was able to overcome all errors by using:

Method #2 define in post #6 ✨ Change require custom libraries to suggestions as a better method with more options Needs work
combined with this patch https://www.drupal.org/files/issues/2024-09-17/taxonomy_manager-3474919-... →
from: https://www.drupal.org/project/taxonomy_manager/issues/3474919 🐛 Form element taxonomy_manager_tree broken Active

Thanks!

Hello,

I was able to overcome all errors by using:

Method #2 define in post #6 ✨ Change require custom libraries to suggestions as a better method with more options Needs work
combined with this patch https://www.drupal.org/files/issues/2024-09-17/taxonomy_manager-3474919-... →
from: https://www.drupal.org/project/taxonomy_manager/issues/3474919 🐛 Form element taxonomy_manager_tree broken Active

Thanks!

Hello,

I was able to overcome all errors by using:

Method #2 define in post #6 ✨ Change require custom libraries to suggestions as a better method with more options Needs work
combined with this patch https://www.drupal.org/files/issues/2024-09-17/taxonomy_manager-3474919-... →
from: https://www.drupal.org/project/taxonomy_manager/issues/3474919 🐛 Form element taxonomy_manager_tree broken Active

Thanks!

Hello,
The patch from #254 → almost resolved the issue.
Whenever I select a second independent facet element, I get:
Uncaught TypeError: settings.facets_views_ajax is undefined

la558 → created an issue.

thanks @pgrandeg for you suggestion.

Although that made the trick and I was able to upgrade taxonomy_manger to 2.0.13

composer update drupal/taxonomy_manager  --with-dependencies

Gathering patches for root package.
Loading composer repositories with package information
Updating dependencies
Lock file operations: 1 install, 1 update, 0 removals
  - Upgrading drupal/taxonomy_manager (2.0.12 => 2.0.13)
  - Locking jquery/fancytree (2.38.3)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 1 install, 1 update, 0 removals
  - Downloading jquery/fancytree (2.38.3)
  - Downloading drupal/taxonomy_manager (2.0.13)
Gathering patches for root package.
Gathering patches for dependencies. This might take a minute.
  - Installing jquery/fancytree (2.38.3): Extracting archive
  - Upgrading drupal/taxonomy_manager (2.0.12 => 2.0.13): Extracting archive
Generating autoload files
59 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
No security vulnerability advisories found.

when attempting to access any of the vocabularies in the "taxonomy manager' page, the site broke
"The website encountered an unexpected error. Try again later."

Watch dog shows:

 php    Error      ArgumentCountError: Too few arguments to function Drupal\taxonomy_manager\TaxonomyManagerHelper::__construct(), 4 passed in  
                                        /Library/WebServer/Documents/dil/web/core/lib/Drupal/Component/D  

So I had to roll back the recommended changes.

thanks.

la558 → created an issue.

@solideogloria
fantastic!
Thank you for clarifying!

Oh,
I think I got it.
Just need to uninstall it either through the web interface (/admin/modules/uninstall) or command line
Webform Algolia Places

thanks for your suggestion.

I'm not sure if I understand you correctly.
Here is the list of the required libraries by "Modules > contrib > webform" listed in the 'compose.librarires.json'

    "require": {
        "algolia/places": "*",
        "choices/choices": "*",
        "codemirror/codemirror": "*",
        "jquery/chosen": "*",
        "jquery/geocomplete": "*",
        "jquery/hotkeys": "*",
        "jquery/icheck": "*",
        "jquery/image-picker": "*",
        "jquery/inputmask": "*",
        "jquery/intl-tel-input": "*",
        "jquery/rateit": "*",
        "jquery/select2": "*",
        "jquery/textcounter": "*",
        "jquery/timepicker": "*",
        "jquery/toggles": "*",
        "popperjs/popperjs": "*",
        "progress-tracker/progress-tracker": "*",
        "signature_pad/signature_pad": "*",
        "svg-pan-zoom/svg-pan-zoom": "*",
        "tabby/tabby": "*",
        "tippyjs/tippyjs": "*"
    },

    "repositories": {
        "algolia.places": {
            "type": "package",
            "package": {
                "name": "algolia/places",
                "version": "1.19.0",
                "type": "drupal-library",
                "extra": {
                    "installer-name": "algolia.places"
                },
                "dist": {
                    "url": "https://registry.npmjs.org/places.js/-/places.js-1.19.0.tgz",
                    "type": "tar"
                },
                "license": "MIT"
            }
        },

Those entries are part of the webform module.

So, do I need to remove those entries -by applying a patch.

Also, how can I know what libraries the 'webform' module needs, so I do not remove the ones that are actually needed by this module?

Hello,
I wonder if there is a way to remove the dependency to algoglia/places in

webform > composer.librarires.json

and any other reference that points to algolia/places.

Thanks!

La558 → created an issue.

Hello,
here is the patch for the 2 lines

diff --git a/core/lib/Drupal/Core/Extension/ExtensionPathResolver.php b/core/lib/Drupal/Core/Extension/ExtensionPathResolver.php
index 5045949a..613d87e0 100644
--- a/core/lib/Drupal/Core/Extension/ExtensionPathResolver.php
+++ b/core/lib/Drupal/Core/Extension/ExtensionPathResolver.php
@@ -55,7 +55,7 @@ class ExtensionPathResolver {
       throw new UnknownExtensionTypeException(sprintf('Extension type %s is unknown.', $type));
     }
     try {
-      return $this->extensionLists[$type]->getPathname($name);
+      return $this->extensionLists[$type]->getPathname($name ?? '');
     }
     catch (UnknownExtensionException $e) {
       // Catch the exception. This will result in triggering an error.
@@ -82,7 +82,7 @@ class ExtensionPathResolver {
    *   If the extension is unknown.
    */
   public function getPath(string $type, string $name): string {
-    return dirname($this->getPathname($type, $name));
+    return dirname($this->getPathname($type, $name) ?? '');
   }
 
 }

It solved for me the issue with the dirname() warning message

Here is my compser.json file

{
    "name": "drupal/recommended-project",
    "description": "Project template for Drupal projects with a relocated document root",
    "type": "project",
    "license": "GPL-2.0-or-later",
    "homepage": "https://www.drupal.org/project/drupal",
    "support": {
        "docs": "https://www.drupal.org/docs/user_guide/en/index.html",
        "chat": "https://www.drupal.org/node/314178"
    },
    "repositories": [
        {
            "type": "composer",
            "url": "https://packages.drupal.org/8"
        }
    ],
    "require": {
        "composer/installers": "^2.0",
        "cweagans/composer-patches": "^1.7",
        "drupal/admin_toolbar": "^3.4",
        "drupal/bootstrap": "^3.30",
        "drupal/core-composer-scaffold": "^10.2",
        "drupal/core-project-message": "^10.2",
        "drupal/core-recommended": "^10.2",
        "drupal/ctools": "^4.0",
        "drupal/facets": "^2.0",
        "drupal/field_group": "^3.4",
        "drupal/field_permissions": "^1.3",
        "drupal/field_report": "^2.1",
        "drupal/fontyourface": "^4.0",
        "drupal/fpa": "^4.0",
        "drupal/search_api": "^1.34",
        "drupal/search_api_autocomplete": "^1.8",
        "drupal/search_api_solr": "^4.3",
        "drupal/simplesamlphp_auth": "^4.0",
        "drupal/taxonomy_manager": "^2.0",
        "drupal/title_length": "^2.0",
        "drupal/token": "^1.14"
    },
    "conflict": {
        "drupal/drupal": "*",
        "symfony/yaml":"6.4.8",
        "symfony/validator":"6.4.8",
        "symfony/string":"6.4.8",
        "symfony/serializer":"6.4.8",
        "symfony/psr-http-message-bridge":"6.4.8",
        "symfony/process":"6.4.8",
        "symfony/mime":"6.4.8",
        "symfony/mailer":"6.4.8",
        "symfony/intl":"6.4.8",
        "symfony/http-kernel":"6.4.8",
        "symfony/http-foundation":"6.4.8",
        "symfony/error-handler":"6.4.8",
        "symfony/dependency-injection":"6.4.8",
        "symfony/console":"6.4.8",
        "symfony/config":"6.4.8",
        "symfony/cache":"6.4.8",
        "symfony/var-exporter":"6.4.8",
        "symfony/var-dumper":"6.4.8",
        "symfony/routing":"6.4.8",
        "symfony/framework-bundle":"6.4.8",
        "symfony/finder":"6.4.8",
        "symfony/filesystem":"6.4.8",
        "symfony/event-dispatcher":"6.4.8"       
    },
    "minimum-stability": "stable",
    "prefer-stable": true,
    "config": {
        "allow-plugins": {
            "composer/installers": true,
            "drupal/core-composer-scaffold": true,
            "drupal/core-project-message": true,
            "phpstan/extension-installer": true,
            "dealerdirect/phpcodesniffer-composer-installer": true,
            "php-http/discovery": true,
            "simplesamlphp/composer-module-installer": true,
            "cweagans/composer-patches": true
        },
        "sort-packages": true
    },
    "extra": {
        "patches": {
            "drupal/core": {
                "Htaccess modifications to override rule for simplesaml directory":"patches/htaccess-simplesaml_v1.patch"
            }
        },
        "drupal-scaffold": {
            "locations": {
                "web-root": "web/"
            }
        },
        "installer-paths": {
            "web/core": [
                "type:drupal-core"
            ],
            "web/libraries/{$name}": [
                "type:drupal-library"
            ],
            "web/modules/contrib/{$name}": [
                "type:drupal-module"
            ],
            "web/profiles/contrib/{$name}": [
                "type:drupal-profile"
            ],
            "web/themes/contrib/{$name}": [
                "type:drupal-theme"
            ],
            "drush/Commands/contrib/{$name}": [
                "type:drupal-drush"
            ],
            "web/modules/custom/{$name}": [
                "type:drupal-custom-module"
            ],
            "web/profiles/custom/{$name}": [
                "type:drupal-custom-profile"
            ],
            "web/themes/custom/{$name}": [
                "type:drupal-custom-theme"
            ]
        },
        "drupal-core-project-message": {
            "include-keys": [
                "homepage",
                "support"
            ],
            "post-create-project-cmd-message": [
                "<bg=blue;fg=white>                                                         </>",
                "<bg=blue;fg=white>  Congratulations, you’ve installed the Drupal codebase  </>",
                "<bg=blue;fg=white>  from the drupal/recommended-project template!          </>",
                "<bg=blue;fg=white>                                                         </>",
                "",
                "<bg=yellow;fg=black>Next steps</>:",
                "  * Install the site: https://www.drupal.org/docs/installing-drupal",
                "  * Read the user guide: https://www.drupal.org/docs/user_guide/en/index.html",
                "  * Get support: https://www.drupal.org/support",
                "  * Get involved with the Drupal community:",
                "      https://www.drupal.org/getting-involved",
                "  * Remove the plugin that prints this message:",
                "      composer remove drupal/core-project-message"
            ]
        }
    },
    "require-dev": {
        "drush/drush": "^12.5"
    }
}

thanks

I run
composer why-not symfony/process 6.4.8
#response#

drupal/recommended-project dev-master conflicts symfony/process (6.4.8) 
Not finding what you were looking for? Try calling `composer update "symfony/process:6.4.8" --dry-run` to get another view on the problem.

run:
composer update "symfony/process:6.4.8" --dry-run
I got the same response as with `composer update` above

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - drupal/recommended-project is present at version dev-master and cannot be modified by Composer
    - drupal/core-recommended 10.2.7 requires symfony/process ~v6.4.0 -> satisfiable by symfony/process[v6.4.8].
    - drupal/recommended-project dev-master conflicts with symfony/process v6.4.8.
    - drupal/core-recommended is locked to version 10.2.7 and an update of this package was not requested.

La558 → created an issue.

Thanks graveplot

I have thought that as well, but I did check all the different symfony packages (23) -as listed above by mark_fullmer, in the 'composer.lock' file, and all of them are set to "version": "v6.4.8"

For example:
"name": "symfony/event-dispatcher",
"version": "v6.4.8",

@mark_fullmer

Thank you for your comment stating how to roll back to previous Symfony version.

I agree with @Berdir that

> but there's nothing we can do about that here.

However, I wonder about something:
I experienced this issue on a brand new installation of Simplesamlphp_auth; however, on none of the other 3 other sites -which already had installed this module, I did not experience any issue after updating to Drupal 10.2.7

I wonder why?

I found a way to downgrade the different Symfony packages and solve the problem - until symfony release a new version that fixes this issue:

https://www.drupal.org/project/simplesamlphp_auth/issues/3452457 💬 Update to Symfony 6.4.8 throws error Active
by mark_fullmer

on your local machine: edit composer.json to add the following under the "conflict": { section:"

conflict": {
    "symfony/yaml":"6.4.8",
    "symfony/validator":"6.4.8",
    "symfony/string":"6.4.8",
    "symfony/serializer":"6.4.8",
    "symfony/psr-http-message-bridge":"6.4.8",
    "symfony/process":"6.4.8",
    "symfony/mime":"6.4.8",
    "symfony/mailer":"6.4.8",
    "symfony/intl":"6.4.8",
    "symfony/http-kernel":"6.4.8",
    "symfony/http-foundation":"6.4.8",
    "symfony/error-handler":"6.4.8",
    "symfony/dependency-injection":"6.4.8",
    "symfony/console":"6.4.8",
    "symfony/config":"6.4.8",
    "symfony/cache":"6.4.8",
    "symfony/var-exporter":"6.4.8",
    "symfony/var-dumper":"6.4.8",
    "symfony/routing":"6.4.8",
    "symfony/framework-bundle":"6.4.8",
    "symfony/finder":"6.4.8",
    "symfony/filesystem":"6.4.8",
    "symfony/event-dispatcher":"6.4.8"
  },

then run composer update to update the composer.lock file -if not it will generate a conflict with composer.lock file

@AaronBauman

I'm hitting that same error;
I wonder how did you roll back to symfony/framework-bundle 6.4.3

I'm not sure where to check with version I'm at.

Thanks

Thanks @Andriy,

uninstalling the module and installing it from scratch 2.0.11 did work.

Hello,
I'm experiencing the same.
SimpleSamlphp is installed with composer as part Drupal

I looked at my databases/tables:

I do not have a " SimpleSAMLphp" database.
and do not have "simpleSAMLphp_kvstore" and "simpleSAMLphp_saml_LogoutStore" tables

however in the Drupal database, I do have:
simplesaml_saml_LogoutStore and
simpleSAMLphp_saml_LogoutStore

Am I missing something?

Thanks for the update.
I was able to successfully update to 2.0.11

However, when accessing the taxonomy manager page and selecting any of the different vocabularies:
admin/structure/taxonomy_manager/voc/

and then selecting any taxonomy term, I get the following error:

Drupal\Component\Plugin\Exception\InvalidPluginDefinitionException: The "taxonomy_term" entity type did not specify a "taxonomy_manager" form class. in Drupal\Core\Entity\EntityTypeManager->getFormObject() (line 209 of /path_to_site/web/core/lib/Drupal/Core/Entity/EntityTypeManager.php).

here is the full back-trace error:

#0 /path_to_drupal_site/web/core/lib/Drupal/Core/Entity/EntityFormBuilder.php(44): Drupal\Core\Entity\EntityTypeManager->getFormObject('taxonomy_term', 'taxonomy_manage...')
#1 /path_to_drupal_site/web/modules/contrib/taxonomy_manager/src/Form/TaxonomyManagerForm.php(366): Drupal\Core\Entity\EntityFormBuilder->getForm(Object(Drupal\taxonomy\Entity\Term), 'taxonomy_manage...')
#2 [internal function]: Drupal\taxonomy_manager\Form\TaxonomyManagerForm->termDataCallback(Array, Object(Drupal\Core\Form\FormState), Object(Symfony\Component\HttpFoundation\Request))
#3 /path_to_drupal_site/web/core/lib/Drupal/Core/Form/FormAjaxResponseBuilder.php(69): call_user_func_array(Array, Array)
#4 /path_to_drupal_site/web/core/lib/Drupal/Core/Form/EventSubscriber/FormAjaxSubscriber.php(112): Drupal\Core\Form\FormAjaxResponseBuilder->buildResponse(Object(Symfony\Component\HttpFoundation\Request), Array, Object(Drupal\Core\Form\FormState), Array)
#5 [internal function]: Drupal\Core\Form\EventSubscriber\FormAjaxSubscriber->onException(Object(Symfony\Component\HttpKernel\Event\ExceptionEvent), 'kernel.exceptio...', Object(Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher))
#6 /path_to_drupal_site/web/core/lib/Drupal/Component/EventDispatcher/ContainerAwareEventDispatcher.php(111): call_user_func(Array, Object(Symfony\Component\HttpKernel\Event\ExceptionEvent), 'kernel.exceptio...', Object(Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher))
#7 /path_to_drupal_site/vendor/symfony/http-kernel/HttpKernel.php(239): Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch(Object(Symfony\Component\HttpKernel\Event\ExceptionEvent), 'kernel.exceptio...')
#8 /path_to_drupal_site/vendor/symfony/http-kernel/HttpKernel.php(91): Symfony\Component\HttpKernel\HttpKernel->handleThrowable(Object(Drupal\Core\Form\FormAjaxException), Object(Symfony\Component\HttpFoundation\Request), 1)
#9 /path_to_drupal_site/web/core/lib/Drupal/Core/StackMiddleware/Session.php(58): Symfony\Component\HttpKernel\HttpKernel->handle(Object(Symfony\Component\HttpFoundation\Request), 1, true)
#10 /path_to_drupal_site/web/core/lib/Drupal/Core/StackMiddleware/KernelPreHandle.php(48): Drupal\Core\StackMiddleware\Session->handle(Object(Symfony\Component\HttpFoundation\Request), 1, true)
#11 /path_to_drupal_site/web/core/lib/Drupal/Core/StackMiddleware/ContentLength.php(28): Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object(Symfony\Component\HttpFoundation\Request), 1, true)
#12 /path_to_drupal_site/web/core/modules/big_pipe/src/StackMiddleware/ContentLength.php(32): Drupal\Core\StackMiddleware\ContentLength->handle(Object(Symfony\Component\HttpFoundation\Request), 1, true)
#13 /path_to_drupal_site/web/core/modules/page_cache/src/StackMiddleware/PageCache.php(106): Drupal\big_pipe\StackMiddleware\ContentLength->handle(Object(Symfony\Component\HttpFoundation\Request), 1, true)
#14 /path_to_drupal_site/web/core/modules/page_cache/src/StackMiddleware/PageCache.php(85): Drupal\page_cache\StackMiddleware\PageCache->pass(Object(Symfony\Component\HttpFoundation\Request), 1, true)
#15 /path_to_drupal_site/web/core/lib/Drupal/Core/StackMiddleware/ReverseProxyMiddleware.php(48): Drupal\page_cache\StackMiddleware\PageCache->handle(Object(Symfony\Component\HttpFoundation\Request), 1, true)
#16 /path_to_drupal_site/web/core/lib/Drupal/Core/StackMiddleware/NegotiationMiddleware.php(51): Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object(Symfony\Component\HttpFoundation\Request), 1, true)
#17 /path_to_drupal_site/web/core/lib/Drupal/Core/StackMiddleware/AjaxPageState.php(36): Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object(Symfony\Component\HttpFoundation\Request), 1, true)
#18 /path_to_drupal_site/web/core/lib/Drupal/Core/StackMiddleware/StackedHttpKernel.php(51): Drupal\Core\StackMiddleware\AjaxPageState->handle(Object(Symfony\Component\HttpFoundation\Request), 1, true)
#19 /path_to_drupal_site/web/core/lib/Drupal/Core/DrupalKernel.php(704): Drupal\Core\StackMiddleware\StackedHttpKernel->handle(Object(Symfony\Component\HttpFoundation\Request), 1, true)
#20 /path_to_drupal_site/web/index.php(19): Drupal\Core\DrupalKernel->handle(Object(Symfony\Component\HttpFoundation\Request))
#21 {main}

If I roll back to v. 2.0.9, the error goes away.

Thanks!

La558 → created an issue.

Hello,
A member from the Islandora community guided me. Here is what I needed to do. In the desired 'content type', I had to create a field -for convenience and consistency, name it "Member of" > machine name: "field_member_of". Here comes the key part, set it up as a Entity reference > Reference type: Content Content type: Repository Item
I still have things to figure out to make it work; however, this would be the response to this question related to "field_member_of"

Ok.

I managed to install Islandora by changing the value from 'stable' to 'dev' in the composer.json file

however, after installation and going into the 'extend' page, I noticed that the 'islandora Advanced Search' is Deprecated.
https://groups.google.com/g/islandora/c/SEOAWJrfE_M

The submodule of Islandora called "Islandora Advanced Search" is being deprecated [per TAG meeting notes where it was decided]. It is being replaced by the independent "Advanced Search" module. This module includes all the code that was in Islandora Advanced Search, and also contains some additional features (including better use of edismax search).

The Islandora Advanced Search submodule will remain in the islandora module's 2.x branch but will be marked deprecated. It will be removed in Islandora 3.x.

To get the current Advanced Search module, use `composer require drupal/advanced_search`. (not a typo; this will download it from its new location on Drupal.org).

Unfortunately there is no way to convert your block placement and other configuration options from Islandora Advanced Search to Advanced Search. If you need help porting your setup, please contact the #support channel on Slack. I sent a query out earlier, and I am not aware of anyone actively using Islandora Advanced Search.

* on Github at https://github.com/Islandora/advanced_search
* on Drupal.org at https://www.drupal.org/project/advanced_search →

So, it looks like the instructions on https://github.com/Islandora/advanced_search/blob/2.x/README.md needs to be updated at least under the installation part from:
composer require islandora/islandora
to
composer require drupal/advanced_search

then, the following should remain.
drush en advanced_search

Under *Configuration* the url should change
from:
admin/config/islandora/advanced_search
to:
/admin/config/search/advanced

Now, can you help me please with the instructions under "Configure Collection Search", I don't seem to see where to find and set "field_member_of" and "field_decedent_of"

Many thanks in advance!

La558 → created an issue.

This patch fixes the error for me
https://www.drupal.org/files/issues/2023-08-16/3336646-function-is-depre... →
Thanks!

I'm on
Drupal Version: 10.2.0
Facets 2.0.6

and after updating to
PHP 8.2.13 (I also tested with PHP 8.3 -> getting the same results as PHP 8.2)

I got multiple deprecated function messages

"Deprecated function: Creation of dynamic property Drupal\facets\Result\Result::$transliterateDisplayValue is deprecated in Drupal\facets\Plugin\facets\processor\DisplayValueWidgetOrderProcessor->sortResults() (line 72)..."

I installed patch fexed-transliterateDisplayValue-15345798.patch
but did not work - composer update was failing to apply the patch, since the sortResults() function in Facets 2.0.6 version is different than the one in the patch (the "get()" function is not defined)

This is my current 'sortResults' function defined in "DisplayValueWidgetOrderProcessor"

  /**
   * {@inheritdoc}
   */
  public function sortResults(Result $a, Result $b) {
    // Get the transliterate values only once.
    if (!isset($a->transliterateDisplayValue)) {
      $a->transliterateDisplayValue = $this->transliteration->removeDiacritics($a->getDisplayValue());
    }
    if (!isset($b->transliterateDisplayValue)) {
      $b->transliterateDisplayValue = $this->transliteration->removeDiacritics($b->getDisplayValue());
    }

    // Return the sort value.
    if ($a->transliterateDisplayValue == $b->transliterateDisplayValue) {
      return 0;
    }
    return strnatcasecmp($a->transliterateDisplayValue, $b->transliterateDisplayValue);
  }

so I tweaked the #5 patch (removing the get() function and make it look like:

-   * {@inheritdoc}
-   */
+ * {@inheritdoc}
+ */
   public function sortResults(Result $a, Result $b) {
     // Get the transliterate values only once.
-    if (!isset($a->transliterateDisplayValue)) {
-      $a->transliterateDisplayValue = $this->transliteration->removeDiacritics($a->getDisplayValue());
+    $transliterateValueA = $a->transliterateDisplayValue;
+    if (!$transliterateValueA) {
+        $transliterateValueA = $this->transliteration->removeDiacritics($a->getDisplayValue());
+        $a->set('transliterateDisplayValue', $transliterateValueA);
     }
-    if (!isset($b->transliterateDisplayValue)) {
-      $b->transliterateDisplayValue = $this->transliteration->removeDiacritics($b->getDisplayValue());
+
+    $transliterateValueB = $b->transliterateDisplayValue;
+    if (!$transliterateValueB) {
+        $transliterateValueB = $this->transliteration->removeDiacritics($b->getDisplayValue());
+        $b->set('transliterateDisplayValue', $transliterateValueB);
     }
 
     // Return the sort value.
-    if ($a->transliterateDisplayValue == $b->transliterateDisplayValue) {
-      return 0;
+    if ($transliterateValueA == $transliterateValueB) {
+        return 0;
     }
-    return strnatcasecmp($a->transliterateDisplayValue, $b->transliterateDisplayValue);
+
+    return strnatcasecmp($transliterateValueA, $transliterateValueB);
   }
 
 }

by doing so, I was able to successfully install the patch through 'composer update'

however, this did not fix the deprecated function message; getting

Deprecated function: Creation of dynamic property Drupal\facets\Result\Result::$transliterateDisplayValue is deprecated in Drupal\facets\Plugin\facets\processor\DisplayValueWidgetOrderProcessor->sortResults() (line 75 ...

La558 → created an issue.

La558 → created an issue.

I'm experiencing the same problem.
After upgrading to Drupal 10.1.0, Boostrap them breaks when 'Bandwidth optimization' for 'CSS' and 'JS' files is checked to 'aggregate'
When aggregation is not selected, the theme loads just fine.
If switching to another theme, such as 'Claro' the interface displays without any issue.

UPDATE

Regardless of how many tweaks I did (different browsers, different database, started from scratch multiple times, changed on mysql variables, etc), it did not work.

What I ended up doing was installing the site using drush command:
https://www.drush.org/11.x/commands/site_install/

So, first install Drupal using composer:
composer create-project drupal/recommended-project project_name

Then created 'files' directories for private and public files and tweaked the settings.php file and made apache the owner, and created a database for the new site.

Up to hear same as before; then installed site with Drush:

cd web
../vendor/bin/drush site:install standard --site-name="site_name" --db-prefix="pref_" --locale=en --site-mail=site@email.com --account-name=account_name --account-mail=site@email.com --account-pass="account_password" --db-url=mysql://db_user:db_pwd@localhost:3306/db_name

I'm all set now.

@cilefen thanks for your response
Globally set max_allowed_packet to 256M (268435456) -client and server side; It did not make any difference, still unable to install drupal on my local.
Getting the same error.

I'm having the same issue while installing D10:

Environment:
Local installation: MacOS Monterey (v. 12.6.3)
PHP 8.1.17
mysql Ver 8.0.30 for macos12 on arm64 (MySQL Community Server - GPL)

Multiple attempts - all getting the same result.
I've tried installing Drupal using Chrome as well as Firefox

Any guidance on how to solve this would be appreciated.

An AJAX HTTP request terminated abnormally.
Debugging information follows.
Path: /core/install.php?rewrite=ok&langcode=en&profile=standard&continue=1&id=1&op=do_nojs&op=do
StatusText: error
ReadyState: 0

Error Page:

Drupal\\Core\\Config\\UnmetDependenciesException: 
Configuration objects provided by standard have unmet dependencies: core.entity_form_display.node.article.default (path), 

user.role.authenticated (shortcut), 

user.role.content_editor (path, toolbar)





in 
/Library/WebServer/Documents/filc2/web/core/lib/Drupal/Core/Config/UnmetDependenciesException.php on line 100 
#0 
/Library/WebServer/Documents/filc2/web/core/lib/Drupal/Core/Config/ConfigInstaller.php(526): Drupal\\Core\\Config\\UnmetDependenciesException::create('standard', Array)\
n#1 
/Library/WebServer/Documents/filc2/web/core/lib/Drupal/Core/ProxyClass/Config/ConfigInstaller.php(132): Drupal\\Core\\Config\\ConfigInstaller->checkConfigurationToInstall('module', 'standard')\
n#2 /Library/WebServer/Documents/filc2/web/core/lib/Drupal/Core/Extension/ModuleInstaller.php(191): Drupal\\Core\\ProxyClass\\Config\\ConfigInstaller->checkConfigurationToInstall('module', 'standard')\
n#3 
/Library/WebServer/Documents/filc2/web/core/lib/Drupal/Core/ProxyClass/Extension/ModuleInstaller.php(83): Drupal\\Core\\Extension\\ModuleInstaller->install(Array, false)\
n#4 
/Library/WebServer/Documents/filc2/web/core/includes/install.core.inc(1657): Drupal\\Core\\ProxyClass\\Extension\\ModuleInstaller->install(Array, false)\
n#5 
/Library/WebServer/Documents/filc2/web/core/includes/install.core.inc(698): install_install_profile(Array)\
n#6 /Library/WebServer/Documents/filc2/web/core/includes/install.core.inc(569): install_run_task(Array, Array)\
n#7 /Library/WebServer/Documents/filc2/web/core/includes/install.core.inc(119): install_run_tasks(Array, NULL)\
n#8 
/Library/WebServer/Documents/filc2/web/core/install.php(48): install_drupal(Object(Composer\\Autoload\\ClassLoader))\
n#9 
{main}, referer: http://filc2.local/core/install.php?rewrite=ok&langcode=en&profile=standard&continue=1&id=1&op=start 

I'm facing this problem as well; unfortunately, none of the above patches worked for me.
Drupal: 9.5.9
PHP: 8.1.17
MySQL: 8.0.30

TypeError: Cannot access offset of type string on string in Drupal\views\Plugin\views\filter\NumericFilter->adminSummary() 
(line 396 of /web/core/modules/views/src/Plugin/views/filter/NumericFilter.php)

Any suggestion?

I've also tested it with the patch #22 from Integration with chosen or select2 → without success.