Is there a good way to reload the entire application upon (type === AUTH_LOGOUT) and make sure it completes reloading before we representing the Login page?
Thanks!
Which version of admin-on-rest are you using? There was a bug prior to v1.1.0, now the state resets after a logout, and the whole app should rerender.
Related
I have moved my project to prism 7.2
I have quite a few "OnNavigatingTo" and replaced accordingly with InitializeAsync or Initialize
If I remember correctly "OnNavigatingTo" was firing every time you navigated to a page whether to or back. If I was navigating back to a page it would fire whilst Initialize doesn't.
This whether correct or wrong is causing me issues with some of my pages where I was passing back parameters when navigating back .
Is this the intended behavior?
thanks
OnNavigatingTo was only ever supposed to fire once. It's intent was to initialize. There ended up being cases where it fired more than once. Anything you require done once should be placed in IInitialize.Initialize anything that should be fired each time you navigate or requires some logic like Navigated Back to... should be in INavigat[ed|ion]Aware.OnNavigatedTo.
It was this confusion that led so many Prism users to request that the support be dropped and a new API be introduced that made the intent clearer.
I am developing an application on xpages and I have the following problem:
I use dynamic view panel with customizer bean. The customizer bean is based on the Jesse Gallagher bean available on GitHub (https://github.com/jesse-gallagher/Domino-One-Offs/blob/master/mcl/reports/DynamicViewCustomizer.java).
The problem is that after a few minutes of inactivity in the application, the navigation components (Pager Expand / Collapse, Pager, and PagerSizes) stop responding. The document access link works normally. If a refresh is run in the browser, the navigation components will work again.
If I remove the bean customizer the problem does not happen.
Does anyone know what the cause of the problem is and how to solve it?
Thaks a lot!
Marcus
Put Keep Session Alive controll from Extension Library to your page and set the delay for example to 60s. If this helps, you can change this to higher value.
The real cause of the problem was that I was adjusting some component and testing at the same time, without giving a reload in the application in the browser. This causes the behavior of the application to be abnormal. That way if you are testing and concurrently changing something in some component of the application, reload the application in the browser.
I have a challenge in my app that I need to resolve quick, the thing is I have to prevent the current component from being destroyed when I navigate backwards using this.location.back();
Based on my project I have an About Us link in my Login component that navigate to the About component using this.routerExtensions.navigate(["/about"]);, in the About component I added the back button that goes back to Login component as I described in the first paragraph. My problem is that the About component is destroyed and I need to prevent that.
Is there any way I can implement this functionality?
Thanks!
When we navigate to a page it reloads every time. If I previously created some views dynamically in it either programatically or using ui/builder all of this will be lost. Is there a way to save / cache the state of the page and restore it after the page reloading?
Set a boolean variable when you have loaded a page. Whenever navigating back to that page, check the status of the boolean variable in the pageLoad/onNavigatedTo hooked up functions before the actual code in that page.
I'm afraid of that there is no built-in feature for that.
What you can do is to store/reload manually your screen's data in application-settings at the unloaded and navigatingTo events.
I am implementing a web application using ASP .Net and C#. One of the pages has a requirement that it always needs to be fetched from the server, rather than from the local browser cache. I have been able to achieve this.
We have a back button in the application, which simply invokes javascript:history.back() method. The problem is that when the back button is clicked to navigate to the page which is always to be reloaded from the server, the browser displays a "Web page expired message".
The intent here is to force the browser to reload the page rather than display the web page expired message.
Any help would be highly appreciated. Thanks a ton in advance.
You will probably need to change the implementation to make the browser load the URL explicitly:
window.location.href = 'http://....';
instead of invoking the back button, since the intention of the back button is to get the last page from the cache.
(If browsers would not act that way, they would re-send your form data multiple times when using the back button during a registration process or similar.)
You mean you want to control browser behaviour, which is not possible. I doubt you can solve it that way. You could set the expiration time to a small value (1 minute perhaps?) so that the page is still valid if one navigates back quickly.