nessita

> Overall good, it feels like the right length. Two things I noticed when using: > > 1. I wrote “n/a” in the box for the UI changes checkbox because...

Hey @devin13cox, thank you for your work so far! I have restarted my review in this branch/ticket but I have an issue, I'm not being able to reproduce the original...

@devin13cox I spent quite some time debugging why I wasn't able to reproduce. Finally I realized I was trying to reproduce a slightly different issue :facepalm:. We have two bugs...

> Resolved the issue commented on above. :trophy: > Interestingly, the failure was actually caused when using a model with casing like this: `FooBar` I think this is in fact...

> _The update of related objects fails in the admin when the related model has a name in camel case._ > > Do you agree? I don't think we have...

> Hey @nessita, thank you for taking a deep dive into this! I was not aware of the m2m issue, but that makes sense. I can set aside some time...

> Just commenting on this, I've been pretty busy lately so haven't had much time to fix this. Thanks for sharing that. As mentioned before, we understand that contributors work...

> Altered the approach to add the context variable for `RelatedWidgetWrapper` instead of the `Select` widget I like the change of the `data-context` out of `Select` and into `RelatedFieldWidgetWrapper`, though...

@devin13cox As with the other PR, thank you for your patience, I haven't forgotten about this PR either, it's also in my list and I'll get to this ASAP.

As mentioned in the ticket, I think the changes should focus only on updating the "Enabling the sites framework" to reiterate the ability to use `get_current_site`.