@simon2d

I am still experiencing this issue.

A workaround was for us to manually delete the URL alias associated the page A. After flushing the cache, the redirect was working correctly.

Experiencing the same behavior here. Our content author raised this to the devs recently. Not sure when this started occuring.

simon2d → created an issue.

Hi all, is there any update on this issue? We are still experiencing it on 10.1.x

Hi all,

Just confirming I'm experiencing the same issue as everyone else is mentioning

We have a custom block with field that is an entity reference media type. When adding a new image, we can only select the image via the checkbox and click insert. But clicking insert swirls for a few seconds and then doesn't attach the image on the page.

This has occurred for us when switching from 10.0.11 to 10.1.0 (or higher, have tested 10.1.6 as well)

Using the dev version, or the patches above has not fixed the issue

Regards
S

Thanks for your comment @cilefen

This is on 10.0.11, not ^10.1. Would it still apply?

I am not seeing any console errors related to the above.

Thanks

simon2d → created an issue.

I'll also add that this seems to be working for some text fields but not for others. Our ckeditor config has not changed under Texts formats and editors

simon2d → created an issue.

I fixed the above issue by changing value for NameIDPolicy in authsources.php to an empty array:

'NameIDPolicy' => []

I also encountered an issue with entityID. We previously had this set to null but seemed like that isn't possible anymore considering the new authsources template. Instead I updated as follows (taking example from #96 but removing the ports):

Before:

// The entity ID of this SP.
// Can be NULL/unset, in which case an entity ID is generated based on the metadata URL.
'entityID' => null,

After:

// The entity ID of this SP.
'entityID' => "https://{$_SERVER['HTTP_HOST']}/simplesaml/module.php/saml/sp/metadata.php/default-sp",

I have now managed to get it working on Drupal 10.0.11 on our develop environment. Thanks for everyones help. I will linger for a bit to see if I can help others.

Hi all, currently getting an error running Drupal 10.0.11:
Uncaught PHP Exception TypeError: "SimpleSAML\Utils\Config\Metadata::parseNameIdPolicy(): Argument #1 ($nameIdPolicy) must be of type ?array, bool given, called in /mnt/www/html/company/vendor/simplesamlphp/simplesamlphp/modules/saml/src/Message.php on line 477" at /mnt/www/html/company/vendor/simplesamlphp/simplesamlphp/src/SimpleSAML/Utils/Config/Metadata.php line 250
In our authsources.php file we have
'NameIDPolicy' => false,
I notice there was a lot of discussion previously about nameidpolicy along with a patch, but seems I cannot apply the patch due to version constraints.
Does anybody have a suggestion on how we can resolve this? Thanks

Hi everyone

Having the same issue mentioned above related to nameidpolicy.

We are running Drupal 10.0.11 with Simplesamlphp_auth ^4

The patch listed above (#49) and fix mentioned specifies using alpha version 5 of simplesamlphp/saml2 however the 2.1 rc1 version of simplesamlphp/simplesamlphp project is locked to saml2 ^4.6

How can we get around this and does anybody have a fix for it?

Downgrading to beta4 seems to have fixed the issues for me. I will use this version in the meantime. Thanks.

Hi seanB, thanks so much for your comments.

Is there a patch to use in the meantime or shall I wait for the changes to be commited?

Kind regards

simon2d → created an issue.

Thanks very much @shelane for your help. I will test and let you know how this works out.

I also observed simplesamlphp_auth can require either simplesamlphp:^1.19||^2.1

Is there a specific reason for this? Will I need to use ^2.1 for drupal 10?

Hi guys, thanks all for your hard work getting this Drupal 9/10 compatible. Just in time!

I have a question. We are using acquia/blt-simplesamlphp:1.0.0 which we used to load the config into our Acquia Cloud. This module requires simplesamlphp_auth:^3.0 thus cannot use the 4.0 version. Is there anything I can do to get around this e.g. loosening the restrictions somehow or overwriting this require from this module?

Currently we are on core 9.5.10 and want to use simplesamlphp_auth:4.x with simplesamlphp:^1.19. From what I can tell it should work but probably will stop working on simplesamlphp:^2 due to the directory (www->public) changes which I understand.

Thanks in advance.

Hi @cilefen thanks for your comment, please bear with me I am not so 'techy'

Checking the console we are getting a bunch of errors using the .once function, which I believe is part of our jquery.

Our scripts.js file is calling this. It looks like we are directly using the jquery from the webform module.

global-styling:
js:
assets/build/js/scripts.js: { scope: footer }
assets/build/js/utils.js: { }
css:
base:
assets/build/css/base/base.theme.css: {}
dependencies:
- webform/libraries.jquery.select2
- webform/webform.element.select2

I am assuming the .once feature has been removed and will possibly require a change of our javascript. Reading into it here: https://www.drupal.org/node/3158256 →

--

I will do some more digging and get back to you. Thanks.

simon2d → created an issue.

simon2d → created an issue.

simon2d → created an issue.