Bug report - apex.confirm

Apex 4.0.2
See http://apex.oracle.com/pls/apex/f?p=24317:79
Both regions have a button that submits the page with the following URL javascript:apex.confirm('Are you sure?',{request:'FOO',showWait:true});The one at the top of the page works fine. But if you scroll all the way to the bottom of the page and click the Submit button, the confirm dialog is shown fine. But the ShowWait indicator and the gray modal/page overlay are not visible, the probably assume that the entire page is visible with no vertical/horizontal scrolling.
Can it be made smarter to show the showWait indicator and overlay on the current page viewport?
Thanks

Override the position property of the apex_wait_popup class - image's parent div
from
.apex_wait_popup {
background-color:#FFFFFF;
border:2px solid #666666;
display:block;
font-size:16px;
left:40%;
padding:5px;
<b>position:absolute;</b>
text-align:center;
top:30%;
width:300px;
z-index:1002;
}to
.apex_wait_popup {
background-color:#FFFFFF;
border:2px solid #666666;
display:block;
font-size:16px;
left:40%;
padding:5px;
<b>position:fixed;</b>
text-align:center;
top:30%;
width:300px;
z-index:1002;

Similar Messages

  • Bug Report APEX 4.2(.1) : Unable to find item ID for item "P3500_RELEASE"

    1. On the Home Page, click the "Settings" wheel in the header of the Team Development region on the right side.
    2. On the Home Page Preferences popup set "Show" to something else as "All" and click [Apply Changes]
    3. Back on the Home Page, in the Team Development region on the right side, click the number next to "Bugs"
    4. ERR-1002 Unable to find item ID for item "P3500_RELEASE" in application "4800".

    Patrick -
    I decided to drop back and implement the demo to change the email address on my EBS login per the 2015 white paper.
    Something is definitely wrong here..
    The FND: APEX URL Profile option is set to: http://appstest4.fubar.com:7001/ords
    The Function to call the pag is set toe: GWY.jsp?targetAppType=APEX&p=110:1:::::EBS_RESP_ID, EBS_APP_ID,EBS_SEC_GROUP:[RESPONSIBILITY_ID],[RESP_APPL_ID],[SECURITY_GROUP_ID]
    When I call the page though, the URL is http://appstest4.fubar.com:7001/ords/f?p=110:LOGIN_DESKTOP::::::
    Is is possible the jsp is not the correct one?

  • Bug report - hidden confirmation buttons in HDR on 13" display

    For the HDR Pro function, hidden buttons 'OK' and 'Cancel' on Macbook Pro 13" running Snow Leopard and Photoshop CS5.
    Of course I can use the 'esc' key for 'Cancel' and 'return' key for 'OK' - but this is still annoying.
    See image below to illustrate this:

    My display resolution is 1280x800 (like any 13.3" makbooks by apple) so it should have been fine - the image attached has the window magnified to full screen (on Mac, that means between the dock and the upper status bar). On a 1600x1200 external display the buttons show up fine.
    I also tried playing a bit with the window while hiding the dock, and got interesting results:
    If the dock is hidden when I launch the "Merge to HDR...", the 'Cancel' and 'OK' buttons are showing up fine. Then, I can un-hide the dock and they would still appear fine within the scaled down window
    If the dock is not hidden when I launch the "Merge to HDR...", the buttons are missing. If I hide the dock at this stage the buttons would still be missing (showing only about one pixel of the top of those buttons).
    So, maybe the dock takes just enough pixels to reduce the overall available screen resolution to less than 768, but I believe this is a bug - especially since those computers with that resolution (i.e. 13.3" Macbooks running MacOSX) are widely in use and considered pro, I think it should be supported without such glitches.
    Thanks,

  • Re: BUG? APEX 4.0: ORA-20503 error editing report with 400+ columns

    Hello Everyone.
    I've run into something quite strange and am hoping you can help me.
    I am using Apex 4.0.1 and Oracle version 10.2.0.5. I've created a "classical" report in which the underlying SQL is a very simple:
    select * from pvtabThe Oracle table pvtab consists of 419 columns, all of which are varchar2(88) and number type. That's it.
    When I run the report, al of the columns show up as expected.
    However, when I go into the "Report Attributes" tab and click on one of the fields (any of them, it doesn't matter which one), I immediately get the following error:
    ORA-20503: Current version of data in database has changed since user initiated update process. current checksum = "598CAA7B68746A66F4B99E1512C36DED" application checksum = "0"If if replace the "*" with a few actual column names, then I am able to access any of these columns without problem.
    If I put back the "*", I then encounter this error again.
    I have never seen this error with other SQL SELECT statements in which I use the "*" qualifier to retrieve all columns from the table.
    And so, I am wondering if the error is caused because of the large number of columns (419) in my table.
    I've seen this same error mentioned in connection with forms but never with a report.
    So, is there some limit to the number of columns one can have in a "classic" or interactive report?
    Any idea why I would be getting this error?
    Here is the DDL for my table pvtab:
    CREATE TABLE  "PVTAB"
       (     "MICRO" VARCHAR2(4),
         "PRIM" VARCHAR2(4),
         "UNIT" NUMBER,
         "SEC_REF_1" NUMBER,
         "SECN_1" VARCHAR2(88),
         "SEC_REF_2" NUMBER,
         "SECN_2" VARCHAR2(88),
         "SEC_REF_3" NUMBER,
         "SECN_3" VARCHAR2(88),
         "SEC_REF_4" NUMBER,
         "SECN_4" VARCHAR2(88),
         "SEC_REF_5" NUMBER,
         "SECN_5" VARCHAR2(88),
         "SEC_REF_6" NUMBER,
         "SECN_6" VARCHAR2(88),
         "SEC_REF_7" NUMBER,
         "SECN_7" VARCHAR2(88),
         "SEC_REF_8" NUMBER,
         "SECN_8" VARCHAR2(88),
         "SEC_REF_9" NUMBER,
         "SECN_9" VARCHAR2(88),
         "SEC_REF_10" NUMBER,
         "SECN_10" VARCHAR2(88),
         "SEC_REF_11" NUMBER,
         "SECN_11" VARCHAR2(88),
         "SEC_REF_12" NUMBER,
         "SECN_12" VARCHAR2(88),
         "SEC_REF_13" NUMBER,
         "SECN_13" VARCHAR2(88),
         "SEC_REF_14" NUMBER,
         "SECN_14" VARCHAR2(88),
         "SEC_REF_15" NUMBER,
         "SECN_15" VARCHAR2(88),
         "SEC_REF_16" NUMBER,
         "SECN_16" VARCHAR2(88),
         "SEC_REF_17" NUMBER,
         "SECN_17" VARCHAR2(88),
         "SEC_REF_18" NUMBER,
         "SECN_18" VARCHAR2(88),
         "SEC_REF_19" NUMBER,
         "SECN_19" VARCHAR2(88),
         "SEC_REF_20" NUMBER,
         "SECN_20" VARCHAR2(88),
         "SEC_REF_21" NUMBER,
         "SECN_21" VARCHAR2(88),
         "SEC_REF_22" NUMBER,
         "SECN_22" VARCHAR2(88),
         "SEC_REF_23" NUMBER,
         "SECN_23" VARCHAR2(88),
         "SEC_REF_24" NUMBER,
         "SECN_24" VARCHAR2(88),
         "SEC_REF_25" NUMBER,
         "SECN_25" VARCHAR2(88),
         "SEC_REF_26" NUMBER,
         "SECN_26" VARCHAR2(88),
         "SEC_REF_27" NUMBER,
         "SECN_27" VARCHAR2(88),
         "SEC_REF_28" NUMBER,
         "SECN_28" VARCHAR2(88),
         "SEC_REF_29" NUMBER,
         "SECN_29" VARCHAR2(88),
         "SEC_REF_30" NUMBER,
         "SECN_30" VARCHAR2(88),
         "SEC_REF_31" NUMBER,
         "SECN_31" VARCHAR2(88),
         "SEC_REF_32" NUMBER,
         "SECN_32" VARCHAR2(88),
         "SEC_REF_33" NUMBER,
         "SECN_33" VARCHAR2(88),
         "SEC_REF_34" NUMBER,
         "SECN_34" VARCHAR2(88),
         "SEC_REF_35" NUMBER,
         "SECN_35" VARCHAR2(88),
         "SEC_REF_36" NUMBER,
         "SECN_36" VARCHAR2(88),
         "SEC_REF_37" NUMBER,
         "SECN_37" VARCHAR2(88),
         "SEC_REF_38" NUMBER,
         "SECN_38" VARCHAR2(88),
         "SEC_REF_39" NUMBER,
         "SECN_39" VARCHAR2(88),
         "SEC_REF_40" NUMBER,
         "SECN_40" VARCHAR2(88),
         "SEC_REF_41" NUMBER,
         "SECN_41" VARCHAR2(88),
         "SEC_REF_42" NUMBER,
         "SECN_42" VARCHAR2(88),
         "SEC_REF_43" NUMBER,
         "SECN_43" VARCHAR2(88),
         "SEC_REF_44" NUMBER,
         "SECN_44" VARCHAR2(88),
         "SEC_REF_45" NUMBER,
         "SECN_45" VARCHAR2(88),
         "SEC_REF_46" NUMBER,
         "SECN_46" VARCHAR2(88),
         "SEC_REF_47" NUMBER,
         "SECN_47" VARCHAR2(88),
         "SEC_REF_48" NUMBER,
         "SECN_48" VARCHAR2(88),
         "SEC_REF_49" NUMBER,
         "SECN_49" VARCHAR2(88),
         "SEC_REF_50" NUMBER,
         "SECN_50" VARCHAR2(88),
         "SEC_REF_51" NUMBER,
         "SECN_51" VARCHAR2(88),
         "SEC_REF_52" NUMBER,
         "SECN_52" VARCHAR2(88),
         "SEC_REF_53" NUMBER,
         "SECN_53" VARCHAR2(88),
         "SEC_REF_54" NUMBER,
         "SECN_54" VARCHAR2(88),
         "SEC_REF_55" NUMBER,
         "SECN_55" VARCHAR2(88),
         "SEC_REF_56" NUMBER,
         "SECN_56" VARCHAR2(88),
         "SEC_REF_57" NUMBER,
         "SECN_57" VARCHAR2(88),
         "SEC_REF_58" NUMBER,
         "SECN_58" VARCHAR2(88),
         "SEC_REF_59" NUMBER,
         "SECN_59" VARCHAR2(88),
         "SEC_REF_60" NUMBER,
         "SECN_60" VARCHAR2(88),
         "SEC_REF_61" NUMBER,
         "SECN_61" VARCHAR2(88),
         "SEC_REF_62" NUMBER,
         "SECN_62" VARCHAR2(88),
         "SEC_REF_63" NUMBER,
         "SECN_63" VARCHAR2(88),
         "SEC_REF_64" NUMBER,
         "SECN_64" VARCHAR2(88),
         "SEC_REF_65" NUMBER,
         "SECN_65" VARCHAR2(88),
         "SEC_REF_66" NUMBER,
         "SECN_66" VARCHAR2(88),
         "SEC_REF_67" NUMBER,
         "SECN_67" VARCHAR2(88),
         "SEC_REF_68" NUMBER,
         "SECN_68" VARCHAR2(88),
         "SEC_REF_69" NUMBER,
         "SECN_69" VARCHAR2(88),
         "SEC_REF_70" NUMBER,
         "SECN_70" VARCHAR2(88),
         "SEC_REF_71" NUMBER,
         "SECN_71" VARCHAR2(88),
         "SEC_REF_72" NUMBER,
         "SECN_72" VARCHAR2(88),
         "SEC_REF_73" NUMBER,
         "SECN_73" VARCHAR2(88),
         "SEC_REF_74" NUMBER,
         "SECN_74" VARCHAR2(88),
         "SEC_REF_75" NUMBER,
         "SECN_75" VARCHAR2(88),
         "SEC_REF_76" NUMBER,
         "SECN_76" VARCHAR2(88),
         "SEC_REF_77" NUMBER,
         "SECN_77" VARCHAR2(88),
         "SEC_REF_78" NUMBER,
         "SECN_78" VARCHAR2(88),
         "SEC_REF_79" NUMBER,
         "SECN_79" VARCHAR2(88),
         "SEC_REF_80" NUMBER,
         "SECN_80" VARCHAR2(88),
         "SEC_REF_81" NUMBER,
         "SECN_81" VARCHAR2(88),
         "SEC_REF_82" NUMBER,
         "SECN_82" VARCHAR2(88),
         "SEC_REF_83" NUMBER,
         "SECN_83" VARCHAR2(88),
         "SEC_REF_84" NUMBER,
         "SECN_84" VARCHAR2(88),
         "SEC_REF_85" NUMBER,
         "SECN_85" VARCHAR2(88),
         "SEC_REF_86" NUMBER,
         "SECN_86" VARCHAR2(88),
         "SEC_REF_87" NUMBER,
         "SECN_87" VARCHAR2(88),
         "SEC_REF_88" NUMBER,
         "SECN_88" VARCHAR2(88),
         "SEC_REF_89" NUMBER,
         "SECN_89" VARCHAR2(88),
         "SEC_REF_90" NUMBER,
         "SECN_90" VARCHAR2(88),
         "SEC_REF_91" NUMBER,
         "SECN_91" VARCHAR2(88),
         "SEC_REF_92" NUMBER,
         "SECN_92" VARCHAR2(88),
         "SEC_REF_93" NUMBER,
         "SECN_93" VARCHAR2(88),
         "SEC_REF_94" NUMBER,
         "SECN_94" VARCHAR2(88),
         "SEC_REF_95" NUMBER,
         "SECN_95" VARCHAR2(88),
         "SEC_REF_96" NUMBER,
         "SECN_96" VARCHAR2(88),
         "SEC_REF_97" NUMBER,
         "SECN_97" VARCHAR2(88),
         "SEC_REF_98" NUMBER,
         "SECN_98" VARCHAR2(88),
         "SEC_REF_99" NUMBER,
         "SECN_99" VARCHAR2(88),
         "SEC_REF_100" NUMBER,
         "SECN_100" VARCHAR2(88),
         "SEC_REF_101" NUMBER,
         "SECN_101" VARCHAR2(88),
         "SEC_REF_102" NUMBER,
         "SECN_102" VARCHAR2(88),
         "SEC_REF_103" NUMBER,
         "SECN_103" VARCHAR2(88),
         "SEC_REF_104" NUMBER,
         "SECN_104" VARCHAR2(88),
         "SEC_REF_105" NUMBER,
         "SECN_105" VARCHAR2(88),
         "SEC_REF_106" NUMBER,
         "SECN_106" VARCHAR2(88),
         "SEC_REF_107" NUMBER,
         "SECN_107" VARCHAR2(88),
         "SEC_REF_108" NUMBER,
         "SECN_108" VARCHAR2(88),
         "SEC_REF_109" NUMBER,
         "SECN_109" VARCHAR2(88),
         "SEC_REF_110" NUMBER,
         "SECN_110" VARCHAR2(88),
         "SEC_REF_111" NUMBER,
         "SECN_111" VARCHAR2(88),
         "SEC_REF_112" NUMBER,
         "SECN_112" VARCHAR2(88),
         "SEC_REF_113" NUMBER,
         "SECN_113" VARCHAR2(88),
         "SEC_REF_114" NUMBER,
         "SECN_114" VARCHAR2(88),
         "SEC_REF_115" NUMBER,
         "SECN_115" VARCHAR2(88),
         "SEC_REF_116" NUMBER,
         "SECN_116" VARCHAR2(88),
         "SEC_REF_117" NUMBER,
         "SECN_117" VARCHAR2(88),
         "SEC_REF_118" NUMBER,
         "SECN_118" VARCHAR2(88),
         "SEC_REF_119" NUMBER,
         "SECN_119" VARCHAR2(88),
         "SEC_REF_120" NUMBER,
         "SECN_120" VARCHAR2(88),
         "SEC_REF_121" NUMBER,
         "SECN_121" VARCHAR2(88),
         "SEC_REF_122" NUMBER,
         "SECN_122" VARCHAR2(88),
         "SEC_REF_123" NUMBER,
         "SECN_123" VARCHAR2(88),
         "SEC_REF_124" NUMBER,
         "SECN_124" VARCHAR2(88),
         "SEC_REF_125" NUMBER,
         "SECN_125" VARCHAR2(88),
         "SEC_REF_126" NUMBER,
         "SECN_126" VARCHAR2(88),
         "SEC_REF_127" NUMBER,
         "SECN_127" VARCHAR2(88),
         "SEC_REF_128" NUMBER,
         "SECN_128" VARCHAR2(88),
         "SEC_REF_129" NUMBER,
         "SECN_129" VARCHAR2(88),
         "SEC_REF_130" NUMBER,
         "SECN_130" VARCHAR2(88),
         "SEC_REF_131" NUMBER,
         "SECN_131" VARCHAR2(88),
         "SEC_REF_132" NUMBER,
         "SECN_132" VARCHAR2(88),
         "SEC_REF_133" NUMBER,
         "SECN_133" VARCHAR2(88),
         "SEC_REF_134" NUMBER,
         "SECN_134" VARCHAR2(88),
         "SEC_REF_135" NUMBER,
         "SECN_135" VARCHAR2(88),
         "SEC_REF_136" NUMBER,
         "SECN_136" VARCHAR2(88),
         "SEC_REF_137" NUMBER,
         "SECN_137" VARCHAR2(88),
         "SEC_REF_138" NUMBER,
         "SECN_138" VARCHAR2(88),
         "SEC_REF_139" NUMBER,
         "SECN_139" VARCHAR2(88),
         "SEC_REF_140" NUMBER,
         "SECN_140" VARCHAR2(88),
         "SEC_REF_141" NUMBER,
         "SECN_141" VARCHAR2(88),
         "SEC_REF_142" NUMBER,
         "SECN_142" VARCHAR2(88),
         "SEC_REF_143" NUMBER,
         "SECN_143" VARCHAR2(88),
         "SEC_REF_144" NUMBER,
         "SECN_144" VARCHAR2(88),
         "SEC_REF_145" NUMBER,
         "SECN_145" VARCHAR2(88),
         "SEC_REF_146" NUMBER,
         "SECN_146" VARCHAR2(88),
         "SEC_REF_147" NUMBER,
         "SECN_147" VARCHAR2(88),
         "SEC_REF_148" NUMBER,
         "SECN_148" VARCHAR2(88),
         "SEC_REF_149" NUMBER,
         "SECN_149" VARCHAR2(88),
         "SEC_REF_150" NUMBER,
         "SECN_150" VARCHAR2(88),
         "SEC_REF_151" NUMBER,
         "SECN_151" VARCHAR2(88),
         "SEC_REF_152" NUMBER,
         "SECN_152" VARCHAR2(88),
         "SEC_REF_153" NUMBER,
         "SECN_153" VARCHAR2(88),
         "SEC_REF_154" NUMBER,
         "SECN_154" VARCHAR2(88),
         "SEC_REF_155" NUMBER,
         "SECN_155" VARCHAR2(88),
         "SEC_REF_156" NUMBER,
         "SECN_156" VARCHAR2(88),
         "SEC_REF_157" NUMBER,
         "SECN_157" VARCHAR2(88),
         "SEC_REF_158" NUMBER,
         "SECN_158" VARCHAR2(88),
         "SEC_REF_159" NUMBER,
         "SECN_159" VARCHAR2(88),
         "SEC_REF_160" NUMBER,
         "SECN_160" VARCHAR2(88),
         "SEC_REF_161" NUMBER,
         "SECN_161" VARCHAR2(88),
         "SEC_REF_162" NUMBER,
         "SECN_162" VARCHAR2(88),
         "SEC_REF_163" NUMBER,
         "SECN_163" VARCHAR2(88),
         "SEC_REF_164" NUMBER,
         "SECN_164" VARCHAR2(88),
         "SEC_REF_165" NUMBER,
         "SECN_165" VARCHAR2(88),
         "SEC_REF_166" NUMBER,
         "SECN_166" VARCHAR2(88),
         "SEC_REF_167" NUMBER,
         "SECN_167" VARCHAR2(88),
         "SEC_REF_168" NUMBER,
         "SECN_168" VARCHAR2(88),
         "SEC_REF_169" NUMBER,
         "SECN_169" VARCHAR2(88),
         "SEC_REF_170" NUMBER,
         "SECN_170" VARCHAR2(88),
         "SEC_REF_171" NUMBER,
         "SECN_171" VARCHAR2(88),
         "SEC_REF_172" NUMBER,
         "SECN_172" VARCHAR2(88),
         "SEC_REF_173" NUMBER,
         "SECN_173" VARCHAR2(88),
         "SEC_REF_174" NUMBER,
         "SECN_174" VARCHAR2(88),
         "SEC_REF_175" NUMBER,
         "SECN_175" VARCHAR2(88),
         "SEC_REF_176" NUMBER,
         "SECN_176" VARCHAR2(88),
         "SEC_REF_177" NUMBER,
         "SECN_177" VARCHAR2(88),
         "SEC_REF_178" NUMBER,
         "SECN_178" VARCHAR2(88),
         "SEC_REF_179" NUMBER,
         "SECN_179" VARCHAR2(88),
         "SEC_REF_180" NUMBER,
         "SECN_180" VARCHAR2(88),
         "SEC_REF_181" NUMBER,
         "SECN_181" VARCHAR2(88),
         "SEC_REF_182" NUMBER,
         "SECN_182" VARCHAR2(88),
         "SEC_REF_183" NUMBER,
         "SECN_183" VARCHAR2(88),
         "SEC_REF_184" NUMBER,
         "SECN_184" VARCHAR2(88),
         "SEC_REF_185" NUMBER,
         "SECN_185" VARCHAR2(88),
         "SEC_REF_186" NUMBER,
         "SECN_186" VARCHAR2(88),
         "SEC_REF_187" NUMBER,
         "SECN_187" VARCHAR2(88),
         "SEC_REF_188" NUMBER,
         "SECN_188" VARCHAR2(88),
         "SEC_REF_189" NUMBER,
         "SECN_189" VARCHAR2(88),
         "SEC_REF_190" NUMBER,
         "SECN_190" VARCHAR2(88),
         "SEC_REF_191" NUMBER,
         "SECN_191" VARCHAR2(88),
         "SEC_REF_192" NUMBER,
         "SECN_192" VARCHAR2(88),
         "SEC_REF_193" NUMBER,
         "SECN_193" VARCHAR2(88),
         "SEC_REF_194" NUMBER,
         "SECN_194" VARCHAR2(88),
         "SEC_REF_195" NUMBER,
         "SECN_195" VARCHAR2(88),
         "SEC_REF_196" NUMBER,
         "SECN_196" VARCHAR2(88),
         "SEC_REF_197" NUMBER,
         "SECN_197" VARCHAR2(88),
         "SEC_REF_198" NUMBER,
         "SECN_198" VARCHAR2(88),
         "SEC_REF_199" NUMBER,
         "SECN_199" VARCHAR2(88),
         "SEC_REF_200" NUMBER,
         "SECN_200" VARCHAR2(88),
         "SEC_REF_201" NUMBER,
         "SECN_201" VARCHAR2(88),
         "SEC_REF_202" NUMBER,
         "SECN_202" VARCHAR2(88),
         "SEC_REF_203" NUMBER,
         "SECN_203" VARCHAR2(88),
         "SEC_REF_204" NUMBER,
         "SECN_204" VARCHAR2(88),
         "SEC_REF_205" NUMBER,
         "SECN_205" VARCHAR2(88),
         "SEC_REF_206" NUMBER,
         "SECN_206" VARCHAR2(88),
         "SEC_REF_207" NUMBER,
         "SECN_207" VARCHAR2(88),
         "SEC_REF_208" NUMBER,
         "SECN_208" VARCHAR2(88)
       );Thank you for any help/advice.
    Elie
    Edited by: EEG on Jun 12, 2011 2:09 PM

    So, is there some limit to the number of columns one can have in a "classic" or interactive report?Yes. See Oracle® Application Express Application Builder User's Guide Release 4.0, Appendix B: Oracle Application Express Limits.
    Any idea why I would be getting this error?No, but I've replicated it in APEX 4.0.2.00.07 on 11.2.0.1.0 EE using a table of 420 <tt>varchar2(88)</tt> columns:
    >
    ORA-20503: Current version of data in database has changed since user initiated update process. current checksum = "50C9BDC0AA1AEF0EB272E9158B2117B4" application checksum = "0"
    >
    Happens whether using <tt>select *</tt> or including all column names in the query. (I know you don't want to type all the column names, but I'd never use <tt>select *</tt> in a production application: always use a proper column list. You can get one without typing by drag-and-drop of a table in most IDEs, or a query from <tt>user_tab_columns</tt>.)
    I hit the problem at 274 columns. Such an arbitrary number leads me to think that the problem is not one of the number of columns per se, but is due to some other limit (possibly a 32K VARCHAR2/RAW buffer somewhere).
    Workaround:
    Updates to the report column attributes are actually being saved, and you can navigate them using the Page Definition tree view as described in Appendix B.
    Getting More Help:
    This is probably a bug. If you have a support agreement with Oracle raise an SR with Oracle Support.
    Also:
    <li>Search the forum using the "ORA-20503" code and other possible terms to see if there's anything relevant. I had a quick look but the only thread in this context recommended an upgrade on an Oracle 9 DB version that's not compatible with APEX 4.0.
    <li>To get the attention of the Oracle APEX team or anyone else who may know more about this problem than we do, edit your original post and change the Subject to be more specific about the actual nature of the problem: <em>BUG? APEX 4.0: ORA-20503 error editing report with 400+ columns</em>, and include your database version/edition and the definition of the <tt>PVTAB</tt> table.
    Finally:
    Somebody's bound to ask, so we might as well get started:
    <li>Why so many columns?
    <li>What requirement is this trying to fulfil?

  • Bug report: Safari 5 fails to handle 8192 bit RSA certificates

    Running Safari 5.1.7 on OS X 10.6.8 -- I haven't confirmed for the version of Safari running on 10.7 -- and trying to access a site over https that uses an 8192 bits large RSA cert causes Safari to bug out. It can't display the certificate details correctly, giving just a garbled text output, and even a buggy interface dialog, and manually trying to accept the certificate to get the website to load causes Safari to run in an endless loop, displaying the certificate warning anew, over and over, making it impossible to load the page. The exact same certificate details put in a 4096 bit cert works just fine.
    Could anyone in the core dev team take a look at this? The number of sites making use of 8192 bit large certs is growing, and Safari is the only browser out there that can't handle it.
    add.: it seems the problem sits at a more fundamental level than in Safari, possibly in some underlying framework - apparently several other applications in OS X fails with handling an RSA cert of 8192 bits size, as mentioned in this thread: https://discussions.apple.com/message/11728527
    Possibly related: https://discussions.apple.com/message/3650856

    Could anyone in the core dev team take a look at this? The number of sites making use of 8192 bit large certs is growing, and Safari is the only browser out there that can't handle it.
    It might be worth registering (for free) as an Apple Developer:
    http://developer.apple.com/programs/register/
    ... and then you can use the Bug Reporter to submit trackable bug reports:
    http://developer.apple.com/bugreporter/

  • Possible Bug In Apex 4.0.2

    Hi Everyone.
    I would like to report what I think is a bug in Apex 4.0.2.
    If you go to my workspace on apex.oracle.com:
    Workspace = EEG
    Username = [email protected]
    Password = galaxy (all lowercase)
    Run the application: 37796 - Elie_Various_Goodies [no credentials are required]
    This app was imported from my 4.0.1 workspace at my job. On the page I created two Date Picker items, P1_BEGIN_DATE and P1_END_DATE. I set them up so that whenever a user selects a begin date, a dynamic action "MANAGE_DATES" fires and automatically sets P1_END_DATE to this selected begin date value. Now when a user goes to select an end date, the displayed calendar starts at the previously selected begin date rather than the default of "Today".
    All of this worked fine on my office (4.0.1) workspace. However, after exporting this app and then importing onto apex.oracle.com, none of this functionality would work. Even worse, whenever I try to select a begin date or even an end date, the selected dates never make it into the date picker fields. Displaying the "Session" window shows these fields as empty.
    It was only after I copied the two date picker fields and also re-created my dynamic action (P1_BEGIN_DATE2, P1_END_DATE2, MANAGE_DATES) did my functionality return.
    This behavior is quite strange. I can only think this is some sort of bug attributed to the export/import process when exporting a 4.0.1 app into a 4.0.2 workspace. I am not sure if this bizarre behavior happens with non-date picker items. Nor am I sure if this beavior would be repeated if I export/import from 4.0.2 into the another 4.0.2 environment.
    Another strange thing I noticed. If I change my date picker items to be "date picker (classic)" type items, the dynamic action does not work at all. This is true in both 4.0.2 and 4.0.1. I'm not sure if this a bug or not. It could be that the classic date picker is just not "javascript" enabled so to speak. If that is true, then it would have been nice if the docs would have warned us about this.
    Has anyone else seen this behavior?
    Thank you.
    Elie

    Hi Joel.
    First let me thank you for the warning about allowing "everyone" access to my workspace.
    You're correct, of course. Anyone could destroy anything within my workspace. I guess I was too trusting especially as I have seen many posts on the Forum where others have given access to their workspace so that responders can offer help. I really should be more discreet about this. Again, thank you. Needless to say, I have changed my password.
    With respect to the possible bug, the MANAGE_DATES dynamic action is intended to be a submit page because that is the only way I can see to get BOTH the P1_END_DATE date picker item as well as the end date textual field to be assigned the selected P1_BEGIN_DATE. I tried to use a dynamic action in which javascript sets the value of the end date textual field to the selected P1_BEGIN_DATE value. This works without the need to submit the page. Unfortunately, this does not cause the P1_END_DATE date picker item to default to this value. Instead, the default remains at today's date. This is why I finally resorted to a dynamic action that submits the page whenever a new value is selected (that is, a "change" event) from the P1_BEGIN_DATE date picker item.
    All of this works in my office 4.0.1 environment. However, I was puzzled when this fails under 4.0.2 on the hosted web site at apex.oracle.com. This is why I posted a "possible" bug in 4.0.2.
    I hope this all makes sense.
    One more thing, as already mentioned in my original post, this "defaulting a date picker" functionality does NOT work at all for the "classic" date picker items in both 4.0.1 nor in 4.0.2. I realize one can implement this functionality (I' guessing) my using, say, a "onChange" javascript call to submit the page. It's just funny that the "classic" date picker items are not acted upon by the dynamic action MANAGE_DATES that submits the page.
    Thank you.
    Elie

  • Bug report status

    Hi, I have previously highlighted an issue with the Xperia C3 D2533 running 5.0, where the back camera is producing low quality images.This is from the Galaxy Note 1 While this is from the Xperia C3 What is appaling is if you zoom in, the N7000 has more detail than the C3, whereby the C3 just paints over the colours unscrupulously giving jagged edges obvious from the USB. I have sent an email to support and received a reply saying it has been forwarded to the developers about two weeks ago. I have heard that the Lollipop 5.1 is coming out in July and am curious as to whether the camera issue has been confirmed as a bug by the developers and are currently looking into it, hopefully rolling out the update with the fix as well. Edit: I have done a software reset and a repair via PC Companion using the steps recommended. The PC Companion told me there are no available updates or softwares for this phone. Therefore to sum it up, what I would like to know is a confirmation on the status of this report among the devs and whomever it may concern in the troubleshooting phase.

    Seems like a search of the bug report submission
    queue would be useful.Use this:
    http://developers.sun.com/contact/feedback.jsp?referer=http://forum.java.sun.com&category=sdn&mailsubject=Forums%20or%20Community
    It's as pointless as any other measure in getting Sun to do what you want. ;)

  • BUG report - Inconsistent IR settings in Builder

    Apex 4.0.2
    Most of the reports used in the App Builder have been converted to use Interactive reports which is great. But I find that the IR settings are not consistent across all the reports. I had reported this during the tryapexnow.com beta phase. Now that we can use the new apex_application_install API to load up the Builder apps into our own workpace so we can review how they are built, the Region Utilities > Update Interactive Report Settings page shows this. Or just run the query
    select
    page_id, name, allow_save_rpt_public, show_finder_drop_down, show_display_row_count, show_search_bar, show_search_textbox, show_actions_menu, show_select_columns, show_rows_per_page, show_filter, show_sort, show_control_break, show_highlight, show_computation, show_aggregate, show_chart, show_notify, show_group_by, show_calendar, show_flashback, show_reset, show_download, show_help
    from apex_040000.wwv_flow_worksheets
    where flow_id=4000My main annoyance is the "Save Report Public" checkbox. The IR saved report list shouldn't be cluttered with all the report settings saved by all the workspace developers.

    Please submit an official bug report to Adobe at:
    http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
    Alexander.
    Canon EOS 400D (aka. XTi) • 20" iMac Intel • 12" PowerBook G4 • OS X 10.4 • LR 1 • PSE 4

  • Sigil, error and bug reporting

    I finally got around to updating my desktop to Arch, I have been running my file and print servers with Arch and without problems for over a year.
    So far everything has gone pretty well, a few problems, mainly caused by me misstyping something, all problems solved by searching the wiki and the forums. But now I have a problem I cannot find any answer to, so my first post here is to ask for help.
    I installed Sigil from the official repositories, no errors reported, but it will not run. Starting from cli gives the error 'Could not load a transcoding service.' The only forum reference I can find to transcoding is 3 years old and seems to be connected with gstreamer and firefox. Can anyone point me to further information that will allow me to solve this?
    While searching for help I came across the Sigill package page here which states that the program has been flagged out of date a month ago, despite the fact that the version there is the latest release from the developers. I was going to post the error as a bug on the package page but was informed that I should not post bugs on out of date packages, so what is the proceedure for posting bugs in cases like this?

    weedfreak wrote:I installed Sigil from the official repositories, no errors reported, but it will not run. Starting from cli gives the error 'Could not load a transcoding service.'
    I cannot confirm that issue. Sigil works fine on my local machines.
    By the way, please file a bug report at https://bugs.archlinux.org/ and copy&paste the complete output you're getting from the cli.

  • RH bug reports sent to dead Macromedia address

    When one reports a RoboHelp bug through
    http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform,
    the bug report is apparently submitted to a no longer existing
    Macromedia address.
    One gets an e-mail bach with the error message: "Your message
    did not reach some or all of the intended recipients. Subject: [
    Bug Report ] Sent: [Date]. The following recipient(s) could not be
    reached: [email protected] The e-mail account does not
    exist at the organization this message was sent to."
    Other than being an insult to the RH user community, it ought
    to be in Adobe's own interest to get bug info from their users.
    Anyone knows an Adobe address to which we can send RH bug reports
    (and expect them to be read)?

    The link to the page is as below, without the comma at the
    end.
    http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
    I just tested it and it worked fine. I got an acknowledgement
    immediately. Also I can confirm that all the bug reports and
    feature requests do get read and considered.
    Try again Morten and see what happens. Nobody has reported
    this before so I think there must have been a glitch.

  • Bug report: Russian Translation Messages

    There are several incorrectly translated messages. Better translation is below. English original is back-translated, so could be not exact in all cases. Russian text should be replaced.
    Mail - Setup - View/Actions (Почта - настройки - отображение и действия) - "удалить подтверждение сообщения" (remove message confirmation) should be "подтверждение удаления сообщения" (confirm message removal)
    Blackberry World Setup / General(Общие настройки) - 'Cохранить на карту памяти' (save once to SD card) should be 'Cохранять на карту памяти' (usually save to SD card)
    Blackberry World Payment methods - 'Методы оплаты' should be 'Способы оплаты'
    Clipboard Select / Select all should be 'Выделить' / 'Выделить все' (as select/highlight), not 'Выбрать' / 'Выбрать все' (as 'choose') phone-wide
    SMS is translated as 'Текстовые сообщения' (Text Messages) in Russian. Untranslated 'SMS' or at least 'Сообщения' (messages) is much more common for Russia.
    A message after doing a software update check is not correct: 'В настоящее время установлена самая последняя версия ПО' (Latest software version is currently installed) - should be 'В настоящее время установлена последняя доступная версия ПО' (Latest available software version is currently installed)
    "Ожидание подключения для передачи данных" message (Waiting for data connection) during set-up doesn't fit the screen, should be wrapped or cut.
    "Новый часовой пояс <...> время отправлено" (New timezone... time sent) notification during the initial set-up should be 'время установлено' (time set).
    Cheers,
    Alex

    This could be related to another bug reported here recently:
    E-mail looses all images if mail server doesn't accept outgoing email...
    You cannot count on Apple looking into this or even noticing it if you report it here, so I suggest you the same I suggested in the other thread, i.e. report it in one of the following places:
    http://www.apple.com/macosx/feedback/
    http://developer.apple.com/bugreporter/

  • Bug Report (reproducible) - Adding an appointment to Google Calendar causes Pre to display a blank calendar.

    I have been able to reproduce an important bug on the Pre (webOS 1.0.2).  I didn't see a way to submit an official bug report, so I'm posting it here.
    Step 1: Import the following ical file into a Google calendar:  http://www.halfwayproductions.com/test.ics
    Step 2: Sync the Google calendar to your Pre
    Step 3: Your Pre calendar appears completely blank!
    It's worth noting that this file doesn't import correctly into Google calendar.  Google gets the repeat wrong and puts the appointment at the wrong time.  However, this shouldn't cause the Pre to display a blank calendar!
    Post relates to: Pre p100eww (Sprint)

    EDgeofNJ wrote:
    I confirmed that a meeting location with an apostrophe causes the event to not sync to Google Calendar. Interesting enough, I created an event on Google Calendar with an apostrophe in the location and it sync'd to my Pre, without causing the calendar to go blank. BTW, I'm on 1.1.0.
    This seems like it would be a very common occurance as many meetings or appointments could possibly contain apostrophes in the location (Joe's office, Dr's office, Arthur's Tavern, etc). It leaves me with little confidence of what is on the Pre and what is in my Google Calendar, as there could be other issues causing events not to sync, and they are obviously not "in sync." Is anyone looking into a fix for this? (Is Palm or Google listening?) In the mean time, is there any way to get a log of events that did not sync, as opposed to blindly assuming everything was uploaded fine?
    Message Edited by EDgeofNJ on 07-30-2009 10:18 AM
    Some of these are known occurrences and I believe have been logged into the Palm SW database. Symbols had also been causing Facebook contacts to not sync properly as well. I don't know if getting a log of events that do not sync is possible at this time. However, if a user could post characters and their entry points that are known anomalies that cause the errors, that'd be useful.

  • Strange behavior when Popup LOVs has read-only condition and Bug Report

    Hi,
    I observed an inconsistent behavior of Popup LOVs when the read-only condition is true. In that case the defined lov query is used to map the internal value of the page item to the display value defined in the lov query.
    What is the reason for this behavior? Because if the Popup LOV is in "edit mode" the page item value is just displayed without looking up the display value. The display value is just used for the popup lov. Mapping the value is normally a behavior of the popup key lov.
    -> The result is that different values are displayed if the page item is in edit or read-only mode. That's not really the behavior someone would expect.
    BTW, there seems to be a bug with "Display Extra Values" set to "Yes" in the case read-only is true. If the lookup doesn't return a value it just displays [ ], but because the property is set to yes it should display the value. The Popup Key Lov has the same bug.
    Thanks for bringing some light into that behavior
    Patrick
    Oracle APEX Essentials: http://essentials.oracleapex.info/
    My Blog, APEX Builder Plugin, ApexLib Framework: http://www.oracleapex.info/

    Patrick,
    I've added your comments to a task already in our queue to examine all item types for correct behavior in read-only mode. I've noticed the quirks with display extra values also.
    By the way, still interested in your thoughts re: Re: Bug Report: Images broke when using get_blob_file_src and not authentic .
    Scott

  • Bug Report E71 - Post (serious) bugs here.

    Hi,
    Maybe it's wise to have a dedicated bug report topic for the E71.
    So not discussions here .. just USEFULL reports.
    Bug #1 :
    Situation:
    - I am having a sip internet-call (native SIP client) with an Asterisk server.
    - put the call on 'standby' (by menu Options)
    - i press the 'Options' softkey again
    - phone freezes. Only battery removal can restart it.
    (it also freezes after doing some random key presses .. which i can't remember exactly .. but the standby is not stable.)
    Bug #2:
    - please fix color-settings for the camera . There is 'purple' all over.

    501.21.001 on RM-357 (E71-2) Since upgrading to 501, I've had two major problems. 1) rarely (it's only happened twice), the SMS application will hang when attempting to reply to a message. The original message stays on the screen and nothing will let me out of the app. The phone will respond to the power button, however, and seems to work fine after a reboot. 2) battery life and/or battery meter is terrible. Battery meter will stay near the top then suddenly drop to 2-3 bars remaining. Energy Profiler seems to confirm my power usage is about where it used to be (drawing about 0.12W with the screen off and Gravity running in the background). Phone will then reach 1 bar and give "battery low" warnings, but I'm not convinced the battery is truly low. Last night I was on one bar for over two hours, Gravity was left running, I send and received a few texts, and I was connected to my in-car bluetooth for about 25 minutes, and the phone did not die. On the original firmware, I would never have made it through all that on one bar, which makes me think the bug is with the battery meter, not the battery life itself.

  • Logic Pro 5.1 ch plugin subwoofer channel bug report

    hello,
    I had found out that Native Instruments absynth 5.1 ch synthesize sofware , which in stand alone mode
    outputs the subwoofer channel audio properly, does not output subwoofer channel audio in Logig Pro surround
    plugin in 64 bit mode.
    I contacted  Native Instruments about this and after a certain time, they say that they did deeper invstigation
    and found out that it is the Logic bug.
    I just don't know how to bug report to the apple, so I put this here.
    Please confirm and fix it.

    The crashed thread (7) mentions logic's preferences file. (com.apple.logic.pro). Drag it to the desktop (so you can reclaim you key commands if it works) and restart logic. Logic will create a new preferences file. Worth a try..

Maybe you are looking for

  • Photos do not appear in iMovie 11

    Suddenlhy photos imported into iMovie 11 do  not appear in iMovie anymore. Previously imported photos appear fine. I am using OSX Mountain Lion. Any idea what is wrong ?

  • Profile Editor and DNG Profiles - Still Beta 2?

    Are the DNG profiles and Profile Editor still at Beta 2? I am confused because the Adobe Labs DNG Profiles resources page (http://labs.adobe.com/wiki/index.php/DNG_Profiles) has not been updated since Oct 22 2008, but Lightroom 2.2 provides non-beta

  • Password Server Class?

    I am writing to a password protected server with a username and a password. I don't know of any class that can connect to a username and password server that is not in the sun package. I don't want to download any new packages. If anyone knows of a c

  • Sound output pops/clicks/silence Logic & Motu 828mkII & G5 Quad

    Mac OS 10.4.3 G5 Quad 3.5Gb ram Logic 7.2.3 Motu 828mkII When I've got a lot of automation going on, sometimes the sound output cuts out briefly, I hear a small pop or click on the monitors and I have to press stop on Logic to get the audio back onli

  • My child is getting my imessages on the Mac

    Finally sorted out all my updates with Lion OS 8 and set up parental controls for my 9-year old's user account. Now I realize he can see text messages sent to me from coworkers, friends, etc. on imessage. How can I remedy this?