FCKeditor solves the problem of cross-origin application in IFRAME.

Some days ago, when I was working on extjs + FCKeditor, I found a very tricky problem.

 

When IFRAME is not nested, all functions of FCKeditor are normal and the application is very convenient. However, when I cross-origin, the application pop-up forms in the toolbar of the editor cannot be opened, with a 404 error.

 

Page a loads page B

 

Page a is the application IFRAME

B page placement rendering FCKeditor

 

The two pages are used in different domains and normally used in one domain, but displayed normally in two different domains, the Error 404 is not found in the pop-up box for uploading images.

 

After painstaking research, I finally found a solution.

 

In the FCKeditor/Editor/JS/fckeditorcode_ie.js script file, it was a mess when it was just opened. It was really annoying to solve it.

We found that O. src = fckconfig. basepath + 'fckdialog.html 'is the form path of the pop-up tool, that is, this path is wrong.

 

It is a relative path, so it obtains the parent path.

 

Modified to: O. src = fckconfig. fullbasepath + 'fckdialog.html ';

 

After obtaining the path of the current editor domain, it will be OK.