I go into site manager for an old page that we want to disable. The Display param on the Publish tab is set to "No", but one can still put in the page's url and get to it in the browser.
Is that the way it is supposed to work.
Related
I am trying to figure out in SSRS 2016 why the back button goes missing and how to get it back. I am adding the report into an iFrame of another application - I do not have access to that application's code, I just get to put in a URL.
If I put in a URL like this:
http://sqlservername/Reports/report/Cityworks%20Reports/Parks/ParksReport?rs:embed=true
I get the back button, however the report does not scroll horizontally very well.
If I put the URL in like this, the report scrolls horizontally very well however the back button goes missing:
http://sqlservername/ReportServer/Pages/ReportViewer.aspx?Cityworks+Reports%2fParks%2fParksReport&rs:Command=Render
I have tried to see what other options are available and am stumped at the moment. Has anyone come across this and know a solution?
Try add to the wanted URL the follow parameter
&rc:showbackbutton=true
One URL is for the Report manager, and the other for Browsing. The URL with YourServer\ReportServer is the browser landing page; there's therefore no "need" for the back button as it's purely a browsing page. If you go to http://YourServerName/ReportServer you'll see you have a page that very much looks like one you get with IIS with folder browsing enabled. Normally you only land on these pages when you receive a report by email, which contains a link to the report; or you are an end user.
The other URL YourServer\Reports is the report manager. It makes more sense here to have a back button, as you are navigating a management portal. As a result you could have come from other pages other than the folder browser page.
I have 2 pages, a main page and a secondary. And in both the pages I have a form with the auto complete integrated.
In the main page after I choose a place(Auto complete works here) and click the submit button i get redirected to the secondary page, where the results get displayed.
When I use the form in this secondary page the auto complete doesn't work. But if I reload the page, it works.
I have tried $route.reload, $location.path($location.path()) etc, but that is not helping. Only location.reload() works, and the data stored in the services is getting reset when I use this.
How do I get Response/Request URLs (which are shown in F12 Developer tools - Network Tab) using QTP 11? Based on these URLs, I need to perform certain action in my application. Is there any alternate solution to get those URLs?
Scenario: Open IE browser and navigate to a URL, Press F12, Go to 'Network' tab. Click on 'Start Capturing' button. Now click on any button or link on the page, you will get a set of URLs in the Developer Tool (F12).
Firstly, do you need all of the URL requests generated from a button and/or link click? Remember that what you get from the "Network" tab in the developer tools also include URL's for fetching e.g. Javascript and CSS in addition to, for instance a GET request to an external API.
I'll try an provide you with an alternative approach. If what you are really requiring is the URL associated with each interactive element, then you should be able to get that by using the GetROProperty method like so:
strURL = Browser("YourBrowser").Page("MainPage").WebButton("aButton").GetROProperty("href")
A more generic script for fetching e.g. all the "href" properties for all the links on a page may be found in the following post: (HP QuickTest) How do I get HTTP status using QuickTest?.
Hope this helps.
UPDATE: With regards to your question regarding fetching of the URL's from the IE developer tools; As far as I know there is no way to fetch them from this view by using QTP.
I have an issue with DotNetNuke where only the admin can see a new page I've added in the main navigation (the page appears in sidebar for all users)
After creating a new page with DotNetNuke, I can manually browse to the page, and all links to it work however it is only visible in the navigation menu when I'm logged in as administrator.
Manually going to the page works fine when not logged in. Include in Menu? is checked (and been toggled) and I've tried all variations of permissions I can think of (which apart from the navigation issue work exactly as I would expect).
I hope this is the correct format I'm still relatively new!
Sounds like you have the page settings set to admin only for view... navigate to the page click on pages>page settings. click on the permissions tab and make sure inherit page settings from parent page is unchecked. Then next to All Users, Registered Users, Subscriber,
Translator (en-US), Unauthenticated Users and Unverified Users make sure there is a green check mark in the view section. Then make sure that page is disabled in advanced settings is unchecked and include in menu in page settings is checked.... Hope this helps... If not try making a new page and copy all the modules from the old one and see if that works
In my application I have a page that display several tabs. All the informations are gathered with a single HTTP request. Every tab contains an HTML form. By default on the load of the page we load the first tab. After a modification within any tab we reload the page for informations refresh (following en INSERT/UPDATE in a backend database). What we want: if before any update we were on a particular tab (any other than the first one), to return on the same tab.
I thought at several solutions:
To use different URL for different tabs (panes), namely URL routing. For example, domain.ext/page/tab. There, I have a problem because the URL must update following user trace. If the user click on a 3rd tab, we have to change the URL to domain.ext/page/3rd-tab using $location.path() which triggers page reloading.
To use the same URL (what we have now) and anchors in the page managed by $location.search() and reloadOnSearch = false. For example, domain.ext/page?pane=tab. There, I have another problem because the query string (that is managed by $location.search()) is kept at service level and when the user goes on another page, the query string is the same (domain.ext/another-page?pane=tab). I would like to delete the query string when the user leaves the page.
To use ui-route. This solution change lot of the actual structure of the application.
IMHO the 2nd solution seems better except that I don’t know where and when to reset query string.
I’d like your opinions on this topic.
Thanks.