-
Notifications
You must be signed in to change notification settings - Fork 96
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
FIX Don't trigger init if already redirected #1830
Conversation
Fixes silverstripe#1829 See issue for context
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.
Code looks good to me.
I'm just running a CI run against 2.2
to double check if the CI failures are pre-existing.
The CI failures aren't happening without this PR. Can you please take a look and see if you can resolve them? |
The CI errors are a bit strange honestly EDIT : ok I see the classes expect to have a default tab class even with an empty session, i'll fix this I think these tests assume too much and should probably be fixed but I haven't had a deeper look at it
|
@GuySartorelli CI is green |
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.
Thanks for updating so the tests pass!
It's a little less clear what's going on now though, so I've requested a change to the comment to make up for that.
Co-authored-by: Guy Sartorelli <[email protected]>
I'm not sure if the |
i can update to "if we've hit the "landing" page or if the model is not valid" i agree it still a bit odd, because you would expect and invalid model to do some kind of errors, but since the model admin class can be instantiated by itself, without a valid user (as designed in the unit tests at the moment), it should still properly return default summary fields for instance |
Probably updating that comment would do IMO, or else adding a 'reset so we use the "landing page"' comment when setting it to |
Given the change freeze corresponding with the 5.3.0-rc1 release is coming in the next few days (if all goes well), @lekoala can you please update the comment as mentioned above? I'll then merge it in if Michal doesn't respond before I click the button. |
@GuySartorelli done |
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.
All good from my perspective now, thanks Thomas!
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.
LGTM, thanks for making that change.
Fixes #1829
See issue for context
Description
Manual testing steps
Issues
Pull request checklist