I tried with this last week without success (but remember I'm very new to openwisp, django an python).
I couldn't do it with monkey patching the OrgMixin class. If remove from fields, database fails with "organization cannot be NULL" when saving. I did not manage to modify the default value with monkey patching, but yes modifying directly the OrgMixin class. I will try again. El lunes, 24 de agosto de 2020 a las 0:14:22 UTC+2, federico...@gmail.com escribió: > I suggest to simply use one organization and leave everything as is. > > One improvement we can do, and I would welcome that, is to make the > organization selection automatic when the user has access to only one > organization. > I had this in the back of my mind for some time and now I finally created > an issue for it: https://github.com/openwisp/openwisp-users/issues/170 > > If we do this change, you may then just use OPENWISP_ADMIN_THEME_LINKS > <https://github.com/openwisp/openwisp-utils#id12> to supply a custom css > which hides the organization field. > > I think that would be enough and would keep it simple for you. Overriding > that part may cause you unnecessary headaches. > > > On Thursday, August 20, 2020 at 4:05:40 AM UTC-5, pni...@gmail.com wrote: >> >> We want to use Openwisp in the internal network of a company. >> >> Can everything about organizations be removed from the frontend? If >> possible, do not modify the models, simply hide all the fields to select >> organization and that there is an organization in the database. >> >> Would it be possible to do it without having to overwrite all the >> applications? >> > -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to openwisp+unsubscr...@googlegroups.com. To view this discussion on the web, visit https://groups.google.com/d/msgid/openwisp/0a7145e4-1157-4b26-9bd8-5dec9135da48n%40googlegroups.com.
