This content has been marked as final.
Show 4 replies
-
1. Re: Error message "Initialize is not defined"
Newsgroup_User Nov 28, 2006 9:26 AM (in response to Averill)a possible cause of js errors from dw menu items is if you have an
Anti-Virus doing real time scans. Reason- when you invoke a dw command- it
calls on several .htm and .js files. The real time a/v scan can cause a
delay and throw off the javascript timing, like having a variable called
before the included file that defines it is opened.
test- turn off real time scanning
fix- go into the a/v preferences, and see if you can exclude the
dreamweaver/configuration folder from real time scans.
-
2. Re: Error message "Initialize is not defined"
Averill Nov 28, 2006 10:10 AM (in response to Newsgroup_User)Thanks, Alan.
AV scanning (McAfee) was already turned off for running scripts. If that's not what you meant, then I don't know what you mean.
This problem is new, after I've been using DW8 for at least a year. It just started in the last week, and I can't think of any changes in my computer or program configuration that have happened in that time. Or should I say, I haven't made any changes yada yada - not that it matters, I suppose. No new extensions, no new programs, nada. -
3. Re: Error message "Initialize is not defined"
Newsgroup_User Nov 28, 2006 10:29 AM (in response to Averill)Just to verify, you've gone through this TechNote already?:
Troubleshooting JavaScript errors in Dreamweaver
http://www.adobe.com/go/19105
You can uninstall extensions via the Start menu: Start > Programs >
Macromedia > Extension Manager.
I wouldn't worry about not being able to do a second install of DW.
--
David Alcala
Adobe Product Support
-
4. Re: Error message "Initialize is not defined"
Averill Nov 28, 2006 5:58 PM (in response to Averill)I had gone through most of that tech note, but hadn't renamed the configuration folder - sort of stopped after I couldn't uninstall my extensions. So now I did unstall the extensions (thanks for that tip!!), which didn't help; then renamed the the configuration folder - and voila! it worked. I've done this before for a similar problem, guess I should clean out all the old config folders out there. Thanks for that. Shows me I must complete the tasks given - just didn't quite believe that this was the problem being addressed by the tech note.
Thanks for the help!
Averill


