Skip to content
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

API Make ElementalAreaController a subclass of FormSchemaController #1273

Merged
merged 1 commit into from
Nov 19, 2024

Conversation

GuySartorelli
Copy link
Member

class ElementalAreaController extends CMSMain
class ElementalAreaController extends FormSchemaController
Copy link
Member Author

@GuySartorelli GuySartorelli Nov 12, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was originally changed from subclassing LeftAndMain to CMSMain in #449

The reasoning was

It makes more sense for ElementalAreaController to inherit from CMSMain rather than LeftAndMain, as this means that permissions are checked in relation to the Page Level rather than for the entire CMS.

Maybe that made sense at the time, but you can have an elemental area on any DataObject including inside a ModelAdmin.... so requiring CMS_ACCESS_CMSMain permissions is just wrong. Instead, require CMS access more generally, and let the model permissions dictate what can and can't be done within the controller.

@GuySartorelli GuySartorelli marked this pull request as ready for review November 14, 2024 21:01
Comment on lines -183 to +185
// Will end up at an HTML page with "Silverstripe - Bad Request"
$this->assertSame('text/html; charset=utf-8', $response->getHeader('Content-type'));
$this->assertStringContainsString('Silverstripe - Bad Request', $response->getBody());
// Gives suitable error message for XHR request
$this->assertStringStartsWith('text/plain', $response->getHeader('Content-type'));
$this->assertStringContainsString('There seems to have been a technical problem', $response->getBody());
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The modal links used to be routed through LeftAndMain which meant the error handling in that class was used. For some reason they weren't picked up as XHR requests so the full HTML error page was being rendered which wasn't really the correct behaviour, but it's what happened.

Now, a simple 400 response (the default one produced when a form's CSRF token is missing) is produced and isn't altered. This is the correct behaviour.

The end result for the user is no change.

@emteknetnz emteknetnz merged commit 2791227 into silverstripe:6 Nov 19, 2024
5 of 17 checks passed
@emteknetnz emteknetnz deleted the pulls/6/formschema branch November 19, 2024 04:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants