@tylertech-lee-hazlett

anyone able to approve this so it can be D11 ready?

Found an issue running the tests at the turn of the month for `redirect_404_cron`. Made the compare be `Y-z` instead of `d` because committing code at the turn of the month apparently can cause test failures.

We have a use case for the proposed changes. We have links in the wild that are `/HelloThere`, but `/HelloThere` should also go to `/hellothere`. Making it configurable with the default being case sensitive makes sense to me.

We are using the redirect_domain module portion mostly. so `go.example.com/gohere` and `go.example.com/GoHere` should be the same for our use case.

Moving to Normal priority as a Federal law is coming in 2026 that will fine site owners who don't adhere to Accessibility standards

tylertech-lee-hazlett → created an issue.

neither worked for me.

here is the url for adding a member if anyone needs it: /group/[group:gid]/content/add/group_membership

idk if that's the actual token, [group:gid], but just know that's where the group id goes.

same for me. add member is completely gone. testing the reinstall of group via devel now. if that doesn't work, will try uninstalling group_support_revisions.

tylertech-lee-hazlett → created an issue.

MR 110 is for 8.x-1.x
MR 109 is for 2.0.x

Apologies if I did that wrong.

tylertech-lee-hazlett → made their first commit to this issue’s fork.

tylertech-lee-hazlett → created an issue.

understood. thank you for the module suggestion.

just a thought but maybe in the views ui we could add an option to allow the user to select an additional option of the group to display as

Example:

1. I want to display a grouped set of bootstrap cards
2. I want the grouping to be displayed as accordion so when I expand the accordion, it shows my cards

Example 2:

1. I want to display a grouped set of bootstrap tables
2. I want the group to be displayed as tabs so when I click the tab, it shows the table for the group

This might be the domain_menu_access module that needs fixed.

Hitting the issue as well. It looks like it is assigning by what the user has access to and not the domain.

attached failure verification as proof of the test actually working before adding the fix back in.

Okay, I see. Maybe we missed, unchecking the "Remember domain selection" button when we get configurations in other domains.

Isn't it a multi-user issue though? i.e. if "Remember domain selection" is meant as a GLOBAL config setting, is it global for the user? or global for Drupal?

So if I come in and we need to spin up a new domain and with a specific theme, I need to kick everyone out while I do that or else we end up with split configuration. So every domain specific site change will require everyone to stop what they are working on.

To be fair, we're fairly new to drupal so there may be something I'm missing but it also feels like you're still missing what I'm saying and we're still just misunderstanding each other.

To change block settings for a theme you go to admin/structure/block/list/themename change the domain there and then change the block settings

We don't want this. Please consider this one of our biggest misunderstandings.

I only want the theme and theme settings saved for the domain per the path list I attached. Here it is again for reference. These are all paths that are enabled via the UI so there wasn't anything manually added in here. This works and saves Saved Configurations correctly: system.site, system.theme, system.theme.global.

• /admin/config/system/site-information
• /admin/appearance/settings/swift
• /admin/appearance/settings/pathways
• /admin/appearance/settings/collection
• /admin/appearance/settings
• /admin/appearance

Changing a theme for a domain requires to go to admin/appearance, choosing the domain and then changing the theme

I don't disagree, but you are missing the other steps we have to do: 1, 3, 4, 5 in the workaround. Even with this workaround, we've had an asset injector file end up in Saved Configurations causing the issue which is why 5 is there.

so why the user was going to appearance first then?

So, we discovered this problem by changing the theme for a specific domain. Selecting "Set as Default".

As I kept going, I found it was when I did a specific action that caused the issue. That specific action is

1. when I have "Remember domain selection" on
2. select a new domain on admin/appearance (which causes the reload)
3. turn "Remember domain selection" off
4. going anywhere else in admin and saving a setting

BUT it also happens when (so this would be why a user goes to appearance, to change the theme)

1. I have "Remember domain selection" on
2. select a new domain on admin/appearance (which causes the reload)
3. set a different theme as default for specific domain
4. turn "Remember domain selection" off
5. going anywhere else in admin and saving a setting

After the setting is saved, this is where the block.block.*, assetinjector.css.*, views.*, groups.* is being added to Saved Configurations. We are not expecting this.

Block, Views, Groups and Asset Injector are all items that showed up in Saved Configurations, which is most of what we are working in.

> From my understanding you have tried to achieve domain specific block layout settings

No, it is the theme setting admin/appearance in the domain config list that we are trying to configure for the specific domain configs. I'll update the summary. I've attached the urls in our config in case maybe I'm misunderstanding further.

I am aware admin/structure/block doesn't lead to the same path because we are also seeing some weird behavior there where if we don't switch back to "All domains" and then uncheck "Remember domain selection" then we will see the name of the main tab theme on admin/structure/block say it's using "theme 2" but then in the "demonstrate block region (theme 1)" and all configure/edit blocks urls point to theme 1. Another file attached of what that looks like.

We do have a workaround which is currently:

1. Check "Remember domain selection"
2. Change the theme for a specific domain
3. Select "All Domains" for the theme after changing for specific domain
4. Uncheck "Remember domain selection"
5. Keep an eye on any new entries in /admin/config/domain/config-ui/list for a little bit. delete if found.

Hey Lindsay! I'm in the same boat. I believe the Linkit module itself is going to be the cause of the issue. I see you posted on a few of the issues I was looking at over on that module as well.

I think there is an issue open that should allow a hook to be added and then we can implement a link_domain submodule. But I'm not sure there's currently a way to do it.

Linkit states most of their core features are in D11. I think since it's in core for D11 it's probably more likely to work as intended but I know all your dependencies may not be D11 compatible yet (ours aren't!).

https://www.drupal.org/project/linkit/issues/3366761 ✨ Provide a hook/event for modifying the suggestions list Active

tylertech-lee-hazlett → created an issue.

We have a use case for this with the domain access module. Adding a check to not show content tied to other domains so it'd be under: allowing additional contextual filtering.

I think this issue would fix it though: https://www.drupal.org/project/linkit/issues/3366761 ✨ Provide a hook/event for modifying the suggestions list Active

If a hook gets added, I'd be happy to attempt a linkit_domain module.

They added a hook in the Drupal 7 version: https://git.drupalcode.org/project/linkit/-/commit/4a5a1b87d755089c47982...

I think that was lost in Linkit v6 and the latest 7.

are you still having an issue with this? we are using Radix 6 with tb_megamenu without issues. be happy to share any insights.

in our instance, it seemed to degrade more and more over time until it basically became non-functioning. flushing cache and running cron would work once or twice and then that didn't. fully deleting and recreating became the answer but it'd started to become every edit, we had to delete and recreate.

hitting this on our instance as well. save, settings show on site, not in Edit on the css asset.

will probably rollback to .19 until this is addressed.

was looking for the older ticket to see if it was fixed yet and found yours. i believe this was fixed at least with a patch on #3450485

https://www.drupal.org/files/issues/2024-05-29/3450485-domain-form-build... →

tylertech-lee-hazlett → created an issue.

https://git.drupalcode.org/project/radix/-/merge_requests/107

This would be my first MR for any drupal project so feel free to advise if I've done anything wrong in any drupal workflow regard (and obviously any code issues as well)

tylertech-lee-hazlett → created an issue.

That did fix it. Thank you!

Sorry for the delay, I guess I need to update my notification settings. I will try the edit and save and follow up today.

tylertech-lee-hazlett → created an issue.