iFrame Developer Toolbar Wrong Page Fix

Search for a command to run...

No comments yet. Be the first to comment.
Building on the previous topic of leveraging Liquibase properties to modify APEX installations, we will delve into a companion technique. This one enables users to define as many property files as they wish in the artifact to set it when deploying. T...

Prereqs Latest SQLcl Existing SQLcl Project with an APEX app Note On average, I prefer to keep the same Schema name, APEX Application ID, Workspace Name, and Workspace ID across environments and have separate databases. I understand that this isn...

Situation Recently I was given a seed data file that was generated from SQLcl with a bunch of INSERT statements, and it worked fine in SQL Developer when ran but would fail in SQLcl with the following: SQL> @DEMO_DATA_TABLE.sql Error starting at lin...

There are plenty of good resources explaining how to create custom download links in APEX so I will skip over that part and list a couple here: - https://oracle-base.com/articles/misc/apex-tips-file-download-from-a-button-or-link - https://joelkallma...

Quick Tip for handling the merging of JSON in Oracle Database!

Some times I have had a client request to use iFrames of other APEX pages. One issue I always have is that when doing this, the developer toolbar points to whatever page is being used in the iFrame.
For example, I declared an iFrame on page 1 of my app which has page 2 of my app as its source:
With P1_IFRAME_URL computed as:
apex_util.prepare_url( 'f?p=' || :APP_ID || ':2:' || :APP_SESSION ||'::NO:::');
So when I run page 1 of my app, my developer toolbar now shows the following:

Developer toolbar is pointing to Page 2 when we are on Page 1
Notice that the developer toolbar shows "Edit Page 2" instead of "Edit Page 1". This has to do with how APEX renders modal dialogs. They are iFrames, and APEX is picking this up as the same. This can get very annoying when editing a page as you lose "Quick Edit" and the "Edit Page" functionality.

Modifying the footer of our Standard page template copy
3. Assign it to the iFrame page.
That is it! Now your developer toolbar will be fine and pointing to the parent page. Just note that you want to do this only for pages that will be strictly used as iFrames, otherwise you lose the developer toolbar for them if they are used as a standalone page. Shout out to @jrimblas for showing me this tip!

Developer toolbar is now pointing to Page 1 when we are on Page 1