Overextends skips the template with different filename even when it would not create a cycle about django-overextends HOT 9 CLOSED

I made a comment on Django ticket. From what I understand this is not possible without code change in Django.

from django-overextends.

Can you provide a complete example somewhere of this not working the way you expect it to?

I'm able to use overextends as a replacement for extends just fine.

from django-overextends.

I've even checked with multiple base templates with the same name in different apps - the one in the app ordered higher in INSTALLED_APPS is always used.

Possibly you're just missing the correct ordering in INSTALLED_APPS?

from django-overextends.

See this example project.

from django-overextends.

Tested with current version of django-overextends and Django 1.4.10.

from django-overextends.

I've taken a closer look now with your example project and see the issue.

overextends called user.html has no way of knowing that it's being called from user.html, which it would need to know to compare to the template name given to overextends, and when different just act like the extends tag without skipping.

I'm gonna close this at this point since it's not a bug and you can achieve what you want using both extends and overextends - one could argue that this is explicit and therefore the right approach anyway.

from django-overextends.

Really? So what should I use if I have user.html extending base.html extending user.html extending base.html?

from django-overextends.

I'm not sure what kind of answer you're expecting, that sounds ridiculously contrived.

Like you said earlier, it's not possible without modification to Django.

from django-overextends.

Of course example is made up, but when you have multiple apps you do not know how exactly they will end up loading. Currently it fails silently, something being skipped.

And of course use cases are those which then make a case for modification to Django.

from django-overextends.