Our catalogs are continually restarting PWB because a script on the page is triggering the inactivity timer. If I disable active script in the IE Security settings, or open to a different page, the problem goes away. I have read through the threads on the Inactivity counter and tried all the recommendations.
[Browser]
...
StartTimersOnMouseKeyboard=True
...
[Inactivity]
InactivityTimer=True
InactivitySeconds=120
InactivityMessageTitle=End Session
InactivityMessageFile=C:\PWB\Catalog_Inactivity.rtf
InactivityAction=Exit
InactivitySoundFile=
InactivityStartOnOpen=False
InactivityShowDialog=True
ResetOnMouseMove=True
ResetOnMouseButton=True
ResetOnKeyboard=True
Unfortunately, I have no control over the content of our catalog. Any ideas? Thanks.
Active Script triggering Inactivity Counter
Moderators: Tyler, Scott, PWB v2 Moderator
Sorry, that would have made sense
That would have made sense to give you the URL:
http://alpha2.suffolk.lib.ny.us/search~S43
Also, I downloaded the latest PWB version.
http://alpha2.suffolk.lib.ny.us/search~S43
Also, I downloaded the latest PWB version.
Found the problem
I found the problem. I tore through the catalog and found the one line causing the problem
I created a test page, with just this line, that caused PWB to restart:
http://www.nenpl.org/cat_temp/Inactivity.htm
I am going to try and have the link removed from the catalog.
Code: Select all
<script></script>
http://www.nenpl.org/cat_temp/Inactivity.htm
I am going to try and have the link removed from the catalog.
Is this page available for testing?
http://www.nenpl.org/cat_temp/Inactivity.htm
It seems to be missing.
--Scott
http://www.nenpl.org/cat_temp/Inactivity.htm
It seems to be missing.
--Scott
moslty empty
I left the page as empty as possible, so it only had the one line that loads the widget, but not the line that actually calls an instance of it. That was enough for PWB to restart on its own. I just added the call so you can see it on the page.
I'm sure you'd still like to examine the cause of the problem, just know there is no rush. I have been able to remove the widget from the catalog homepage and that fixed the problem. I'll leave the test page up until your done troubleshooting.
I'm sure you'd still like to examine the cause of the problem, just know there is no rush. I have been able to remove the widget from the catalog homepage and that fixed the problem. I'll leave the test page up until your done troubleshooting.