Knowledgebase
|
Unresponsive script Warnings when working with very large bookings
Posted by Jesse Chieppa on 29 Jun 2011 01:16 PM
|
|
Unresponsive script Warnings when working with very large bookingsIf you manage very large bookings or group bookings you may find that your browser gives you an unresponsive script warning. This is caused by the default timeout for java scripts being set lower than is needed to complete the action when dealing with very large groups. To up the time a script is allowed to run do the following. Firefox 1. In the Location bar, type about:config and press Enter. â—¦ The about:config "This might void your warranty!" warning page may appear. Click I'll be careful, I promise!, to continue to the about:config page. 2. In the about:config page, search for the preference dom.max_script_run_time, and double-click on it. 3. In the Enter integer value prompt, type 60. (Or enter 0 to let the script run forever without prompting) 4. Press OK and restart your browser for the change to take effect. Internet Explorer Review KB Article posted at http://support.microsoft.com/kb/175500 WARNING: Modifying the registry as described in the steps below can have major impact on the operating system if done incorrectly. We recommend only modifying the registry if you are experienced and comfortable in doing so. Otherwise please install Firefox and follow the steps above Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756 How to back up and restore the registry in Windows http://support.microsoft.com/kb/322756 To change this time-out value in Internet Explorer 4.0, 5.0, 6, 7, or 8, follow these steps: Using a Registry Editor such as Regedt32.exe, open this key: HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Styles Note If the Styles key is not present, create a new key that is called Styles. Create a new DWORD value called "MaxScriptStatements" under this key and set the value to the desired number of script statements. If you are unsure of what value you need to set this to, you can set it to a DWORD value of 0xFFFFFFFF to completely avoid the dialog. By default the key doesn't exist. If the key has not been added, the default threshold limit for the time-out dialog box is 5,000,000 statements for Internet Explorer 4 and later. Because the Internet Explorer 4.0, 5.0, 6, 7, and 8 time-out is based on the number of script statements executed, the time-out dialog box will not display during ActiveX control or database-access delays. Endless loops in script will still be detected. Safari 1. You need to access the Safari Debug Menu 2. When the Debug Menu is activated, click on it in the menu bar and uncheck “Enable Runaway JavaScript Timer” (pre Safari 4) or check Develop -> “Disable Runaway JavaScript Timer” (Safari 4+) If the Debug/Develop menu is not available: 1. Quit Safari. Open Terminal.app in your Utilities folder. 2. Copy & paste the following command into the window: defaults write com.apple.Safari IncludeDebugMenu 1 3. Press “return”. When you see your Mac’s name as command prompt, it’s done, 4. Quit Terminal 5. Restart Safari and go to the Debug or Develop menu, following the suggestion above. If you are uncomfortable following the steps above please install Firefox and follow the defined steps for Firefox. | |
 (0 vote(s)) Helpful Not helpful |