"Really, content displayed in includelets shouldn't be further sub-divided by embedded HTML, because results are going to be hard to predict and may work or fail depending on the layout/theme selected for the page/portlet."
I agree, I was thinking the same. It could be very hard to predict the results with a complex theme, and even harder to troubleshoot. However, in principle it should be possible, certainly for a simple theme, as long as the various components are 'contained' in div blocks with robust css. So whilst it probably shouldn't be a major selling point, whatever is causing the problem should probably be ironed out.
When I have time I will try to work out what is going on.
I will try the simple content includelet, thankyou. The XoWiki includelet appears to be an includelet for admin functions only.
We are now lucky enough to have gone from having no options to having two ways to achieve includelet driven pages! Having this capability in acs-core feels good. Both Layout-Manager and XoWiki are fantastic tools. The trick will be to find the best ways to utilise them fully without creating a muddle. There is definitely more than enough rope now! 😊
All we need now is a fully CSS compliant Xinha that produces tidy output!
R.
