5
Thanks for the replies
Rowd hits the hammer on the nail when she said that she prefers a generic solution. Ideally, the templates I'm building are generic templates that can be used n different themes. So generic solutions are best.
That brings me to a question about Rowds solution tho, xoImgUrl mimics $xoops_imageurl, which usually points to xoopsroot/themes/
themename/. If I use that in the template, would it know the original image location in xoopsroot/images/icons/ or will it look for the original in the template folder under images/icons/, thereby not overriding, but as biter suggests, changing the path? The only thing that's generic about that solution is that the path is dynamic...?
If I now add a modules/news/images/topics/ folder to my theme folder, I can override the xoopsroot/modules/news/images/topics/ images without changing anything in the templates. If I add an images/icons folder to my theme folder (mimicing the xoopsroot/images/icons/ structure), the override doesn't take effect. Does this only work in module folders?
Herko