Hide includes in edit mode

I have some code needed in my template that should not be
seen within Contribute in edit mode (i.e
<noscript></noscript> etc). Up to now the trick was to
put said code in include files so that Contribute would not show
them, but recently for some reason I ignore Contribute has started
showing the content from my include files when in edit mode and
some of the code that should be hidden shows up. Even though this
code is locked and not editable in Contribute some of it (div's) do
en up showing over other elements and makes it very hard to edit
regular content in Contribute.
Anyone ever had that problem, or know of some way to make
sure that includes are not seen in edit mode?

Hi,
I'm having the same issue.
Whenever I create a new page in contribute from a Dreamweaver template it converts any php includes and places the content into the page rather than leaving it as a php include.
This does not happen if I use Dreamweaver and the same template file, it actually works how you would expect and leaves the code alone.
Why is Contribute doing this and how can we stop it?
Can someone from Adobe please answer this as no one seems to have got an answer.
Many thanks.

Similar Messages

Hide menu in edit mode

I have a dhtml menu included into a web page. I would like to
know if it's possible to hide the menu in edit mode so that it will
not interfere with the rest of the page. Right now when I enter in
edit mode the menu overlaps the page content. Any help is
appreciated

Hi,
I'm having the same issue.
Whenever I create a new page in contribute from a Dreamweaver template it converts any php includes and places the content into the page rather than leaving it as a php include.
This does not happen if I use Dreamweaver and the same template file, it actually works how you would expect and leaves the code alone.
Why is Contribute doing this and how can we stop it?
Can someone from Adobe please answer this as no one seems to have got an answer.
Many thanks.

Problem including a jsp in edit mode

Hello
Somehow i have a problem while including a jsp page while displaying the edit mode.
If my doEdot just writes something like "Hello World" into the response it just works fine.
But if i try to include a jsp resource the problems start to arise:
1. The normal resource lookup request.getResource(IResource.JSP, bla) returns an unavailable resource. This seems the be because although a working instance of my portlet is used, the passed request belongs to another context.
2. Passing a precomputed resource seems to work, the page definitly gets called (-> it gets compiled and no errors show in stacktrace), but a sap dialog shows, saying that no properties exist, that can get configured cry
I even stripped the jsp page to the single line "Hello", it gets compiled, but not shown!?
                                                                                edit: After the dialog a new dialog is shown sayin: The specified root item cannot be retrieved from the configuration. Correct the entry before trying again
Even IF my confoguration is wrong (higly possible), why does it only show when using include but not while writing directly into the response stream?
Solution:
Portlet gets called via doEdit and thus is in edit mode. Since jsp pages extend AbstractPortalComponent the service method does not serve via the doContent method but tries to call doEdit on itself. Since jsp pages usually do not define doEdit, the default edit behavior gets applied.
Set Default mode within the request type and the request node.
Message was edited by: Mark Vollmann

Thank you it worked .I really doesn't have much experience in the front end.
Thank you once again.
I ahve another problem , this is alomst the same , here i have a html anchor when user clicks on that link i wnat to display the result in the same window , but it is displaying in the new window , it does not have frames , so i can not say target .
here is the code , please give me advice
<table>
<tr>
<td><jsp:include page="top.jsp" /></td>
</tr>
<tr>
<td align="left" valign="top" width="50%"><jsp:include page="paneltranscripts.jsp" /></td>
<td width="50%"><center>
<%
if(transcripts.length == 0)
out.println("<h2>No Transcripts Avialable</h2>");
else
{ %>
<% out.println("You are viewing at ");%> <b> <%= roomname%> </b> <% out.println("room transcripts"); %>
<br>
<% out.println("To <b>view</b> the transcripts click on the link"); %>
<br>
<% out.println("To <b>download</b> the transcripts right click on the link, open it in new window and save the page"); %>
<br>
<br>
<%
     for(int i=0;i<=transcripts.length-1; i++)
          if(transcripts.equals(""))
               continue;
          else
          %>
               <a href="/DigiChat/DigiClasses/Resources/<%= sitename%>/Transcripts/<%= roomname%>/<%= realtranscripts[i%">"><%= transcripts[i] %></a>
               <br>
               <br>
          <%
%>
</td>
</tr>
</table>
When user clicks on the transcripts[i] i want to display the result in the same window.
Thank you</a>

ALV in EDIT-Mode: can't hide the toolbar in edit-mode

Hi,
I have supressed in my ALV all standard-buttons with the help of an it_toolbar_excluding. I have built my own toolbar (p_object->mt_toolbar). Until know everything is fine, the ALV shows only my own generated toolbar.
In that moment, when I change a property of a column in the fieldcatalog ( wa_catalog-edit = 'X' ), both toolbars are shown, the standard toolbar and my own generated buttons.
What's wrong, how can I hide the standard toolbar when I am in the edit mode?
Kind regards
Andreas
Edited by: Andreas Waldt on Sep 3, 2008 5:19 PM

Thank you very much,
during testing I have recognized, that the buttons in the toolbar are new functions, because of the edit mode.
So I have put all the new button into the excluding list. It worked!
Thanks again!
Andreas

Correctly Hide Edit Mode Elements in Preview Mode

Hello,
I wanted to know how I should modify the code below to correctly show content in the correct mode? The code below works, but when switching to preview mode, I have to manually refresh the page to get the "Preview/Publish mode text" to disappear. I'm aware I could modify the sidekick to force a refresh, but I'd prefer to do it similarly to how CQ does it (eliminate all edit mode components immediately without refreshing the page). Thoughts?
import="com.day.cq.wcm.api.WCMMode"
<%
    if ((WCMMode.fromRequest(request) == WCMMode.EDIT) || (WCMMode.fromRequest(request) == WCMMode.DESIGN)) {
        %><div>Edit mode only text</div><%
    } else {
        %><div>Preview/Publish mode text</div><%
%>

Hi,
As the above code is evaluated server side and edit/preview is triggered client side this approach will not work for you.
You could use the fact that CQ is adding "cq-wcm-edit" class to page body in edit mode and "cq-wcm-preview" in preview and hide your divs by CSS.
Br

I'm using Photoshop Elements 12 on Windows 8.1. When I go into the Expert Edit Mode the toolbar available appears in one single column and misses off several tools including foreground and background colour. How can I restore the original toolbar?

I'm using Photoshop Elements 12 on Windows 8.1. When I go into the Expert Edit Mode the toolbar available appears in one single column and misses off several tools including foreground and background colour. How can I restore the original toolbar?

Thanks for your help - your suggestion worked beautifully.Dennis Hood
From: 99jon <[email protected]>
To: Dennis Hood <[email protected]>
Sent: Thursday, 15 January 2015, 15:20
Subject: I'm using Photoshop Elements 12 on Windows 8.1. When I go into the Expert Edit Mode the toolbar available appears in one single column and misses off several tools including foreground and background colour. How can I restore the original toolbar?
I'm using Photoshop Elements 12 on Windows 8.1. When I go into the Expert Edit Mode the toolbar available appears in one single column and misses off several tools including foreground and background colour. How can I restore the original toolbar?
created by 99jon in Photoshop Elements - View the full discussionTry re-setting the prefs.Go to: Edit >> Preferences >> General (Photoshop Elements menu on Mac)Click the button Reset Preferences on next Launch If the reply above answers your question, please take a moment to mark this answer as correct by visiting: https://forums.adobe.com/message/7099161#7099161 and clicking ‘Correct’ below the answer Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: Please note that the Adobe Forums do not accept email attachments. If you want to embed an image in your message please visit the thread in the forum and click the camera icon: https://forums.adobe.com/message/7099161#7099161 To unsubscribe from this thread, please visit the message page at , click "Following" at the top right, & "Stop Following" Start a new discussion in Photoshop Elements by email or at Adobe Community For more information about maintaining your forum email notifications please go to https://forums.adobe.com/thread/1516624.

How to hide the Navigation and Builder links in edit mode

I am building a portal that will have outside vendors sharing documents to a site... I would like them to be able to change the file, author or experation date ... but I don't want them to see the naviagtion or builder links when you go into edit mode... any suggestions

Hi,
Try with iview "Open on new window" parameter options. Perhaps if you use new window without head, you can show iview without options you don't want.
Hope this helps,
Iván.

Hiding Parsys in Edit Mode

Hello,
I'm building a tabbed component and I'm having trouble hiding the parsys section for inactive tabs using CSS styling (whether visibility or display). Even though I set the visibility of the parent DIV the parsys is sitting to hidden, it still displays on the page while in Edit mode (works in Preview).
<%
        String[] linkname = properties.get("navitems", String[].class);
        for (int i = 0; i < linkname.length; i++) {
          if (i == 0) {
            %><div class="miniShow" style="visibility: visible;"><%
          } else {
            %><div class="miniShow" style="visibility: hidden;"><%
          %>
              <div class="<%= "basicMiniShow"+(i)%>"><cq:include path="<%= "mininav"+i %>" resourceType="foundation/components/parsys"/></div>
            </div>
          <%
         } // end for
%>
With the code above, as my JavaScript function properly swaps between tabs and shows the components in the parsys, the subsequent "Drag your components here" box doesn't disappear. For example, if I add 2 tabs and place a Button in the first parsys and a Image in the second, swapping tabs correctly shows/hides the button/image respectively - however the "Drag your components here" box for both are always visible.
What am I missing here?

   The paragraph component [1] is resposible for rendering once editContext has a resource set[2].   Either
   * Need to pass a variable & then based on that variable paragraph component should decides whether to render or not.
   OR
   * Using javascript Iterate all the div below parent div and apply the style="clear:both".
[1]   /libs/foundation/components/parsys/parsys.jsp
[2]
    if (editContext != null ) {
        editContext.setAttribute("currentResource", null);
        // draw 'new' bar
        IncludeOptions.getOptions(request, true).getCssClassNames().add("section");
        %><cq:include path="*" resourceType="<%= newType %>"/><%

Access web app - Check if form is in edit mode

I want to hide some fields when a form is in edit mode but I can't figure out how to check that. I tried
That is not working. Is there another way to check the "state" of a form.
Thanks, Mike

Hi Mike,
Unfortunately, there is no existing method that I'm aware of to know if a view in an Access 2013 web app is currently in Edit mode or view mode. I can sympathize with you on this one since I’ve had many occasions in my apps where I wanted to use something
like this for various scenarios. I will pass along your feedback to the product team. You can set various properties on controls using macros, however, you cannot read control property values on views in Access 2013 web app views. The one exception is reading
values of data entry controls.
About the closest you can come to achieving you end goal would be to do a whole lot of extra work to control basic editing and save operations on that view. For example, you could create a new custom Action Bar button on your view with the same icon as the
existing Edit Action Bar button. Slide that one into the position you want in the Action Bar. For the On Click event of this custom one, you put the view into Edit mode, and then show the controls that you want (which are hidden by default I presume in the
On Load event of the view).
If you want to experiment with this technique, I would suggest trying it out on a copy of the view. There are a couple of caveats to this approach that I should point out. First, don’t delete the existing built in Edit and Save Action Bar buttons (or any
of the built in ones for that matter). Once deleted, you can never get them back. I am always in the habit of sliding ones I don’t want to the far right and then hiding them in the On Load event of the view. That way if I ever have a need in the future to
bring it back, the button(s) is still there for my use and all I have to do is remove the macro that is hiding it.
The second caveat is that once you put your view into Edit mode using your own custom Action Bar edit button and then click the save button to save the record changes, your hidden controls that you wanted to display on initial load will still show for the
next record. That may not be the behavior you want. In that case you would need to also create your own custom save Action Bar button too. In that On Click event, you would use the Save Record macro action and you would re-hide the controls that you want hidden
again for the next record since Access will automatically pop you back into view mode with the save operation. You’ll have to experiment with this if you want to try it. You might need to hide the controls before doing the Save Record action.
Hope that helps,
Jeff Conrad - Access Junkie - MVP Alumnus
Senior Content Developer - Modern Assistance and Support Experience - Microsoft Corporation
Author - Microsoft Access 2013 Inside Out
Author - Microsoft Access 2010 Inside Out
Co-author - Microsoft Office Access 2007 Inside Out
Access 2007/2010/2013 Info: http://www.AccessJunkie.com
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/en-us/legal/Copyright/Default.aspx

Text Caption appears in Edit Mode but not in Preview Project or Web Browser

I'm using Cp4 and have downloaded Adobe Flash 10 Active X, it's ver 10.1.82.76. I've added a simple text caption with these options:
Timing Display: Rest of slide
Appear after: 2.0 seconds
Transition effect: Fade in only
In: .5 seconds
And Visible is checked
I also have a simple line that I drew with the draw line tool and included an arrow on the end of it.
Everything on the screen works including the click box, the animated text and the failure caption. For some reason the text caption and the arrow are not appearing except in Edit Mode. In Preview Project, they disapper but the click box, failure caption and animated text work fine.
I've rebooted, copied this screen into a new instance of Cp4, re-created these objects on a freshly recorded screen, chosen Order: Bring to Front, created a brand new screen completely from scratch and downloaded the Flash 10 Active X version mentioned above.
They funny thing is, is that the text caption and arrow works fine on other screens in the project. I have 76 screens total.
I'm running Windows XP.
Any suggestions?

Hi there
Can you post a screen capture of what your Timeline looks like?
Odds are your Click Box is pausing in a weird place.
Cheers... Rick
Helpful and Handy Links
Begin learning Captivate 5 moments from now! $29.95
Captivate Wish Form/Bug Reporting Form
Adobe Certified Captivate Training
SorcererStone Blog
Captivate eBooks

ALV: columns in read-only mode look like editable columns in edit mode

Hi,
My application contains an ALV table which should be toggled between display and edit mode like the rest of the fields.
The evident solution was to use
if_salv_wd_table_settings~set_read_only( abap_true or abap_false)
However, unlike the rest of the fields, when the application changes into display mode and the fields get grey like in any SAP application, the columns in the table which were editable remain white, and those which were not editable and thus grey, get now white, too, instead of the other way round. So it will look to the normal user, as if now all columns would be editable!
Of course, he would realize that they are not when he tries to edit them, but this is irritating.
See following link with screenshots (only active for 3 weeks from now on):
[Link to my webmail space/SDN: .|https://businesswebmail.telekom.at/filestorage/MzYxMTk1OTMx/]
I have looked
through my books ("Einstieg in Web Dynpro for ABAP", "Praxisbuch Webdynpro for ABAP", ...)
through the wiki for Webdynpro for ABAP here in SDN as well as through this forum (by searching with "ALV edit")
through the notes in BC-WD-CMP-ALV
but could not find any solution. Most tables in those PDF articles found here in the WD4A wiki also show white cells although they are probabliy in read-only mode (e.g. the imitation of the SE16N browser article).
The attributes to the LO_CELL_EDITOR for both Inputfields and textview columns contain exactly the same values when toggling between display and edit mode (read-only in table settings), so also no chance to change here anything.
Also changing the cell design is not a solution as there is no design that looks like grey for not editable according to WDUI_TABLE_CELL_DESIGN ([SAP Help - WDUI_TABLE_CELL_DESIGN|http://help.sap.com/saphelp_nw2004s/helpdata/en/56/5e9041d3c72e7be10000000a1550b0/frameset.htm].
I do not know if I have made an error, as this is my 3rd Web Dynpro (after the first 2 of the introduction book), or SAP is really inconsistent in User interface between "normal" fields and ALV table fields.
Can you please help me?
Thanks in advance,
Erlend

Hi,
In my application aslo, i have 30 columns out of which 10 are input fields. But, i'm showing the table as ABAP_TRUE incase of Non-editable otherwise to abap_false. Now i'm getting everything as in WHITE cells.
Do you want to show it is Grey mode with Non-editable feature. Is that so.
How many columns are there which has Input fields.
Get the column references.
Now, based on the mode of display create the object as Input or Textview field.
For that column -
If mode eq 'D'.
Create an object for Textview(cl_salv_wd_uie_text_view)
else.
Create an Object for Inputfield(cl_salv_wd_uie_input_field)
endif.
The Append row is a standard button or custom one on ALV toolbar.
Do you want to hide the toolbar or just disable these buttons.
If you want to hide the toolbar then refer my wiki -
http://wiki.sdn.sap.com/wiki/display/WDABAP/NullreferenceforUPDATETOOLBARerrorsofALVinthewebdynpro+ABAP
Regards,
Lekha.
Edited by: Lekha on Sep 30, 2009 8:06 PM

How to get the view in editable mode with OCA button.

Dear Experties,
I am new to CRM WEB UI ,I have got the requirement to develope a view with OCA button on it and when i click on the button it should direct to the second view and it should open with edit mode.
The Source view is table type and target view is form type.
I am able to achieve this but unable to get it in editable mode.
I have added the below code in do_prep_output method but getting dump at the line
lr_entity ?= me->typed_context->EMAINLEG->collection_wrapper->get_first( ).
The error message is
Long text During a 'CAST' operation ('?=' oder 'MOVE ? TO')a type conflict occurred. The source type '\CLASS=CL_BSP_WD_MIXED_NODE' is not compatible for assigning with the target type '\CLASS=CL_CRM_BOL_ENTITY'.
Please somebody help me on this
lv_display = me->view_group_context->is_view_in_display_mode( me ).
IF lv_display EQ abap_false.
ELSE.
     me->view_group_context->set_view_editable( me ).
ENDIF.
DATA:    lr_tx           TYPE REF TO if_bol_transaction_context,
          lr_entity       TYPE REF TO cl_crm_bol_entity,
           lr_comp type REF TO ZL_BT131QI__BSPWDCOMPONEN_IMPL.
lr_comp ?= me->comp_controller.
Check lr_comp is BOUND.
lr_entity ?= lr_comp->typed_context->BTADMINI->collection_wrapper->get_current( ).
CHECK lr_entity IS BOUND.
IF lr_entity->lock( ) = abap_true.
    me->view_group_context->set_view_editable( me ).
ENDIF.
lr_entity ?= me->typed_context->EMAINLEG->collection_wrapper->get_first( ).
WHILE lr_entity IS BOUND.
    lr_entity->lock( ).
    lr_entity ?= me->typed_context->EMAINLEG->collection_wrapper->get_next( ).
ENDWHILE.
The following error text was processed in the system:
Source type \CLASS=CL_BSP_WD_MIXED_NODE is not compatible, for the purposes of assignment, with target type \CLASS=CL_CRM_BOL_ENTITY
Exception Class CX_SY_MOVE_CAST_ERROR
Error Name MOVE_CAST_ERROR
Program ZL_ZBT131QI_EMAINLEG_IMPL=====CP
Include ZL_ZBT131QI_EMAINLEG_IMPL=====CM00C
ABAP Class ZL_ZBT131QI_EMAINLEG_IMPL
Method EH_ON_EDIT
Line 33
Long text During a 'CAST' operation ('?=' oder 'MOVE ? TO')a type conflict occurred. The source type '\CLASS=CL_BSP_WD_MIXED_NODE' is not compatible for assigning with the target type '\CLASS=CL_CRM_BOL_ENTITY'.
Thanks in advance!!!

Hi,
in CRM a context can consist of model nodes, value nodes and, unfortunately, mixed nodes. While mixed nodes implement the same interface as model nodes they can't be casted into a CL_CRM_BOL_ENTITY directly. Instead you need to perform the following conversion in order to get the model node from the mixed node:
DATA: mixed_node     TYPE REF TO cl_bsp_wd_mixed_node,
           entity              TYPE REF TO cl_crm_bol_entity.
mixed_node = me->typed_context->EMAINLEG->collection_wrapper->get_first( ).
entity = ?= mixed_node->if_bsp_wd_ext_property_access~get_model_node( ).
Best,
Christian

Problem with window repaint and scrollbars in edit mode (LabVIEW 8.0.1)

I am running LabVIEW 8.0.1 in Windows XP SP3. For my main VI, I ran into a strange problem about 5 months ago. The front panel window - in both edit mode and run mode - stopped repainting itself on the right side which is most visible when you scroll up and down, but also visible with overlapping windows. Coincident with the repaint problem, both scrollbars look disabled with greyed-out arrows and no boxes in the bars that you can click and drag to scroll the window. The scrollbars still partially work if you hover the mouse over them and roll the mouse wheel but clicking and dragging doesn't work.
The front panel has lots of controls and indicators including tab-control containers and is larger in the horizontal and vertical directions so both scrollbars should be active. But I deleted all elements on the front panel and everything in the block diagram and the problem persists. So the problem is not directly related to some control/indicator display.
I saved the simple VI with this problem (using a wide text line and a tall rounded box to test), then created a new VI and copied the two elements to the new VI. This new VI does not have the repaint and scrollbar problem. The two VIs differ slightly in memory usage and in revision number (the bad one is revision 1785 and the good one is revision 3), but otherwise the two VIs are identical. I attached both VIs to this posting. When you first open the bad VI, you'll see the disabled scrollbars whereas the good VI has active scrollbars. To replicate the repaint problem, scroll the window up and down with your mouse wheel. If it's fine when you first open the VI, click on another window, then click back on the VI window and try the mouse wheel again. This clicking-away-and-back always causes the repaint problem for me. I tried the VIs on two different computers both running Windows XP SP3 and LabVIEW 8.0.1 with identical results.
Here's what I discovered from troubleshooting with the simple VIs:
* scrollbars always disabled
* repaint problem in main window for window widths larger then 680 pixels
* repaint problem in main window menu toolbar for widths larger than 646 pixels
* entire window becomes disabled for window widths larger than 1348 pixels
* can repaint window by minimizing and restoring, but only repaints that one time
* scrollbar boxes sometimes flicker into view but then disappear
* scroll left and right by hovering mouse over horizontal scrollbar and using mouse wheel
I found something similar on this forum (thread: Problem with front panel refresh) - it might be related to the CAR about the panel being offset internally. I don't have access to LabVIEW 8.5 or later and don't plan to upgrade - I haven't tried the trial version as that user did. I could try to copy and paste my entire block diagram to a new VI but the VI is so large I'm afraid something would break, plus I don't want this to happen again in a few months. The problem seemed to occur after a certain number of saves (or revision number). I save backup copies often and when the problem first happened, I was able to go back to a previous version, make the missing changes and save it with no problems, but this only delayed the problem and it came up later. So maybe it's the revision number. It didn't seem related to a particular addition or modification in the front panel or diagram.
The image attached shows the repaint and scrollbar problems in the bad VI.
This brings up a question I have - if this problem is a bug and was fixed in 8.5 and later, is there a way to apply bug fixes to earlier versions? Or do I have to pay for an upgrade to fix such bugs?
Solved!
Go to Solution.
Attachments:
RepaintTest_Bad.gif ‏27 KB
Test Repaint - From Bad VI, scrollbar and repaint problems.vi ‏7 KB
Test Repaint - From Blank VI, no problems.vi ‏5 KB

Seems something got corrupted with this VI. Copy things over to a fresh VI and things should be OK.
See also this recent report of a similar issue.
LabVIEW Champion . Do more with less code and in less time .

Contact bug : contact phone numbers in edit mode are not shown in "dial" mode

Contacts can have seemingly unlimited phone numbers as seen in the contact edit mode, though very few are shown in the corresponding non-edit mode. Of course, Dialing is not supported in the edit mode.
I have found that contacts that include pause characters or block characters are not properly displayed in the contact "dial mode". If you every try a conference call service, this is important to you.
At&t uses the comma as a pause, and Verizon uses the letter "t" as a pause. *82 temporarily blocks your caller id. Somehow the WebOS software that chooses which items to allow me to dial has bugs and worse, there is no clear way to prioritize so I am completely at the whim of the software.

I have tested entering 12 phone numbers on my own Pre Plus and all the numbers display in the normal contact field. How many phone numbers are you trying to to display?
The dialing options on the Palm Pre Plus are as follows:
To insert a two-second pause in the dialing sequence, enter a T where you want the pause to appear. To add a + symbol in the dialing sequence for international dialing, press and hold 0 (zero) in the location where you want the + symbol to appear. To insert a stop in the dialing sequence, enter a P where you want the stop to appear; to dial the next set of numbers after the stop, tap the screen.
As far as 3rd party special dialing character entry you would need to check with the 3rd party on how to enter this information into you device for your conference calling service.

Errors in runtime that I cannot reproduce in edit mode

I just moved an application up to production that doesn't quite work properly but I cannot reproduce the problems in edit mode.
First is I have some filters and a search field on my report page. If I am in Application Builder and I use the reset button all fields clear. But in the runtime version that the end user uses the reset button clears all but the search field.
Second, I have edit buttons on the rows that bring them to the form page and allow them to edit their record. In Application Builder it will populate the values in the form. But in the runtime version that the customer uses it brings the fields up blank.
The application is in Apex 2.2.0.00.32. I have other applications with similar functionality and they all work perfectly. Sure is hard to debug when you can't reproduce it in the builder. :-) Anyone have any ideas?

Yeah, basically there is no issue in the one I moved up. I have this application linked off a web page that allows users to use it. That is the only place that has the issue. When running it while logged into APEX and in the Application Builder it runs fine (hence the debugging issue).
The first page (page 9), brings back a list of all the individuals and information about them. There are two regions, one for filtering and the report region. The filtering region has a reset button. There is a process for clearing out the items when the reset button is hit. However, in the one off the web page the items are not being cleared. We have to go manually reset the values. However, if I run this in Application Builder it works just fine. I do have other applications with similiar functionality linked of the same website and they work as intended as well.
The other problem is similiar in that it works from Application Builder but does not work from the link on the web site (it's an internal site by the way). The primary key of the report list is set to be an link to page 10 for editing that line. So I set the item to be the icon, and to call page 10, which is a form page. I pass the value of the field to the item on the form page.
I have this application in development (and it works correctly there as well) and I do an export/import on it. I also change the application id on it on the import (which I do with most of my apps).
I recently upgraded from 2.0 to 2.2. Other apps (including this one) continued to work with no issues. However, this filtering was added after the upgrade, and is the first app I have exported/imported since that upgrade. I have not deleted it from scratch and reimported it yet cause this is a production application with visibility to end users.
Message was edited by:
user488101

Hide includes in edit mode

Similar Messages

Maybe you are looking for