Igor Starikov

Thank you. That's interesting, yet it'll require a substantial amount of work and usage of some kind of a decent protocol (e.g. OAuth2) to be more or less secure.

Thank you. Yeah, that looks like a security hole also. We need to extend tests with that case to verify all goes fine.

Hi. Those tags are made to accept both model instances and classes. So if your ``object`` is an instance it should be fine. Have you tried it?

So the behaviour or your custom tag compleately depends on its (tag) implementation. To implement it properly you may want to take a look at how `FieldAttrNode` works.

> but what I want is to effectively skip the check in I'd advise to reformulate the task to make it more easy: "make it not to skip but pass...

> Could you give a brief code example, please? Sorry, have work to do these days. > I'm trying to understand exactly what you mean - you mean my custom...

Sorry for the delay. The following will render help text for `elements` attribute when used with `{% mytag mymodel %}`. ```python @register.tag def mytag(parser, token): return FieldAttrNode( field=f'{token.split_contents()[1]}.elements', attr_name='help_text', tag_name='mytag'...

> But I can't get it to work when called from an inclusion template, or a sub template. 1. Use `as` clause to put tag result into a variable. 2....

Thank you for the report. It might be because using `DEFAULT_AUTO_FIELD` setting globally for your project. Since `AppConfig.default_auto_field` is not defined [yet] for outhost, the global setting is used. That...

That rather would be something like: ``` Article.get_flags_for_types([Article], user=user, status=1) ``` Note here that `get_flags_for_types` exposed in `Article` is only a convenience to access a generic method, so you need...