Can you change your subject line to start with "Bug report:"? That might draw a different set of eyes. I think that's how bugs get reported. Those in charge of such things will see if they can reproduce the problem. If so, they will open a bug report.
which value do you see for the p_version_yyyy_mm_dd parameter in the wwv_flow_api.import_begin call at the beginning of your export file? I'm asking, because that #APEX_CSS# ... migration should only be done if we detect a pre-APEX 4.2 export file.
Can you replicate the problem on apex.oracle.com? And which are the exact steps?
My Blog: http://www.inside-oracle-apex.com
APEX Plug-Ins: http://apex.oracle.com/plugins
The version info is: wwv_flow_api.set_version(p_version_yyyy_mm_dd=>'2009.01.12');
This should be wwv_flow_api.set_version(p_version_yyyy_mm_dd=>'2012.01.01');
... but this error is due to a manual modification of the export file.
We parameterise some values, so that the we can use the old-school DEFINE variables in our deploy process via SQL/plus.
One of the developers made a copy-paste error when doing that ...