tracker issue : CF-3923584

select a category, or use search below
(searches all categories and all time range)
Title:

After applying CF11 Update 4, CF is not able to append /CFIDE/scripts path to the URL because of which all the features using scripts are not working.

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/Fixed

Reporter/Name(from Bugbase): / ext-user (Nimit Sharma)

Created: 01/19/2015

Components: Administrator, Administrator Console

Versions: 11.0

Failure Type: Incorrect w/Workaround

Found In Build/Fixed In Build: 292980 /

Priority/Frequency: Major / Most users will encounter

Locale/System: English / Mac 10 All,Win XP All

Vote Count: 0

Listed in the version 2016.0.0.297996 Issues Fixed doc
Verification notes: verified_fixed on July 22, 2017 using build 2016.0.01.298513 
Problem: After applying CF11 Update 4, CF is not able to append /CFIDE/scripts path to the URL because of which all the features using scripts are not working.

Method:

1. Install CF 11.
2. Click on any browse button after login to CF admin.
3. We can see all the drives available to the system.
4. Apply Update 4.
5. Access CF admin and follow Step 2.
6. Now, It doesn't show any drive.

Result:

Expected:

Workaround:

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3923584

External Customer Info:
External Company:  
External Customer Name:  
External Customer Email:

Attachments:

Comments:

I had the same situation and figured out it's due to custom Default ScriptSrc Directory. The Browse Buttons would worked when accessed via IIS that had the Virtual Directory created to the custom Default ScriptSrc Directory but not via tomcat internal server. I followed these instaructions https://vicker313.wordpress.com/2009/08/08/add-tomcat-virtual-directory/ to create virtual directory to my custom Default ScriptSrc Directory in tomcat and after instance restart the browse buttons are working again.
Comment by External U.
8895 | April 23, 2015 04:52:50 PM GMT
Confirmed this issue does not affect CF11 and CF2016 when accessed via IIS having a virtual directory matching CF Admin's custom Default ScriptSrc Directory. Thanks!, -Aaron
Comment by Aaron N.
8896 | July 22, 2017 09:01:29 PM GMT