Ticket #1614 (closed Bug: fixed)
Difference between FCKConfig.BasePath and .FullBasePath
| Reported by: | alfonsoml | Owned by: | martinkou |
|---|---|---|---|
| Priority: | Normal | Milestone: | FCKeditor 2.6.2 |
| Component: | General | Version: | |
| Keywords: | Confirmed Review+ | Cc: |
Description
In editor/source/internals/fckconfig.js the FCKConfig.BasePath and FCKConfig.FullBasePath are calculated automatically, for file:// they both end up being the same, but for the rest of the protocols .BasePath doesn't contain the reference to the protocol and the host.
This usually works, but for chrome:// it fails to load any file referenced by .BasePath It is enough to make FCKConfig.BasePath = FCKConfig.FullBasePath to get the editor loading the stylesheets, so I wonder if the distinction between the two settings is really needed or we could add the reference to protocol and host to .BasePath and get rid of FullBasePath replacing it wherever it appears with .BasePath
Attachments
Change History
Note: See
TracTickets for help on using
tickets.