Could it be that this mechanism doesn't work with extensions like ezwebin?
I've tried again and it doesn't work. Also, I tried to create a very simple content class Abc in the admin interface, and define the node/view/full.tpl for this class, same punishment: it didn't work! Is there a way to see "more" in the template debug output, like what templates it tried before finding the one?
but back to shop/bg_basket.tpl:
My feeling is that even after doing the override through the admin interface, the settings in the extension have stronger precedence, and therefore the shop/basket.tpl would be taken from there... Would it make sense to move the override.ini into the extension/ezwebin/settings folder?..
