-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add patch from https://www.drupal.org/project/group/issues/2853001 to… #497
Conversation
… supress warning when creating new content.
@ekes or @stephen-cox can you help me work out why this test is failing? When I test it manually, it behaves as expected. Logging into the control site forwards the user to /admin Logging into a microsite forwards the user to /group/1 So why would the test be behaving differently?
|
If the same code passes locally, and fails here. I think something about the way the test is run meaning that the domain negotiator does not think there is an active domain:-
that's the reason it wouldn't redirect to either admin or the group page. or it getting cached differently I guess in group site tests we set the site, is it not defaulting to having the domain of the control site at other times? How is that set when running the test, environment variables? |
Guess this is where it's setting the domain https://github.com/localgovdrupal/localgov_shared_workflows/blob/5db7a020b4e724a81ac9a4e2750342facba53ee7/.github/workflows/test-microsites.yml#L223 |
So locally it installs with
And during a test the ID is: What is it in the github test, and why isn't it returned if it's the default anyway. What's creating and updating this. |
I think we should merge and release this, and follow up on the odd failing tests on #503 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just read the issue. As I understand it this patch fixes the issue for us for now, but what will finally get merged might be a different approach. But I don't think changing from one to the other is going to be an issue, and people on the issue seem to be happy enough with this approach now too.
This an issue, again!
Just like mentioned here: https://www.drupal.org/project/responsive_preview/issues/3302861
Which takes us back to https://www.drupal.org/project/group/issues/2853001
The latest patch on there seems to suppress the problem.
Steps to reporoduce:
install localgov_microsites 4.0.0 :)
create a microsite and assign an admin user to the microsite
log into microsite as admin user
create a newsroom
See
Error message
Solution: apply this patch https://www.drupal.org/files/issues/2023-09-25/group2-2853001-26.patch