Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
DCRs do not close properly if VFE has focus
yanSi
When I click the X button to close a DCR that currently has focus on a VFE field, the IE window does not close properly. The window remains in the taskbar and IE process utiliazation goes to 100 percent. My simple DCT only has one VFE field and no formapi so I do not think there is anything wrong with the code. Does anyone know what may be causing this?
Find more posts tagged with
Comments
yanSi
oops. copy and paste didn't work. the datacapute is attached.
Icebreaker
Not Sure,
May be you can check if your config.xml has any errors.
Jay
sort.jpg
yanSi
This problem was happening before I made any customizations to visualformatconfig.xml.
The IE window closes properly when I use the cancel or finish button but occurs only when I click the X button of IE.
ohkal
We are also experiencing this same issue now that we have upgraded some of our servers to 6.7 from 6.5. In 6.5 this problem did not occur and we have not changed any of our VF configs, DCTs, etc.
When you first open a VFE-enabled DCT in 6.7 you are prompted to install a new version of ewebeditpro. After installing this version we start getting this exact problem where the browser will not completely close when you click on the X. Basically, the DCT browser will appear to close but it actually remains in the task bar. If you try to right click on the item in the task bar and choose CLOSE, you will get the common Windows error message saying "This program is not responding...Click End Now or Cancel" If you click End Now to kill it, it will kill your TeamSite main browser too.
If we uninstall this version of ewebeditpro and reinstall from 6.5 then the problem goes away, but again we will be forced to install the 6.7 version when we open a DCT in 6.7 and thus end up facing the same problem
Has anyone had any success in resolving this or at least identified why it is happening? Interwoven support has not been able to replicate the issue so far.