Daniel Ripoll

Ah, i see. Yeah, it's a brand new project, so I guess that's what happens here, it's relying on Django default values then. \-------- Mensaje original -------- On 3 dic....

> The behavior of ujson has always been to try to serialize all objects in > any way possible. That actually makes no sense, if the behaviour of ujson is...

@minsis I tried it, and indeed also tried changing the type of network, but the problem is still the same.

I'll check it as soon as I'm at my office hours, but I think you're maybe having a point on the ipv6, AFAIK we have ipv6 disabled on whole network....

It looks that it's ipv6 fault then, host have ipv6 disabled but somehow docker it's still trying to get ipv6 not 4. So... I guess it's matter of dealing with...

Well, django template parser can normall understand this through templatetags... But somehow any custom templatetag is being ignored here.

OK, basically it looks like Django doesn't like to use database on templatetags. Even it works...

Yup, it is. But if i try to put an ipdb into the templatetag it doesn't get triggered. On the other hand if I try to change from a @register.simple_tag...

Ok, finally figure out how to solve my problem, for anyone interested: ``` from sass_processor.templatetags.sass_tags import SassSrcNode class CustomSassProcessor(SassProcessor): def resolve_path(self, context=None): from resources.models import SiteConfiguration from resources.models import ThemesModel...

So... Any update on this so far?