I'm trying to handle opening app in new tab in the same browser.
When I am logged in to one tab and will open a new tab and log in again, then return to the first tab and click wherever the error page appears with information about the ended session.
How can I handle it so that when opening the application in a new tab, there is a message that app is already open and that you cannot log in again and the session does not end in the first tab. Another solution is to prevent the error page from appearing in the first tab, but to open the login page.
This is an an annoying facet to APEX session management that usually boils down to becoming a training issue. There are a few options to explore.
If the users are opening the URL from a standard link, then you could enable re-join session for that home page.
You could suggest users open a new tab from a link within the application.
Both options will result in two tabs using the same session, which can cause issues with shared session state, but the new tab link could be defined to clone the session.
Either way, when one of these tabs times out, then the other tabs using that session will have also timed out, and the only pleasant way forward is to close all but one tab.
You might also consider enabling some form of single-sign on.
Related
If an ajax/fetch request fails, my framework (django) displays a nice debug page, which contains a lot of useful information.
In chrome devtools I can see a preview of this debug page. But the window in the devtools is way too small.
Is there a way to open the output of the POST request in a new tab?
If I use right-button-click "open in new tab" then chrome does a GET. But the GET does not trigger the exception which I would like to debug.
I think the best you can do is recreate the scenario in Postman. Postman has a tool called interceptor which syncs cookies and captures requests from Chrome.
Postman interceptor uses a chrome extension which sends the captured requests to Postman app if you enable interceptor from the app.
But there could be security risk that the chrome extension will have Site access to all pages, maybe you can limit it by limiting the site access from extension settings(from settings>extensions>Postman interceptor):
Alternativly, if you do not want to use interceptor, then you can copy the payload(form data) and request headers from Headers section, then put them in Postman and make a request. Or you can use requests library to do the same.
How about using the full-screen mode of dev tools instead of opening in the separate browser tab?
Click on the three dots on the right-hand side of the chrome dev tools
Click on the first option (the two overlapping squares) and it would open the chrome dev tools in the full-screen mode.
Please refer to the image below.
When I am clicking on the upload button in document web, inside that the section master page is showing (which should not).
How to remove this either in SharePoint designer or SharePoint 2013 itself?
Also, the site settings is showing up on home page (but it should show in a separate new page).
Screeshots:
It looks like you have a custom master page that is missing much of the core structure of a master page. In particular, an out of the box master page responds to a Query String value of "?IsDlg=1" to control if master page content is displayed in SharePoint dialog boxes along with primary page content.
To see this, go to a site without this custom master page and visit a list or library page. Edit the URL and, if there's no Query String (i.e. no "?" in the URL, add "?IsDlg=1" (no quotes), or if there is a query string add "&IsDlg=1" (no quotes). Notice the difference in the displayed content.
Something is missing from your custom master page. Either the lack of standard CSS classes or missing JavaScript references.
Can you reset the master page back to one of the out of the box master pages and check to see if everything is now working.
As the the Site Settings, someone must of added an IFRAME or a Page Viewer web part to the home page and set the URL to the Site Settings page.
Making Faster Navigation Between APEX Site-Designer Pages
I am having a few difficulties here as this may be a setting that I took for granted in other previous versions of Oracle APEX as before it may have been a default setting, but now the default has changed. Can anyone help me figure it out? I also explain why it was useful for me before...
How do you enable the Oracle APEX instance to permit logging in to the site-designer pages for a single workspace (Application Builder, SQL Workshop, Team Development modules, etc.) using the same user id through more than one browser window?
Note, I do this to save time from navigating between each section of the site-designer (even quick load times can slow down developing an application page or region because of constant shuttling back and forth to make small changes originally missing).
Example Use Case:
Oracle APEX Release: Application Express 4.2.6.00.03
Database Platform: Oracle 11g R2
Client-Agent(Browser): Firefox Release 33
Note, this was a fresh install from a lower version that was upgraded
several times up to the current APEX release.
LOG IN to Site-Designer with an account that has DEVELOPER or ADMIN level user privileges.
USE your own values for WORKSPACE, USER, PASSWORD.
CREATE a new PAGE level OBJECT (REGION, FORM, REPORT, etc.) and stop in the middle of the set-up wizard.
RIGHT-CLICK on a TOP LEVEL Menu item such as SQL WORKSHOP. Open it in a NEW WINDOW;
CREATE an object like a TABLE which can be used by the DESIGN WIZARD open in step 3.
The reason for trying to keep different browser sessions open for the same USER account allows users to go back to another section of the design tool to build other objects or app/page elements that were overlooked before initiating a design wizard process.
Observed Behavior:
The new session will allow the user to make a new database object, but when clicking back on the previous window with the session that is running the original wizard, the server prompts for a new log in because that session has been closed.
Thanks!
The solution I found when facing a similar situation was opening Apex in a couple of different web browsers in parallel, so i have Safari for the SQL workshop, and Chrome for the page designer..
so instead of ctrl-tab i use cmd-tab (or alt-tab for PC)
Our IT said it has something to do with session state..
All I want to do is create a few pages with sign up forms for our fans and customers on our business facebook page.
I created the new app, named it and went on to the basic settings. From what I can tell I just need to set up the "page tab" info. I Named the tab, put in the page tab url, secure page tab url and uploaded a tab image.
Then I wait for it to show up on our fb page. I refresh the page and for a few seconds it looks like something is being loaded in the list of tabs. But then it stops and the layout of default tabs (photos, likes, and events) are unchanged.
The tab should link to the app url which should load inside of an iframe which will have the html from our web server.
That's how I understand it anyways.
You must add manually the application on your page through this URL: http://www.facebook.com/dialog/pagetab?app_id=APP_ID&redirect_uri=https://www.facebook.com/
Remember to replace APP_ID first.
I have a content editor that, when she logs into the Sitecore content editor and clicks an item, nothing happens. The item doesn't load for editing. If she clicks off of the item to another item she's prompted "do you want to save the changes to the item"?
Logging in with another account resolves the issue. Logging in with her account on another PC resolves the issue.
Has anyone ever seen this before? Sitecore is non-functional on this user's PC.
When you say that the item doesn't load for editing, you need to be more specific? Obviously, if she's clicking off the item and getting prompted to save, then the user is able to edit the item. What is it that she can't do?
Also, it depends on what role you have the user set to use, but depending on how you have your site configured, a user can simply click the item, see the fields and enter content in them. There may not be any "edit" queue. Is this not the case? If not, then there's more details that are needed to properly answer your question.
It sounds like a browser / caching issue. I usually try the following.
1. If IE 9 the I try and open a session in private and try again
2. Clear all browser history
3. If that doesn't work try with another browser.
4. If other browser fixes the issue then try to reset the original browser's settings to the defaults.
Last check if you are using a proxy server and try without. This is a long shot.
What version of Sitecore is being used? Older versions using IE9 require compatibility mode to be enabled (this was resolved in later updates of 6.5)
I find the Content Editor most stable in Firefox and IE9 compatibility mode. Chrome has a few finicky issues but generally works.