hi souhalt
It sounds a musty issue.
Just a simple reason:
Quote:
Some Kinds of Modules:
- XOOPS Search
- WF-Downloads
- RSS Center
- SmartSection
- SmartFAQ
- SmartPartner
and maybe more...
These modules are not well designed.
All modules never break <{$xoops_module_header}>.
At least, all good modules get the previous values by $xoopsTpl->get_template_vars("xoops_module_header") before assigning 'xoops_module_header'.
It's a simple rule for the cooperation.
Though hodaka advocated <{$xoops_block_header}> 2~3 year ago, almost themes don't place such a variable even now.
If you want to use such bad-designed modules with blocks of d3pipes, there are two way.
- Request such developpers to keep xoops_module_header
- Use sync block instead of async block of d3pipes
These are quite a common sense.
You should learn XOOPS more.