this is a fairly specific situation but I wondered if anyone could tell me if this is a bug in Apex 18 or not?
I've created a non-authenticated test case for this, i.e. https://apex.oracle.com/pls/apex/f?p=130618:1
You start by creating a module which opens a modal dialog. The way this has to work is that module opens the dialog by means of a simple after processing branch going to "Page or URL (redirect)" which points to a page item that contains the URL to go to. In my case, it's &P0_TEST. This page has a before header process which sets P0_TEST to be a simple URL with &DEBUG. in it, i.e.
:p0_test := apex_util.prepare_url('f?p=130618:2:&SESSION.:INITIALISE:&DEBUG.');
The modal dialog page must have a classic report with PPR set to No but with pagination links (next/prev) defined. When you call the modal dialog, it then has next/previous of the following form:
Next<span class="a-Icon icon-right-arrow"></span>
Notice the bit in bold, the &DEBUG. has not been resolved (although &SESSION. has) and will mean that the request when you click the pagination links will be of the form
and this will fail with mod_plsql's strict validation.
So, is this a bug or is &DEBUG. not supported to be resolved when using it in this way?