DNN: how to un-disable browser back button? - dotnetnuke

I am helping out with a site built using DNN (DotNetNuke). A certain set of pages are somehow blocking the browser's back button. We don't want this behavior. How do we re-enable it? I suspect there's a setting somewhere that's gotten turned on accidentally, but I haven't been able to find any reference to that in the documentation.

I'm not aware of such a setting. It might be in your theme (skin), possibly in some javascript.

Related

Dotnetnuke issue on certain pages

I have a website running on dotnetnuke. However, recently I can't do any action (edit content or page setting) on certain pages (the products subpges in www.midoco.com). Does anybody know why this happen?
What version of DotNetNuke are you on? Check the HOST SETTINGS page to see if you are using the HOSTED Jquery option, if so, try disabling that option.
It is probably a javascript issue, try firing up chrome developer tools (hit F12 in chrome) and check if you have a red X in the bottom right corner. If so, click it and check what causes the issue. I had some similar issues caused by single quotes insted of apostrophes in a language pack and spent a lot of time to find the issue. I just went to one of the pages and see you have an error in /engine1/script.js in your skin.

AngularJS app is not loading on Safari (iOS 5.1.1) back button. Any suggestions?

I've ran into an issue with Safari on iOS 5.1.1 and Angular where I am doing paginated results. After I decide to leave the page that is hosting the app, and then come back to the page by using the browser's history back button.
The application is not initialized so as I scroll again, the pagination functionality is not triggered.
Since 5.1.1 doesn't provide a web inspector, I had to rely on console.log to print events that I want to see that it's executing. On initial load, I see everything ok, but when I am back through the back button nothing fires.
My usual ways of fixing this are not working. Here are the things I've tried:
Used manual bootstrapping of Angular app
Made the page not support caching and expire the page as soon as it's rendered.
Neither of these helped, which is why I am here asking for some suggestions. Unfortunately it's not a very easy thing to replicate through a Fiddle or a hosted HTML file so I am unable to provide one. Hoping that some of you may have experienced this before.
Thanks in advance for any help.
Answer is quite late and I hope you found a solution already but it might be useful for others.
Unfortunately I won't be able to answer why the app is not initialized (due to the lack of code) but I can give you some tools/tips to ease the debugging (assuming you have the iOS simulator).
Debuging on mobile safari can be done either :
with weinre and get the features of the web concole,
or by enabling remote debugging in Mobile Safari itself, see here
Yea, same problem here with iOS 7. It must send the DOM structure over before running any javascript. Kinda pointless...
Since the problem is with mobile safari and since it supports popstate event, you can use this event to detect when the user is back in combination with $location.path(), for example:
$(window).bind("popstate", function () {
alert(location.pathname + $location.path());
});

Delay in Salesforce sites changes

I'm playing with Salesforce's "Sites" functionality today for the first time, whereby I can expose Salesforce functionality to anonymous users via VisualForce. It's cool, but I'm seeing some weird timing behavior. I've been trying to figure it out, but it's a mystery, so I'll ask here?
When I save my changes to my VisualForce page, I would expect to see the changes right away. Or at least, when I do a "real" save (by hitting "Save"), versus a "Quick Save," which I assume is what happens when I'm using the developer toolbar to edit -- or actually hitting the "Quick Save" button in the main VisualForce section.
At any rate, I save it as much as I possibly can, and I'm able to see the right thing when I go to the VisualForce page itself (not using the force.com URL). But when I go to the force.com URL, I'm seeing an old version of a page. If it's just a matter of waiting long enough, that's one thing. But it's acting like I'm doing something wrong.
During development, it is very helpful to add a cache="false" parameter to the apex:page tag. This should solve the issue.
Reference page for apex:page has other optional parameters as well.

How can I remove Unwanted ads on my drupal

I see some ads on my drupal website. No idea where they came from but I want to get rid of them. Any help appreciated
This one comes up from the bottom of the screen from time to time.
You can minimize it but it doesnt go away unless I close my webpage, and open again
It was related to Softonic Toolbar not something with Drupal.
I removed all the toolbars or that kind of unwanted programs which I installed(without conscience) then cleaned with Malwarebytes and CCleaner.
Now everythings fine
I had the same problem. I solved the problem by deactivating the ad option. To do this, simply click on the "ad option" at the bottom of the ad. You will get a page that mentions different things about the ad. Click on "deactivate" link. It will take to another page where you can deactivate the advertisement. It won't come back.

How can I disable F5 (refresh Browser) for Silverlight application without affecting closing?

I was reading this post and noticed that when I am closing browser or tab the message is showing as well. I need to disable the Refresh button or give some warning but problem with solution in that post is that it shows message when I close browser.
Is there any way to show message only on refresh?
I know that there are some posts like this on stackoverflow.com, but none of them work for me. So this is not a duplicate question unless there is a working solution.
window.onbeforeunload from JavaScript (as noted in the post you link to) really is the only way this can be done in a cross-browser, cross-platform way, that I know of.
But that does end up getting triggered for F5. That's just the way browsers work - they unload a page before reloading it, even in the refresh case.
Do you really find users hit F5 often enough for such a prompt to be a problem?
Isn't it possible to catch a key down event on F5?
If not with silverlight you can probably with a keyboard hook.

Resources