@Legoktm: you obviously rearranged this template considerably in the last few days, to use a central JSON data set to store all the data, instead of each template call storing its own data for each each extension and skin. I don't see anything wrong with this new approach - but it does seem very unconventional. Could you explain the thinking behind this change?
Topic on Template talk:Used by
See the original request at Topic:X83vw3ppxaez2iz1.
In general it seems a lot easier for farm/host/package operators since the lists are just in one place to update rather than needing to check and then edit every individual extension/skin page.
Ah, I didn't see that discussion before. Those reasons make sense.