Not able to use @section and Sort within a group in RTF Template

Question

When i try to use sort with for-each-group@section in my template, the Output Post processor is throwing the following exception
Caused by: oracle.xdo.parser.v2.XSLException: <Line 31, Column 84>: XML-22047: (Error) Invalid instantiation of 'xsl:sort' in 'fo:flow' context.
My tags in the RTF template are as below:
<?for-each-group@section:G_PERSON_ID;./DEPT?><?sort:DEPT;'ascending';data-type='text'?>
-- there are 2 more groups within this.
<?end for-each-group?>
I don't get the error if i remove @section from the above tag in my RTF template.
OR
IF i remove the sort tag and keep the @section , it still works.
I need the "sort" so that i can sort the output by department number and I need the "section" so that i can acheieve context based header title for the page using the tag given below in the header area of the word RTF doc. The DEPT number should change as per the data shown in the report.
DEPT <?DEPT?> CLASSIFICATION SENIORITY LISTING BY CLASS CODE & DATE
I am stuck with either being able to use the Sort or the Header feature but not both.
I guess that section is needed for the context based header title to work, because all the data shown in the current page should correspond to only one single DEPT value (to make the Header title consistent with the data). But i dont get why i am not able to sort. The exception from OPP simply beats me. Please help!!
I am using the XML Pub Desktop 5.6.2 to develop my templates.
Is there any way to acheive this? Can someone throw some light on this.
Thanks in advance.

Answer 1

Help About says I'm on 20.0.1
Up until last week, I was able to use the tab key when typing emails and other multi-line text boxes.
Suddenly the behavior of the tab key changed. This isn't the first time. It's been quite a while ago that the function of the tab key changed from indenting to moving around the page, then after some time it changed back to indenting.
Can we get this fixed and leave it alone, please?
I may give one of those add-ins a try, but my problem with add-ins is that they break when FF is patched or upgraded, then I'm left with out the solution they provide.
Can we just fix Firefox, please?
Thanks,
Frank
P.S. Another potential fix I came across suggested starting FF in safe mode to see if the problem goes away. It does not. It seems to be a change to FF that appeared after an update last week. On or just befor 24 Apr.