Let me see if I understand 810 correctly:
810 wrote: [The] bug ... was the module [position that didn't appear in K 4.0 Crypsis. We] have fixed that in the [latest/K 4.0.10] version.
This is what I understand you to have written.
810 wrote: What Rich found has nothing to do with a bug/issue but a feature request.
Well, I know that you and I sometimes disagree about the definition of a bug (or defect or "issue") but I don't think this makes people happy to read that, on the one hand, K 4.0 allows module positions (in the form of kunena_msg_
n) to accommodate placement of modules at every
nth message for
Blue Eagle but does not allow it similarly for those who use
Crypsis.
Therefore, by saying that people need to "customise their
Kunena template" (without providing any tutorial or documentation about the procedure and in the knowledge that these "customisations" will inevitably fail in future when the
internal structures in Kunena are changed
) I don't agree with your assessment that this module position issue is not a defect as you have tried to characterise it.
It is clear from looking at
GitHub
#3687
that this is a bug. At the time of writing #3687 is classed as a bug and that was why I wrote earlier that this topic should be moved to a different category.
All very confusing. It doesn't inspire confidence if people cannot use
Kunena in a "similar" kind of manner whether they use
Crypsis or
Blue Eagle. Leaving that aside, to summarise what you've written: if you want to use
Kunena to place modules after every
nth message posted (relative to the top of the page) use
Blue Eagle; this feature is not supported in
Crypsis.
Crypsis allows the use of module positions at the
nth absolute position (relative to the first message posted in a topic) but does not repeat if a topic spans more than one page.
If I may also summarise my understanding of what has been written, the ability to use relative module positions in
Crypsis—in a similar way to how things have worked with the older (
Blue Eagle) template dating all the way back to K 1.6—is considered by the development team to be a feature request.